Difference between revisions of "Service Identification"

From DGIWG
Jump to: navigation, search
Line 1: Line 1:
−
<div style="color:#000000;">The following metadata elements are only applicable to services.</div>
 
−
 
−
<div style="color:#000000;">A service instance may be either tightly coupled with a dataset instance, loosely coupled (i.e. non associated with specific dataset instances), or it may be “mixed coupled.”</div>
 
−
 
−
<div style="color:#000000;">In the tightly coupled case, the service metadata shall describe both the service and the geographic dataset. Dataset metadata need not be provided in the service metadata for the loosely coupled case. Information about data could be given either with SROPRS or SRCORS.</div>
 
−
 
−
 
  
  
Line 16: Line 9:
 
| align=center style="border-top:1pt outset #000000;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;" | '''Card'''
 
| align=center style="border-top:1pt outset #000000;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;" | '''Card'''
 
| align=center style="border-top:1pt outset #000000;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;" | '''Condition'''
 
| align=center style="border-top:1pt outset #000000;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;" | '''Condition'''
−
| align=center style="border-top:1pt outset #000000;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;" | '''Metadata classes'''
+
| align=center style="border-top:1pt outset #000000;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;" | '''Specific mapping notes'''
 
| align=center style="border-top:1pt outset #000000;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;" | '''Guidelines'''
 
| align=center style="border-top:1pt outset #000000;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;" | '''Guidelines'''
 
| align=center style="border:1pt outset #000000;padding:0.101cm;" | '''Example'''
 
| align=center style="border:1pt outset #000000;padding:0.101cm;" | '''Example'''
Line 31: Line 24:
 
| align=center style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | 1
 
