Service Identification

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	Metadata classes	Guidelines	Example
SRTYPE [DMF/Services]	Service Type A service type name.	String Default is unknown	1		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).	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		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).	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		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).	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		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).
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.	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).
SROPER [DMF/Services]	Service Operation Provides information about the operations that comprise the service	Service Operation	1..*		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).
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/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).