Changes between Version 1 and Version 2 of MolesDiscussion


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

--

Legend:

Unmodified
Added
Removed
Modified
  • MolesDiscussion

    v1 v2  
    1  
    21== Discussion about MOLES issues and priorities == 
    32 
    43'''History''': 
    5  * Initial Version, BNL, reporting a discussion between BNL and KON. Based on [source:TI07-MOLES/trunk/v1Schema/Schemae/ndgmetadata1.2.5.xsd?rev=1299 ndgmetadata1.2.5] 
     4 * Initial Version, BNL, reporting a discussion between BNL and KON. Based on [source:TI07-MOLES/trunk/v1Schema/Schemae/ndgmetadata1.2.5.xsd@1299 ndgmetadata1.2.5] 
    65 
    76==== Issues on the Table ==== 
     
    2019=== The CoatHanger === 
    2120 
    22 The Issue: how do we import material into MOLES? It turns out we already have the ''dgMetadataDescriptionType'': 
     21Issue CH1: how do we import material into MOLES? It turns out we already have the ''dgMetadataDescriptionType'': 
    2322[[Image(dgMetadataDescriptionType)]] 
     23which should occur in each moles record, although it doesn't form ''part'' of one 
     24of the major entities (Activity, Data Production Tool, Observation Station, Deployment, Data Entity). The descriptionSection would seem to be a useful adendum to each of these in their own right (possibly instead of making it part of the overall description, since we see this additional information being additional attribute(s) of the entities). 
     25 
     26''To consider:'' Making a descriptionSection ''part'' of each of the major entities, allowing a stub-b to include this information for each of the first order entities in a natural way. 
     27 
     28Issue CH2: The Online Reference type  
     29[[Image(dgOnlineReferenceType)]] 
     30should evolve towards something that exploits xlink, so that we can indicate whether 
     31one expects to insert the linked object, point to the linked object, or render the remote object, and insert it ... 
     32 
     33Issue CH3: Provide a suggested mechanism of exploiting xlink to do this. (A proposal should be a schema fragment which includes a controlled vocabulary for the attributes 
     34of the xlink, recognising that we will be on the bleeding edge here and some future 
     35changes in our technology may be necessary). 
    2436 
    2537 
    2638 
     39 
     40 
     41 
     42 
     43 
     44 
     45 
     46