| align=center style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | 1
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | &nbsp;
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | &nbsp;
−
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | DMF/Services extends DMF/Core for service metadata and can be used together with DMF/Common (i.e. it is possible to use DMF/Services on top of DMF/Core (if DMF/Common elements are not needed) or on top of DMF/Common for an extensive profile).
+
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" |  
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | For OGC Web Services, the value defined by the applicable OGC Specification has to be used (e.g. 'WMS', WFS', 'CSW', 'WMTS', ... )
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | For OGC Web Services, the value defined by the applicable OGC Specification has to be used (e.g. 'WMS', WFS', 'CSW', 'WMTS', ... )
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:1pt outset #000000;padding:0.101cm;color:#000000;" | &nbsp;
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:1pt outset #000000;padding:0.101cm;color:#000000;" | &nbsp;
Line 46: Line 39:
 
| align=center style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | 1
 
| align=center style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | 1
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | &nbsp;
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | &nbsp;
−
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | DMF/Services extends DMF/Core for service metadata and can be used together with DMF/Common (i.e. it is possible to use DMF/Services on top of DMF/Core (if DMF/Common elements are not needed) or on top of DMF/Common for an extensive profile).
+
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" |  
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | For OGC Web Services, the value defined by the applicable OGC Specification has to be used.
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | For OGC Web Services, the value defined by the applicable OGC Specification has to be used.
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:1pt outset #000000;padding:0.101cm;color:#000000;" | &nbsp;
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:1pt outset #000000;padding:0.101cm;color:#000000;" | &nbsp;
Line 59: Line 52:
 
| align=center style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | 0..1
 
| align=center style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | 0..1
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | &nbsp;
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | &nbsp;
−
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | DMF/Services extends DMF/Core for service metadata and can be used together with DMF/Common (i.e. it is possible to use DMF/Services on top of DMF/Core (if DMF/Common elements are not needed) or on top of DMF/Common for an extensive profile).
+
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" |  
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | This element can be used to mention to which DGIWG profile the service is compliant with.
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | This element can be used to mention to which DGIWG profile the service is compliant with.
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:1pt outset #000000;padding:0.101cm;color:#000000;" | &nbsp;
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:1pt outset #000000;padding:0.101cm;color:#000000;" | &nbsp;
Line 74: Line 67:
 
| align=center style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | 1
 
| align=center style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | 1
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | &nbsp;
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | &nbsp;
−
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | DMF/Services extends DMF/Core for service metadata and can be used together with DMF/Common (i.e. it is possible to use DMF/Services on top of DMF/Core (if DMF/Common elements are not needed) or on top of DMF/Common for an extensive profile).
+
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" |  
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | &nbsp;
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | &nbsp;
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:1pt outset #000000;padding:0.101cm;color:#000000;" | &nbsp;
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:1pt outset #000000;padding:0.101cm;color:#000000;" | &nbsp;
Line 91: Line 84:
 
<div style="color:#000000;">(URI of the metadata of the dataset on which the service operates.)</div>
 
<div style="color:#000000;">(URI of the metadata of the dataset on which the service operates.)</div>
 
| align=center style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | 0..*
 
| align=center style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | 0..*
−
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | ''Mandatory if coupling type is tight or mixed.''
+
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | Mandatory if coupling type is tight or mixed.
−
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | ''DMF/Services extends DMF/Core for service metadata and can be used together with DMF/Common (i.e. it is possible to use DMF/Services on top of DMF/Core (if DMF/Common elements are not needed) or on top of DMF/Common for an extensive profile).''
+
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | The domain value of SROPRS is the URI of the metadata of the dataset on which the service operates. Mandatory when coupling type is tight or mixed. For one resource either operatedDataset or operatesOn may be used (not both for the same resource)''.''
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | &nbsp;
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | &nbsp;
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:1pt outset #000000;padding:0.101cm;color:#000000;" | &nbsp;
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:1pt outset #000000;padding:0.101cm;color:#000000;" | &nbsp;
Line 105: Line 98:
 
| align=center style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | 1..*
 
| align=center style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | 1..*
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | &nbsp;
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | &nbsp;
−
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | DMF/Services extends DMF/Core for service metadata and can be used together with DMF/Common (i.e. it is possible to use DMF/Services on top of DMF/Core (if DMF/Common elements are not needed) or on top of DMF/Common for an extensive profile).
+
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" |  
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | &nbsp;
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | &nbsp;
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:1pt outset #000000;padding:0.101cm;color:#000000;" | &nbsp;
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:1pt outset #000000;padding:0.101cm;color:#000000;" | &nbsp;
Line 114: Line 107:
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;" | <div style="color:#000000;"><u>Service Coupled Resource</u></div>
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;" | <div style="color:#000000;"><u>Service Coupled Resource</u></div>
  
−
<div style="color:#000000;">Further description of the data coupling in the case of tightly coupled services. It links a given operationName with a data set identified by an “identifier". And it requires that a given operationName or identifier shall refer to an existing operationName given by SROPER.name or an identifier given by RSID.code, respectively.</div>
+
<span style="color:#000000;">Further description of the data coupling in the case of tightly coupled services. It links a given operationName with a data set identified by an “identifier". And it requires that a given operationName or identifier shall refer to an existing operationName given by SROPER.name or an identifier given by RSID.code, respectively.</span>
−
 
 
−
 
 
−
 
 
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;" | [https://eden.ign.fr/wiki/index.php/Service_Coupling Service Coupling]
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;" | [https://eden.ign.fr/wiki/index.php/Service_Coupling Service Coupling]
 
| align=center style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | 0..*
 
| align=center style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | 0..*
−
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | ''Only applicable to tightly coupled services.''
+
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | Only applicable to tightly coupled services.
−
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | ''DMF/Services extends DMF/Core for service metadata and can be used together with DMF/Common (i.e. it is possible to use DMF/Services on top of DMF/Core (if DMF/Common elements are not needed) or on top of DMF/Common for an extensive profile).''
+
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" |  
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | &nbsp;
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:none;padding:0.101cm;color:#000000;" | &nbsp;
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:1pt outset #000000;padding:0.101cm;color:#000000;" | &nbsp;
 
| style="border-top:none;border-bottom:1pt outset #000000;border-left:1pt outset #000000;border-right:1pt outset #000000;padding:0.101cm;color:#000000;" | &nbsp;
 +
|-
 +
|}
 +
 +
 +
 +
{| style="border-spacing:0;margin:auto;width:37.999cm;"
 +
|-
 +
| style="background-color:transparent;border-top:0.5pt solid #000000;border-bottom:0.5pt solid #000000;border-left:0.5pt solid #000000;border-right:none;padding:0.097cm;color:#000000;" | DMF/Core
 +
| style="background-color:transparent;border:0.5pt solid #000000;padding:0.097cm;color:#000000;" | DMF/Core defines the minimum set of metadata elements to be implemented by any metadata catalogue. This set satisfies the discovery use case.
 +
|-
 +
| style="background-color:transparent;border-top:none;border-bottom:0.5pt solid #000000;border-left:0.5pt solid #000000;border-right:none;padding:0.097cm;color:#000000;" | DMF/Common
 +
| style="background-color:transparent;border-top:none;border-bottom:0.5pt solid #000000;border-left:0.5pt solid #000000;border-right:0.5pt solid #000000;padding:0.097cm;color:#000000;" | DMF/Common is an additional set of metadata elements for a more complete description of any type of resource supported by DMF. It extends DMF/Core and covers discovery and basic evaluation use cases.
 +
|-
 +
| style="background-color:transparent;border-top:none;border-bottom:0.5pt solid #000000;border-left:0.5pt solid #000000;border-right:none;padding:0.097cm;color:#000000;" | DMF/Service
 +
| style="background-color:transparent;border-top:none;border-bottom:0.5pt solid #000000;border-left:0.5pt solid #000000;border-right:0.5pt solid #000000;padding:0.097cm;color:#000000;" | DMF/Services extends DMF/Core for service metadata and can be used together with DMF/Common (i.e. it is possible to use DMF/Services on top of DMF/Core (if DMF/Common elements are not needed) or on top of DMF/Common for an extensive profile).
 
|-
 
|-
 
|}
 
|}

