Changes between Version 1 and Version 2 of ftfNotes0607


Ignore:
Timestamp:
13/07/06 09:45:59 (13 years ago)
Author:
lawrence
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ftfNotes0607

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