Difference between revisions of "Service Identification"
From DGIWG
| Line 119: | Line 119: | ||
| − | {| style="border-spacing:0 | + | {| style="border-spacing:0;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-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 | ||
Revision as of 10:01, 2 August 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). |
