4 | | |
5 | | |
6 | | And these are converted by hand: |
7 | | |
8 | | NDG PB and AH July 2006 |
9 | | * CSML |
10 | | * not developed in isolation. |
11 | | * conformance to emerging best practice |
12 | | * DECISIONS |
13 | | * all new engineering on csml2.0 should be finished by pre-beta |
14 | | * new developments |
15 | | * processing affordance |
16 | | * GML 3.2 |
17 | | * swath, profileCollection |
18 | | * storage descriptor moving to own namespace |
19 | | * composite domain pattern (remove WHY WHY WHY) |
20 | | * respect standards and autogeneration tools |
21 | | * what is CSML |
22 | | * Core set of base types |
23 | | * trivially derived FTs |
24 | | * schemas |
25 | | * tooling |
26 | | * parser |
27 | | * scanner |
28 | | * cf-compliant netcdf specific |
29 | | * api: basic services |
30 | | * Care in evolution |
31 | | * bodc should be able to do it from sql to python code |
32 | | * nocs may need to transform csml1 to csml2 to avoid rereading entire archive |
33 | | * Need to consider the relationship of delivery service CSML and content at all data providers |
34 | | * How do we plan to deliver qxf files to the consumer of csml files |
35 | | * qxf read methods |
36 | | * MOLES |
37 | | * Decisions |
38 | | * MOLES is an INTERNAL NDG format |
39 | | * Main reason for existence |
40 | | * provide common interface for producing D |
41 | | * content for exporting DIF, ISO19139 |
42 | | * Provides tool for NAVIGATION |
43 | | * Moles should NOT be a profile of ISO19139 |
44 | | * Internal information storage should not be driven by external standards |
45 | | * Needs to be easier to modify, and extend by adding external schema |
46 | | * Needs the "coathanger" functionality. |
47 | | * three types |
48 | | * import content as is |
49 | | * link to content |
50 | | * import content rendered by this service |
51 | | * Major Priorities |
52 | | * Sort out Granules |
53 | | * cross over with CSML |
54 | | * Sort out SpatialTemporal Descriptoin |
55 | | * are bounding boxes sorted |
56 | | * Schema for Stub-B |
57 | | * no explicit catering for big deployments etc |
58 | | * Add Coathanger Functionality |
59 | | * specifiy mechanism |
60 | | * includes what is being hung off |
61 | | * to which nodes |
62 | | * Add ISO19139 export |
63 | | * which profiles |
64 | | * do we have the content? |
65 | | * need code |
66 | | * UML model of existing MOLES |
67 | | * Documentation, Documentation, Documentaiton |
68 | | * xlink pattern issue |
69 | | * transport mechanism |
70 | | * uri |
71 | | * file type |
72 | | * insert or load |
73 | | * role in moles and csml |
74 | | * server side subsetting, how to put in the uri |
75 | | * xlink |
76 | | * roile |
77 | | * arcrole |
78 | | * Services |
79 | | * Discovery |
80 | | * ISO191309 import |
81 | | * browse/discovery view |
82 | | * import of spatio/temporal into backend complex database |
83 | | * Role of OpenSearch |
84 | | * Role of OGC Catalogue Services |
85 | | * Greg Read having an IOC WMO profile meeting in September in Phillidelphia |
86 | | * Z39.50 gateway |
87 | | * Security |
88 | | * evolving to more standards compliance |
89 | | * Java coding |
90 | | * AHM |
91 | | * One free person (registration paid for) |
92 | | * Michael and Helen |
93 | | * Mike |
94 | | * on holiday? |
95 | | * Meetings Needed |
96 | | * Need a bbftp, delivery service, csml discussion, then talk about dx/wXs |
97 | | * Code Review meeting |
98 | | * BInary Image Format Meeting |
99 | | * Issues to trac |
100 | | * Who owns BBFTP |
101 | | * vocab.ndg.nerc.ac.uk |
102 | | * Browse |
103 | | * history should include D |
104 | | * xml rendering/printing clarity needed |
105 | | * WG issue: how to manage role mapping as things change in data providers |
106 | | * can we use the vocab server for role publication |
107 | | * can the aa check whether they have changed |
108 | | * How can we limit discovery searches to specific sites ... |
109 | | * Should Moles creation tools be externally facing? |
110 | | * What advice would one starting from scratch? |
111 | | * database configuratoins |
112 | | * dataset/datagranule decisions, reasons, and limitations |
113 | | * clear guidance needed for use of csml docs (e.g. can cope with 10,000 files) |
114 | | * Automatic population of OAI repository from updated MOLES ... |
115 | | * PML do that ... |
116 | | * Still need to resolve OAI respository quality issues. |
117 | | * CSML API read methods need coordiation (ie. dom isn't doing the work, but he needs to implement them); relationship with CF-API work. |
118 | | * testrig via equivalents to ncdump and ncview? Exploiting CDAT |
119 | | * Phenomenon needs to be fully described (cell methods problem) |
120 | | * Expecation: where a standard name exists, exploit parameter mapping in vocab server to provide discovery vocabularly. Where a standardd name doesn't exist, we need to face the fact that moles records don't have parameter discovery ... records ... |
121 | | * csml api needs to be able to point at a file or an exist db csml file |
122 | | * what do we do about duplicates in our oai harvested repository |
123 | | * namespace problems in xqueries in exist and csml etc |
124 | | * we have one oai repository |
125 | | * should have two exist databases |
126 | | * one live one development |
127 | | * both populated directly |
128 | | * harvest now button |
129 | | * link checker for harvested material |
130 | | * could send an email if some exists to do so |
131 | | * flag broken links in display |
132 | | * parse access constraints a bit more carefully |
133 | | * Better branding for data providers (icons in browse etc) |
134 | | * How to show html in Trac ... |
135 | | |
136 | | The error message which follows is known and understood: we are trying to build a macro which |
137 | | displays a freemind mindmap ... but it's still a broken macro ... |
138 | | |