Difference between revisions of "Service Identification"
From DGIWG
m |
m |
||
| Line 22: | Line 22: | ||
<div style="color:#000000;">A service type name. For OGC Web Services, the value defined by the applicable OGC Specification has to be used (e.g. 'WMS', WFS', 'CSW', 'WMTS', ... )</div> | <div style="color:#000000;">A service type name. For OGC Web Services, the value defined by the applicable OGC Specification has to be used (e.g. 'WMS', WFS', 'CSW', 'WMTS', ... )</div> | ||
| − | | style="border-top:none;border-bottom:1pt solid #000000;border-left:none;border-right:1pt solid #000000;padding-top:0cm;padding-bottom:0.049cm;padding-left:0cm;padding-right:0.049cm;" | [[# | + | | style="border-top:none;border-bottom:1pt solid #000000;border-left:none;border-right:1pt solid #000000;padding-top:0cm;padding-bottom:0.049cm;padding-left:0cm;padding-right:0.049cm;" | [[#String|String]] |
<div style="color:#000000;">Default is '''unknown'''</div> | <div style="color:#000000;">Default is '''unknown'''</div> | ||
Revision as of 17:18, 29 August 2018
The following metadata elements are only applicable to services.
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.”
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.
| Identifier | Title / Description | Value Domain | Card | Condition | Guidelines | Example |
|---|---|---|---|---|---|---|
| SRTYPE
[DMF/Services]
|
Service Type
A service type name. For OGC Web Services, the value defined by the applicable OGC Specification has to be used (e.g. 'WMS', WFS', 'CSW', 'WMTS', ... )
|
String
Default is unknown
|
1 | |||
| SRTVER
[DMF/Services]
|
Service Type Version
Version of the service type. For OGC Web Services, the value defined by the applicable OGC Specification has to be used.
|
String
Default is unknown
|
1 | |||
| SRSTD
[DMF/Services]
|
Service Standard
Standard to which the service adheres. This element can be used to mention to which DGIWG profile the service is compliant with.
|
Citation | 0..1 | |||
| 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
Constraints: * Mandatory if coupling type is tight or mixed.
|
URI
(URI of the metadata of the dataset on which the service operates.)
|
0..* | |||
| 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.
Constraints: * Only applicable to tightly coupled services.
|
Service Coupling | 0..* |
