Difference between revisions of "Service Coupling"
From DGIWG
| Line 3: | Line 3: | ||
| − | {| style="border-spacing:0;width: | + | {| style="border-spacing:0;width:30cm;" |
|- | |- | ||
! style="border:1pt solid #000000;padding:0.049cm;" | Identifier | ! style="border:1pt solid #000000;padding:0.049cm;" | Identifier | ||
Latest revision as of 13:38, 7 May 2021
The properties of Service Coupling are listed below.
| Identifier | Title / Description | Value Domain | Card |
|---|---|---|---|
| operationName
[DMF/Services]
|
Operation Name
Name of the operation.
|
String | 1 |
| identifier
[DMF/Services]
|
Identifier
Identifier of the tightly coupled dataset.
|
String | 1 |
| scope
[DMF/Services]
|
Scope
Scope of the coupling (e.g. name of the WMS layer in which the coupled data are provided when a GetMap operation is called).
Constraints: * Anchor complex type is not allowed for scope.code and scope.namespace which are necessarily implemented as String
|
Identifier | 0..1
|
