Difference between revisions of "SV ServiceIdentification"

From Earth Science Information Partners (ESIP)
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Image:SV_ServiceIdentification.png|thumb|right|Service Information]]  
+
[[Image:SV_ServiceIdentification.png|thumb|right|SV_ServiceIdentification]]  
 
+
== srv:SV_ServiceIdentification ==
 
+
Identification of capabilities which a service provider makes available to a service user through a set of interfaces that define a behaviour
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
<div id="elementsAndDefinitions"> <!--elements, definitions, and examples for class: SV_ServiceIdentification--> <table cellpadding="3" width="100%"> <tr> <th colspan="3">Elements</th> <th width="60%"> <i>Definition and Recommended Practice</i> </th> <th width="20%"> <pre>Examples</pre> </th> </tr> <tr> <td bgcolor="FFFF99">1</td> <td bgcolor="FFFF99">[[CI_Citation|citation]]</td> <td bgcolor="FFFF99">1</td> <td> <i>Citation for the resource, includes name, publication date, identifiers, originators and publishers.</i> </td> <td> <!--No example found: AbstractMD_Identification/citation Type: Abstract_Citation--> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="FFFF99">2</td> <td bgcolor="FFFF99">[[CharacterString|abstract]]</td> <td bgcolor="FFFF99">1</td> <td> <i>Brief narrative summary of the resource contents. Include summary information on general content and features; resource applications: GIS, CAD, image, database; geographic coverage: county/city name; time period of content: begin and end date or single date; and special data characteristics or limitations.</i> </td> <td> <!--No example found: AbstractMD_Identification/abstract Type: CharacterString--> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="CCFFFF">3</td> <td bgcolor="CCFFFF">[[CharacterString|purpose]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Summary of intentions for which the resource was developed.</i> </td> <td> <!--No example found: AbstractMD_Identification/purpose Type: CharacterString--> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="CCFFFF">4</td> <td bgcolor="CCFFFF">[[CharacterString|credit]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Recognition of those who contributed to the dataset. Do not include URLs here. Provide full citations in MD_AssociatedResource section.</i> </td> <td> <!--No example found: AbstractMD_Identification/credit Type: CharacterString--> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="CCFFFF">5</td> <td bgcolor="CCFFFF">[[ISO_19115_and_19115-2_CodeList_Dictionaries#MD_ProgressCode|status]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Status of resource development. Most common status values to use are 'completed', 'ongoing', 'planned' or 'underDevelopment'. Highly recommend populating this field.</i> </td> <td> <!--No example found: AbstractMD_Identification/status Type: MD_ProgressCode--> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="CCFFFF">6</td> <td bgcolor="CCFFFF">[[CI_Responsibility|pointOfContact]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Individuals and/or organizations available for questions about the resource. Use roleCode="pointOfContact". This should be a person at an archive or the originator of the resource. Provide contact details, such address, phone and email.</i> </td> <td> <!--No example found: AbstractMD_Identification/pointOfContact Type: Abstract_Responsibility--> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="CCFFFF">14</td> <td bgcolor="CCFFFF">[[MD_MaintenanceInformation|resourceMaintenance]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Information about the frequency, scope, and responsible party for the updating of the resource.</i> </td> <td> <!--No example found: AbstractMD_Identification/resourceMaintenance Type: Abstract_MaintenanceInformation--> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="CCFFFF">15</td> <td bgcolor="CCFFFF">[[MD_BrowseGraphic|graphicOverview]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>A small image that exemplifies the collective resource. The graphic file should be less than 500KB and 1000x1000 pixels. Provide URL to an image that can be rendered in browsers.</i> </td> <td> <!--No example found: AbstractMD_Identification/graphicOverview Type: MD_BrowseGraphic--> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="CCFFFF">16</td> <td bgcolor="CCFFFF">[[resourceFormat]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Information about the formats of the resource. This is independant of the distribution details and is useful to provide when the resource has a status of 'planned' or 'underDevelopment'.</i> </td> <td> <!--No example found: AbstractMD_Identification/resourceFormat Type: Abstract_Format--> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="CCFFFF">17</td> <td bgcolor="CCFFFF">[[MD_Keywords|descriptiveKeywords]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Commonly used words or phrases which describe the dataset. Optionally, the keyword type and a citation for the authoritative or registered resource of the keywords are also provided.</i> </td> <td> <!--No example found: AbstractMD_Identification/descriptiveKeywords Type: MD_Keywords--> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="CCFFFF">18</td> <td bgcolor="CCFFFF">[[MD_Usage|resourceSpecificUsage]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Basic information about specific application(s) for which the resource(s) has been or is being used by different users.</i> </td> <td> <!--No example found: AbstractMD_Identification/resourceSpecificUsage Type: MD_Usage--> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="CCFFFF">19</td> <td bgcolor="CCFFFF">[[MD_Constrains|resourceConstraints]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>The limitations or constraints on the use of or access to the resource.</i> </td> <td> <!--No example found: AbstractMD_Identification/resourceConstraints Type: Abstract_Constraints--> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="CCFFFF">20</td> <td bgcolor="CCFFFF">[[MD_AssociatedResource|associatedResource]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>The citations and identifiers of associated resources, such as projects and documents.</i> </td> <td> <!--No example found: AbstractMD_Identification/associatedResource Type: MD_AssociatedResource--> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="FFFF99">1</td> <td bgcolor="FFFF99">[[GenericName|serviceType]]</td> <td bgcolor="FFFF99">1</td> <td> <i>A term for describing the type of service. For example 'discovery', 'view', 'download', 'transformation', or 'invoke'.</i> </td> <td> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="CCFFFF">2</td> <td bgcolor="CCFFFF">[[CharacterString|serviceTypeVersion]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>The service type version. For example, we may only be interested in OGC Catalogue V1.1 services. If the version is maintained as a separate attribute, users can easily search for all services of a type regardless of the version</i> </td> <td> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="CCFFFF">3</td> <td bgcolor="CCFFFF">[[MD_StandardOrderProcess|accessProperties]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Service access information such as fees, availability, ordering instructions, turnaround time, etc.</i> </td> <td> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="CCFFFF">4</td> <td bgcolor="CCFFFF">[[SV_CouplingType|couplingType]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>The type of coupling between service and associated data.</i> </td> <td> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="CCFFFF">5</td> <td bgcolor="CCFFFF">[[SV_CoupledResource|coupledResource]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>A more detailed description of the data coupling in the case of tightly coupled services.</i> </td> <td> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="CCFFFF">6</td> <td bgcolor="CCFFFF">[[CI_Citation|operatedDataset]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>A reference to the dataset on which the service operates.</i> </td> <td> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="CCFFFF">7</td> <td bgcolor="CCFFFF">[[CI_Citation|profile]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Definition needed</i> </td> <td> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="CCFFFF">8</td> <td bgcolor="CCFFFF">[[Abstract_Citation|serviceStandard]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Definition needed</i> </td> <td> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="CCFFFF">9</td> <td bgcolor="CCFFFF">[[SV_OperationMetadata|containsOperations]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Definition needed</i> </td> <td> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="CCFFFF">10</td> <td bgcolor="CCFFFF">[[MD_DataIdentification|operatesOn]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Definition needed</i> </td> <td> <pre>Example is needed</pre> </td> </tr> <tr> <td bgcolor="CCFFFF">11</td> <td bgcolor="CCFFFF">[[SV_OperationChainMetadata|containsChain]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Definition needed</i> </td> <td> <pre>Example is needed</pre> </td> </tr> </table> </div>
 
  
 +
<div id="elementsAndDefinitionsManual">
 +
<!--elements, definitions, and examples for class: SV_ServiceIdentification-->
 +
<table cellpadding="3" width="100%">
 +
<tr>
 +
<th colspan="3">Elements</th>
 +
<th width="10%">Domain</th>
 +
<th width="50%">Definition and Recommended Practice</th>
 +
<th width="30%"><i>Examples</i></th>
 +
</tr>
 +
<tr>
 +
<td bgcolor="FFFF99">1</td>
 +
<td bgcolor="FFFF99">[[CI_Citation|srv:citation]]</td>
 +
<td bgcolor="FFFF99">1</td>
 +
<td bgcolor="FFFF99">[[CI_Citation|cit:CI_Citation]]</td>
 +
<td>Citation for the resource, includes name, publication date, identifiers, originators and publishers.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="FFFF99">2</td>
 +
<td bgcolor="FFFF99">[[CharacterString|srv:abstract]]</td>
 +
<td bgcolor="FFFF99">1</td>
 +
<td bgcolor="FFFF99">[[CharacterString|gco:CharacterString]]</td>
 +
<td>Brief narrative summary of the resource contents. Include summary information on general content and features; resource applications: GIS, CAD, image, database; geographic coverage: county/city name; time period of content: begin and end date or single date; and special data characteristics or limitations.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFFFF">3</td>
 +
<td bgcolor="CCFFFF">[[CharacterString|srv:purpose]]</td>
 +
<td bgcolor="CCFFFF">0..1</td>
 +
<td bgcolor="CCFFFF">[[CharacterString|gco:CharacterString]]</td>
 +
<td>Summary of intentions for which the resource was developed.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFFFF">4</td>
 +
<td bgcolor="CCFFFF">[[CharacterString|srv:credit]]</td>
 +
<td bgcolor="CCFFFF">0..*</td>
 +
<td bgcolor="CCFFFF">[[CharacterString|gco:CharacterString]]</td>
 +
<td>Recognition of those who contributed to the dataset. Do not include URLs here. Provide full citations in MD_AssociatedResource section.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFFFF">5</td>
 +
<td bgcolor="CCFFFF">[[ISO 19115 and 19115-2 CodeList Dictionaries#MD_ProgressCode|srv:status]]</td>
 +
<td bgcolor="CCFFFF">0..*</td>
 +
<td bgcolor="CCFFFF">[[ISO 19115 and 19115-2 CodeList Dictionaries#MD_ProgressCode|mcc:MD_ProgressCode]]</td>
 +
<td>Status of resource development. Most common status values to use are 'completed', 'ongoing', 'planned' or 'underDevelopment'. Highly recommend populating this field.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFFFF">6</td>
 +
<td bgcolor="CCFFFF">[[CI_Responsibility|srv:pointOfContact]]</td>
 +
<td bgcolor="CCFFFF">0..*</td>
 +
<td bgcolor="CCFFFF">[[CI_Responsibility|cit:CI_Responsibility]]</td>
 +
<td>Individuals and/or organizations available for questions about the resource. Use roleCode="pointOfContact". This should be a person at an archive or the originator of the resource. Provide contact details, such address, phone and email.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFFFF">7</td>
 +
<td bgcolor="CCFFFF">[[ISO 19115 and 19115-2 CodeList Dictionaries#MD_SpatialRepresentationTypeCode|srv:spatialRepresentationType]]</td>
 +
<td bgcolor="CCFFFF">0..*</td>
 +
<td bgcolor="CCFFFF">[[ISO 19115 and 19115-2 CodeList Dictionaries#MD_SpatialRepresentationTypeCode|mcc:MD_SpatialRepresentationTypeCode]]</td>
 +
<td>Object(s) used to represent the geographic information.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFFFF">8</td>
 +
<td bgcolor="CCFFFF">[[MD_Resolution|srv:spatialResolution]]</td>
 +
<td bgcolor="CCFFFF">0..*</td>
 +
<td bgcolor="CCFFFF">[[MD_Resolution|mri:MD_Resolution]]</td>
 +
<td>The spatial resolution (level of spatial detail) of the dataset.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFFFF">9</td>
 +
<td bgcolor="CCFFFF">[[TM_PeriodDuration|srv:temporalResolution]]</td>
 +
<td bgcolor="CCFFFF">0..*</td>
 +
<td bgcolor="CCFFFF">[[TM_PeriodDuration|gco:TM_PeriodDuration]]</td>
 +
<td>The temporal resolution (level of temporal detail) of the dataset.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFFFF">10</td>
 +
<td bgcolor="CCFFFF">[[ISO 19115 and 19115-2 CodeList Dictionaries#MD_TopicCategoryCode|srv:topicCategory]]</td>
 +
<td bgcolor="CCFFFF">0..*</td>
 +
<td bgcolor="CCFFFF">[[ISO 19115 and 19115-2 CodeList Dictionaries#MD_TopicCategoryCode|mri:MD_TopicCategoryCode]]</td>
 +
<td>Main theme(s) of the resource</td>
 +
<td><i></i></td>
 +
<tr>
 +
<td bgcolor="CCFFFF">11</td>
 +
<td bgcolor="CCFFFF">[[EX_Extent|srv:extent]]</td>
 +
<td bgcolor="CCFFFF">0..*</td>
 +
<td bgcolor="CCFFFF">[[EX_Extent|gex:EX_Extent]]</td>
 +
<td>High-level thematic classifications to assist in the grouping and searching of data. Required when the hierarchyLevelName scopeCode is 'dataset'. Recommended when hierarchyLevelName scopeCode is 'series', 'fieldSession', or 'nonGeographicDataset'. The most applicable topics in NOAA are usually geoscientificInformation, climatologyMeteorologyAtmosphere, oceans or elevation. Repeat if more than one category is applicable. Keep the capitalization and spacing of the terms.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFFFF">12</td>
 +
<td bgcolor="CCFFFF">[[CI_Citation|srv:additionalDocumentation]]</td>
 +
<td bgcolor="CCFFFF">0..*</td>
 +
<td bgcolor="CCFFFF">[[CI_Citation|cit:CI_Citation]]</td>
 +
<td>Additional documentation related to the resource such as publications and users guides.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFFFF">13</td>
 +
<td bgcolor="CCFFFF">[[MD_Identifier|srv:processingLevel]]</td>
 +
<td bgcolor="CCFFFF">0..1</td>
 +
<td bgcolor="CCFFFF">[[MD_Identifier|mcc:MD_Identifier]]</td>
 +
<td>An identifier code that identifies the level of processing in the producers coding system.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFFFF">14</td>
 +
<td bgcolor="CCFFFF">[[MD_MaintenanceInformation|srv:resourceMaintenance]]</td>
 +
<td bgcolor="CCFFFF">0..*</td>
 +
<td bgcolor="CCFFFF">[[MD_MaintenanceInformation|mmi:MD_MaintenanceInformation]]</td>
 +
<td>Information about the frequency, scope, and responsible party for the updating of the resource.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFFFF">15</td>
 +
<td bgcolor="CCFFFF">[[MD_BrowseGraphic|srv:graphicOverview]]</td>
 +
<td bgcolor="CCFFFF">0..*</td>
 +
<td bgcolor="CCFFFF">[[MD_BrowseGraphic|mcc:MD_BrowseGraphic]]</td>
 +
<td>A small image that exemplifies the collective resource. The graphic file should be less than 500KB and 1000x1000 pixels. Provide URL to an image that can be rendered in browsers.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFFFF">16</td>
 +
<td bgcolor="CCFFFF">[[MD_Format|srv:resourceFormat]]</td>
 +
<td bgcolor="CCFFFF">0..*</td>
 +
<td bgcolor="CCFFFF">[[MD_Format|mrd:MD_Format]]</td>
 +
<td>Information about the formats of the resource. This is independant of the distribution details and is useful to provide when the resource has a status of 'planned' or 'underDevelopment'.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFFFF">17</td>
 +
<td bgcolor="CCFFFF">[[MD_Keywords|srv:descriptiveKeywords]]</td>
 +
<td bgcolor="CCFFFF">0..*</td>
 +
<td bgcolor="CCFFFF">[[MD_Keywords|mri:MD_Keywords]]</td>
 +
<td>Commonly used words or phrases which describe the dataset. Optionally, the keyword type and a citation for the authoritative or registered resource of the keywords are also provided.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFFFF">18</td>
 +
<td bgcolor="CCFFFF">[[MD_Usage|srv:resourceSpecificUsage]]</td>
 +
<td bgcolor="CCFFFF">0..*</td>
 +
<td bgcolor="CCFFFF">[[MD_Usage|mri:MD_Usage]]</td>
 +
<td>Basic information about specific application(s) for which the resource(s) has been or is being used by different users.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFFFF">19</td>
 +
<td bgcolor="CCFFFF">[[MD_Constraints|srv:resourceConstraints]]</td>
 +
<td bgcolor="CCFFFF">0..*</td>
 +
<td bgcolor="CCFFFF">[[MD_Constraints|mco:MD_Constraints]]</td>
 +
<td>The limitations or constraints on the use of or access to the resource.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFFFF">20</td>
 +
<td bgcolor="CCFFFF">[[MD_AssociatedResource|srv:associatedResource]]</td>
 +
<td bgcolor="CCFFFF">0..*</td>
 +
<td bgcolor="CCFFFF">[[MD_AssociatedResource|mri:MD_AssociatedResource]]</td>
 +
<td>The citations and identifiers of associated resources, such as projects and documents.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="FFFF99">21</td>
 +
<td bgcolor="FFFF99">[[GenericName|srv:serviceType]]</td>
 +
<td bgcolor="FFFF99">1</td>
 +
<td bgcolor="FFFF99">[[GenericName|gco:GenericName]]</td>
 +
<td>A term for describing the type of service. For example 'discovery', 'view', 'download', 'transformation', or 'invoke'.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFFFF">22</td>
 +
<td bgcolor="CCFFFF">[[CharacterString|srv:serviceTypeVersion]]</td>
 +
<td bgcolor="CCFFFF">0..*</td>
 +
<td bgcolor="CCFFFF">[[CharacterString|gco:CharacterString]]</td>
 +
<td>The service type version. For example, we may only be interested in OGC Catalogue V1.1 services. If the version is maintained as a separate attribute, users can easily search for all services of a type regardless of the version</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFFFF">23</td>
 +
<td bgcolor="CCFFFF">[[MD_StandardOrderProcess|srv:accessProperties]]</td>
 +
<td bgcolor="CCFFFF">0..1</td>
 +
<td bgcolor="CCFFFF">[[MD_StandardOrderProcess|mrd:MD_StandardOrderProcess]]</td>
 +
<td>Service access information such as fees, availability, ordering instructions, turnaround time, etc.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFF99">24</td>
 +
<td bgcolor="CCFF99">[[ISO_19115-3_Codelists#SV_CouplingType|srv:couplingType]]</td>
 +
<td bgcolor="CCFF99">0..1</td>
 +
<td bgcolor="CCFF99">[[ISO_19115-3_Codelists#SV_CouplingType|srv:SV_CouplingType]]</td>
 +
<td><i>Mandatory if srv:coupleResource is present.</i><br>The type of coupling between service and associated data.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFF99">25</td>
 +
<td bgcolor="CCFF99">[[SV_CoupledResource|srv:coupledResource]]</td>
 +
<td bgcolor="CCFF99">0..*</td>
 +
<td bgcolor="CCFF99">[[SV_CoupledResource|srv:SV_CoupledResource]]</td>
 +
<td><i>Mandatory if srv:couplingType is present.</i><br>A more detailed description of the data coupling in the case of tightly coupled services.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFF99">26</td>
 +
<td bgcolor="CCFF99">[[CI_Citation|srv:operatedDataset]]</td>
 +
<td bgcolor="CCFF99">0..*</td>
 +
<td bgcolor="CCFF99">[[CI_Citation|cit:CI_Citation]]</td>
 +
<td><i>Mandatory if srv:operatesOn is present.</i><br>A reference to the dataset on which the service operates.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFFFF">27</td>
 +
<td bgcolor="CCFFFF">[[CI_Citation|srv:profile]]</td>
 +
<td bgcolor="CCFFFF">0..*</td>
 +
<td bgcolor="CCFFFF">[[CI_Citation|cit:CI_Citation]]</td>
 +
<td>Citation to metadata profile.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFFFF">28</td>
 +
<td bgcolor="CCFFFF">[[CI_Citation|srv:serviceStandard]]</td>
 +
<td bgcolor="CCFFFF">0..*</td>
 +
<td bgcolor="CCFFFF">[[CI_Citation|cit:CI_Citation]]</td>
 +
<td>Citation to metadata standard.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFF99">29</td>
 +
<td bgcolor="CCFF99">[[SV_OperationMetadata|srv:containsOperations]]</td>
 +
<td bgcolor="CCFF99">0..*</td>
 +
<td bgcolor="CCFF99">[[SV_OperationMetadata|srv:SV_OperationMetadata]]</td>
 +
<td><i>Mandatory if srv:containsChain not present.</i><br>Description of the operations supported by the service.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFF99">30</td>
 +
<td bgcolor="CCFF99">[[MD_DataIdentification|srv:operatesOn]]</td>
 +
<td bgcolor="CCFF99">0..*</td>
 +
<td bgcolor="CCFF99">[[MD_DataIdentification|mri:MD_DataIdentification]]</td>
 +
<td><i>Mandatory if srv:operatedDataset is present.</i><br>Descriptive information regarding the datasets that the service operates on.</td>
 +
<td><i></i></td>
 +
</tr>
 +
<tr>
 +
<td bgcolor="CCFF99">31</td>
 +
<td bgcolor="CCFF99">[[SV_OperationChainMetadata|srv:containsChain]]</td>
 +
<td bgcolor="CCFF99">0..*</td>
 +
<td bgcolor="CCFF99">[[SV_OperationChainMetadata|srv:SV_OperationChainMetadata]]</td>
 +
<td><i>Mandatory if srv:containsOperations not present.</i><br></td>
 +
<td><i></i></td>
 +
</tr>
 +
</table>
 +
</div>
 +
<br>
 
{{template:isoOrderingFooter}}  
 
{{template:isoOrderingFooter}}  
 
 
 
[[Category:ISO_19119]]
 
[[Category:ISO_19119]]

Latest revision as of 10:23, August 28, 2017

SV_ServiceIdentification

srv:SV_ServiceIdentification

Identification of capabilities which a service provider makes available to a service user through a set of interfaces that define a behaviour

Elements Domain Definition and Recommended Practice Examples
1 srv:citation 1 cit:CI_Citation Citation for the resource, includes name, publication date, identifiers, originators and publishers.
2 srv:abstract 1 gco:CharacterString Brief narrative summary of the resource contents. Include summary information on general content and features; resource applications: GIS, CAD, image, database; geographic coverage: county/city name; time period of content: begin and end date or single date; and special data characteristics or limitations.
3 srv:purpose 0..1 gco:CharacterString Summary of intentions for which the resource was developed.
4 srv:credit 0..* gco:CharacterString Recognition of those who contributed to the dataset. Do not include URLs here. Provide full citations in MD_AssociatedResource section.
5 srv:status 0..* mcc:MD_ProgressCode Status of resource development. Most common status values to use are 'completed', 'ongoing', 'planned' or 'underDevelopment'. Highly recommend populating this field.
6 srv:pointOfContact 0..* cit:CI_Responsibility Individuals and/or organizations available for questions about the resource. Use roleCode="pointOfContact". This should be a person at an archive or the originator of the resource. Provide contact details, such address, phone and email.
7 srv:spatialRepresentationType 0..* mcc:MD_SpatialRepresentationTypeCode Object(s) used to represent the geographic information.
8 srv:spatialResolution 0..* mri:MD_Resolution The spatial resolution (level of spatial detail) of the dataset.
9 srv:temporalResolution 0..* gco:TM_PeriodDuration The temporal resolution (level of temporal detail) of the dataset.
10 srv:topicCategory 0..* mri:MD_TopicCategoryCode Main theme(s) of the resource
11 srv:extent 0..* gex:EX_Extent High-level thematic classifications to assist in the grouping and searching of data. Required when the hierarchyLevelName scopeCode is 'dataset'. Recommended when hierarchyLevelName scopeCode is 'series', 'fieldSession', or 'nonGeographicDataset'. The most applicable topics in NOAA are usually geoscientificInformation, climatologyMeteorologyAtmosphere, oceans or elevation. Repeat if more than one category is applicable. Keep the capitalization and spacing of the terms.
12 srv:additionalDocumentation 0..* cit:CI_Citation Additional documentation related to the resource such as publications and users guides.
13 srv:processingLevel 0..1 mcc:MD_Identifier An identifier code that identifies the level of processing in the producers coding system.
14 srv:resourceMaintenance 0..* mmi:MD_MaintenanceInformation Information about the frequency, scope, and responsible party for the updating of the resource.
15 srv:graphicOverview 0..* mcc:MD_BrowseGraphic A small image that exemplifies the collective resource. The graphic file should be less than 500KB and 1000x1000 pixels. Provide URL to an image that can be rendered in browsers.
16 srv:resourceFormat 0..* mrd:MD_Format Information about the formats of the resource. This is independant of the distribution details and is useful to provide when the resource has a status of 'planned' or 'underDevelopment'.
17 srv:descriptiveKeywords 0..* mri:MD_Keywords Commonly used words or phrases which describe the dataset. Optionally, the keyword type and a citation for the authoritative or registered resource of the keywords are also provided.
18 srv:resourceSpecificUsage 0..* mri:MD_Usage Basic information about specific application(s) for which the resource(s) has been or is being used by different users.
19 srv:resourceConstraints 0..* mco:MD_Constraints The limitations or constraints on the use of or access to the resource.
20 srv:associatedResource 0..* mri:MD_AssociatedResource The citations and identifiers of associated resources, such as projects and documents.
21 srv:serviceType 1 gco:GenericName A term for describing the type of service. For example 'discovery', 'view', 'download', 'transformation', or 'invoke'.
22 srv:serviceTypeVersion 0..* gco:CharacterString The service type version. For example, we may only be interested in OGC Catalogue V1.1 services. If the version is maintained as a separate attribute, users can easily search for all services of a type regardless of the version
23 srv:accessProperties 0..1 mrd:MD_StandardOrderProcess Service access information such as fees, availability, ordering instructions, turnaround time, etc.
24 srv:couplingType 0..1 srv:SV_CouplingType Mandatory if srv:coupleResource is present.
The type of coupling between service and associated data.
25 srv:coupledResource 0..* srv:SV_CoupledResource Mandatory if srv:couplingType is present.
A more detailed description of the data coupling in the case of tightly coupled services.
26 srv:operatedDataset 0..* cit:CI_Citation Mandatory if srv:operatesOn is present.
A reference to the dataset on which the service operates.
27 srv:profile 0..* cit:CI_Citation Citation to metadata profile.
28 srv:serviceStandard 0..* cit:CI_Citation Citation to metadata standard.
29 srv:containsOperations 0..* srv:SV_OperationMetadata Mandatory if srv:containsChain not present.
Description of the operations supported by the service.
30 srv:operatesOn 0..* mri:MD_DataIdentification Mandatory if srv:operatedDataset is present.
Descriptive information regarding the datasets that the service operates on.
31 srv:containsChain 0..* srv:SV_OperationChainMetadata Mandatory if srv:containsOperations not present.




ISO Legend

Possible Parent Elements

ESIP-logo-tag sm-H.jpg

Please contribute!