Version 3 (modified by lawrence, 14 years ago) (diff)

Introducing the data granule material

Discussion about MOLES issues and priorities


  • Initial Version, BNL, reporting a discussion between BNL and KON. Based on ndgmetadata1.2.5

Issues on the Table

(Will eventually be a list of tickets)

  1. The CoatHanger?
  2. Granules
  3. Stub-B Schema


Work is underway to modularise MOLES so that components can be used in the MOLES schema itself and in the stub-B schema. (Need some details. What is involved? Saved for another day).

  • Noting that stub-b is a major interface for browse and travelling metadata
  • Noting also that we accept that very large deployment lists may occur, but we'll worry about that when it happens.

The CoatHanger?

Issue CH1: how do we import material into MOLES? It turns out we already have the dgMetadataDescriptionType: which should occur in each moles record, although it doesn't form part of one of 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).

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.

Issue CH2: The Online Reference type No image "dgOnlineReferenceType" attached to MolesDiscussion should evolve towards something that exploits xlink, so that we can indicate whether one expects to insert the linked object, point to the linked object, or render the remote object, and insert it ...

Issue 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 of the xlink, recognising that we will be on the bleeding edge here and some future changes in our technology may be necessary).

Issue CH4: NumSim in particular. Here we expect to wait for an ISO19139 compliant version, which will have clear subcomponents targetted for the deployment and data production tools.


Here the issue is to come up with schema content that maximises the amount of information we can promote from CSML and provides content to clearly indicate to the browse user which granules are of interest.

There are two parts of the Data Entity which are of interest: overall information about the data entity, and the information we put in a data granule.

The overall material includes the following two elements:

and the granule is