Changes between Version 4 and Version 5 of PlymNotesPeter


Ignore:
Timestamp:
11/07/06 16:15:31 (13 years ago)
Author:
pmiller
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PlymNotesPeter

    v4 v5  
    66 * Highlight report - mostly on schedule at post-Alpha review. WG group were instrumental in Alpha system integration testing. 
    77 * Next three months: need detailed definition of Beta products. Start playing with Vocab server? Discovery back end is broken, Matt Prichard to work on this. Population!  
    8  * CSML future: Andrew presentation (CSML API and v2). CSML will be used by MetOffice and other projects, e.g. FP6 MOTIIVE. Read Exeter communique on OGC etc. (metoffice/infomatics?) Development of 'feature types'. GML stable version 3.2. 'Operational affordance' - can only extend one feature type but can inherit properties from multiple...? CSML will deliver core set of base types, derived feature types, basic services (api), schemas, tooling (parser/scanner).  
     8 * CSML future: Andrew presentation (CSML API and v2). CSML will be used by MetOffice and other projects, e.g. FP6 MOTIIVE. Read Exeter communique on OGC etc. (http://www.met-office.gov.uk/informatics/) Development of 'feature types'. GML stable version 3.2. 'Operational affordance' - can only extend one feature type but can inherit properties from multiple...? CSML will deliver core set of base types, derived feature types, basic services (api), schemas, tooling (parser/scanner).  
    99 * So what should DPs do towards CSML? NOCS will be adapting scanner to deliver their HDF data rather than CF-netCDF. BODC is using QXF-read method from Matlab/Java. Implement CSML v1 for now, then modify for v2. Swath very soon. Parser lets us play with CSML records prior to DX working - use that to help us write our scanner. If going from data->CSML, must write scanner in Python as this encodes the objects and attributes. If going from metadata->CSML, just need to plug in SQL extraction to Python scanner.  
    10  * MOLES future: MOLES is for generating various discovery formats, and will not be driven by external standards e.g. SensorML. x-links to include other docs (XHTML, SensorML, ...) verbatim within MOLES records, e.g for BODC calibration info. Could simplify/thin MOLES... Bryan proposes generating CSML data objects '''first''', then flesh out MOLES from those (then DIF).  
    11  
     10 * MOLES future: MOLES is for generating various discovery formats, and will not be driven by external standards e.g. SensorML. x-links to include other docs (XHTML, SensorML, ...) verbatim within MOLES records, e.g for BODC calibration info. Could simplify/thin MOLES... Bryan proposes generating CSML data objects '''first''', then flesh out MOLES from those (then DIF). Several issues to be sorted: Granules and crossover with CSML; schema for Stub-B; add coathanger facility; export to ISO19139; ... 
     11 * Kerstin's job has changed, so Andrew taking over role. 
     12 * Future funding? Bryan is now on NERC Information Steering Group (ISG). So Discovery portal will be funded. NERC FAB - flexibility and agility in funding. NDGx...?  
     13 * MOLES Browse (python) knowledge transfer from Bryan to Dominic/Fabio. Next stage is to deploy at DPs, configuring.  
     14 * OAI issues with deletion in eXist. Keep with DLESE version or change to...? 
     15 * e-Science All-Hands - no NDG papers... Poster on niESS stand/demo of MOLES browse - Roy certain days?, Mike G all days (free person for stand),  Helen to provide poster (from GO-ESSP ppt), Helen/Fabio, Michael H, Steve P?  
    1216 
    1317== All-Hands Meeting ==