Revision as of 14:44, 30 July 2019


Identifier Title / Description Value Domain Card Condition Specific mapping notes Guidelines Example
SRTYPE
[DMF/Services]
Service Type
A service type name.
 String
Default is unknown
 1   For OGC Web Services, the value defined by the applicable OGC Specification has to be used (e.g. 'WMS', WFS', 'CSW', 'WMTS', ... )  
SRTVER
[DMF/Services]
Service Type Version
Version of the service type.
 String
Default is unknown
 1   For OGC Web Services, the value defined by the applicable OGC Specification has to be used.  
SRSTD
[DMF/Services]
Service Standard
Standard to which the service adheres.
 Citation 0..1   This element can be used to mention to which DGIWG profile the service is compliant with.  
SRCPLING
[DMF/Services]
Service Coupling Type
Type of coupling between service and associated data (if exists)
 Coupling Type Codelist

Default is loose

1      
SROPRS
[DMF/Services]
Resource Operated by the Service
Provides a reference to the dataset on which the service operates


 URI
(URI of the metadata of the dataset on which the service operates.)
 0..* Mandatory if coupling type is tight or mixed. The domain value of SROPRS is the URI of the metadata of the dataset on which the service operates. Mandatory when coupling type is tight or mixed. For one resource either operatedDataset or operatesOn may be used (not both for the same resource).    
SROPER
[DMF/Services]
Service Operation
Provides information about the operations that comprise the service
 Service Operation 1..*      
SRCORS
[DMF/Services]
Service Coupled Resource

Further description of the data coupling in the case of tightly coupled services. It links a given operationName with a data set identified by an “identifier". And it requires that a given operationName or identifier shall refer to an existing operationName given by SROPER.name or an identifier given by RSID.code, respectively.

Service Coupling 0..* Only applicable to tightly coupled services.    


DMF/Core DMF/Core defines the minimum set of metadata elements to be implemented by any metadata catalogue. This set satisfies the discovery use case.
DMF/Common DMF/Common is an additional set of metadata elements for a more complete description of any type of resource supported by DMF. It extends DMF/Core and covers discovery and basic evaluation use cases.
DMF/Service DMF/Services extends DMF/Core for service metadata and can be used together with DMF/Common (i.e. it is possible to use DMF/Services on top of DMF/Core (if DMF/Common elements are not needed) or on top of DMF/Common for an extensive profile).
Retrieved from "https://eden.ign.fr/wiki/index.php?title=Service_Identification&oldid=719"