Changes between Version 3 and Version 4 of ServiceBinding


Ignore:
Timestamp:
07/02/07 16:24:57 (12 years ago)
Author:
lawrence
Comment:

updated with some information about the relevant bits of the ISO19115 content model

Legend:

Unmodified
Added
Removed
Modified
  • ServiceBinding

    v3 v4  
    22 
    33==== DIF ==== 
    4  
    54 
    65==== Introduction ==== 
     
    217216We should simply parse all non-NDG records directly into a related URL, and parse them back out again preserving their content identically. 
    218217 
    219  
    220  
    221  
     218== ISO19139 == 
     219 
     220Then the question is: how should we do this in ISO19139? 
     221 
     222In terms of the content model (ISO19115), the relevant pieces are: 
     223 * DIF's entryID maps onto MD_Metadata/datasetURI (not really relevant to ServiceBinding, included for completeness) 
     224 * All metadata records map onto between 0 and 1 MD_Distribution entities. 
     225   * Which has 0 and many MD_DigitalTransferOptions 
     226     * Which has 0 to many CI_OnlineResources 
     227       * Which consists of a compulsory linkage and optional protocol, applicationProfile,name,description,function 
     228         * of the latter could be download, information,offlineAccess 
     229           * defined as "instructions for transferring data", "information about " 
     230   * We may want to make use of the MD_Format 
     231     * Which has compulsory name and version characterstrings plus an optional specification 
     232 
     233 
     234 
     235  
     236 
     237 
     238 
     239