Difference between revisions of "Documenting ISO-1 Metadata for Service Discovery"

From Earth Science Information Partners (ESIP)
Line 10: Line 10:
 
             <tr>
 
             <tr>
 
                 <td valign="top"><b>Responsible party: (O/N)</b><br /> (MD_Metadata.identificationInfo > SV_ServiceIdentification.pointOfContact > CI_Responsibility)</td>
 
                 <td valign="top"><b>Responsible party: (O/N)</b><br /> (MD_Metadata.identificationInfo > SV_ServiceIdentification.pointOfContact > CI_Responsibility)</td>
                 <td valign="top"><b>Geographic location: (C)</b><br /> (MD_Metadata.identificationInfo > SV_ServiceIdentification.extent > EX_Extent.geographicElement > EX_GeographicExtent > EX_GeographicBoundingBox –or- EX_GeographicDescription)</td>
+
                 <td valign="top"><b>Geographic location: (M/1)</b><br /> (MD_Metadata.identificationInfo > SV_ServiceIdentification.extent > EX_Extent.geographicElement > EX_GeographicExtent > EX_GeographicBoundingBox –or- EX_GeographicDescription)</td>
 
             </tr>
 
             </tr>
 
             <tr>
 
             <tr>
Line 31: Line 31:
 
             <tr>
 
             <tr>
 
                 <td valign="top"><b>Coupled Resource: (C)</b><br /> (MD_Metadata>SV_ServiceIdentification.coupledResource>SV-CoupledResource)</td>
 
                 <td valign="top"><b>Coupled Resource: (C)</b><br /> (MD_Metadata>SV_ServiceIdentification.coupledResource>SV-CoupledResource)</td>
                 <td valign="top"><b>Coupled resource type: (C)</b><br /> (MD_Metadata.identificationInfo>MD_DataIdentification>MD_Constraints.useLimitations and/or MD_LegalConstraints and/or MD_SecurityConstraints)</td>
+
                 <td valign="top"><b>Coupled resource type: (C)</b><br /> (MD_Metadata>SV_ServiceIdentification.couplingType>SV-CouplingType)</td>
 
             </tr>
 
             </tr>
 
         </table>
 
         </table>
 
[[Category:Documentation Connections]]
 
[[Category:Documentation Connections]]

Revision as of 11:13, October 31, 2014

Metadata reference information: (O/1)
(MD_Metadata.metadataIdentifier)
Service title: (M/1)
(MD_Metadata .identificationInfo > SV_ServiceIdentification.citation > CI_Citation.title)
Reference date: (O/1)
(MD_Metadata.identificationInfo > SV_ServiceIdentification.citation > CI_Citation.date)
Resource identifier: (O/N)
(MD_Metadata.identificationInfo>SV_ServiceIdentification.citation > CI_Citation.identifier>MD_Identifier)
Responsible party: (O/N)
(MD_Metadata.identificationInfo > SV_ServiceIdentification.pointOfContact > CI_Responsibility)
Geographic location: (M/1)
(MD_Metadata.identificationInfo > SV_ServiceIdentification.extent > EX_Extent.geographicElement > EX_GeographicExtent > EX_GeographicBoundingBox –or- EX_GeographicDescription)
valign="top">Service topic category: (O/N)
(MD_Metadata.identificationInfo > SV_ServiceIdentification.topicCategory > MD_TopicCategoryCode)
Resource Abstract: (M/1)
(MD_Metadata.identificationInfo >SV_ServiceIdentification.abstract)
On-line Link: (O/N)
(MD_Metadata.identificationInfo >SV_ServiceIdentification.citation>CI_Citation.onlineResource>CI_OnlineResource)
Keywords: (O/N)
MD_Metadata.identificationInfo >SV_ServiceIdentification>MD_Keywords)
Constraints on access and use: (O/N)
MD_Metadata>SV_ServiceIdentification>MD_Constraints.useLimitations and/or MD_LegalConstraints and or MD_SecurityConstraints
Metadata date stamp: (M/N)
(MD_Metadata.dateInfo)
Metadata point of contact: (M/N)
(MD_Metadata.contact > CI_Responsibility))
Resource type: (M/1)
MD_Metadata.metadataScope> MD_Scope.resourceScope)
Coupled Resource: (C)
(MD_Metadata>SV_ServiceIdentification.coupledResource>SV-CoupledResource)
Coupled resource type: (C)
(MD_Metadata>SV_ServiceIdentification.couplingType>SV-CouplingType)