class of information to which the referencing entity applies links a given operationName (mandatory attribute of SV_OperationMetadata) with a data set identified by an 'identifier' scoped identifier of the resource in the context of the given service instance NOTE: name of the resources (i.e. dataset) as it is used by a service instance (e.g. layer name or featureTypeName). reference to the dataset on which the service operates class of information to which the referencing entity applies Operation Chain Information the name, as used by the service for this chain a narrative explanation of the services in the chain and resulting output describes the signature of one and only one method provided by the service a unique identifier for this interface distributed computing platforms on which the operation has been implemented free text description of the intent of the operation and the results of the operation the name used to invoke this interface within the context of the DCP. The name is identical for all DCPs. handle for accessing the service interface parameter information the name, as used by the service for this parameter indication if the parameter is an input to the service, an output or both a narrative explanation of the role of the parameter indication if the parameter is required indication if more than one value of the parameter may be provided class of information to which the referencing entity applies class of information to which the referencing entity applies the parameter is an input parameter to the service instance the parameter is an output parameter to the service instance the parameter is both an input and output parameter to the service instance identification of capabilities which a service provider makes available to a service user through a set of interfaces that define a behaviour - See ISO 19119 for further information a service type name, E.G. 'discovery', 'view', 'download', 'transformation', or 'invoke' provide for searching based on the version of serviceType. For example, we may only be interested in OGC Catalogue V1.1 services. If version is maintained as a separate attribute, users can easily search for all services of a type regardless of the version information about the availability of the service, including, 'fees' 'planned' 'available date and time' 'ordering instructions' 'turnaround' type of coupling between service and associated data (if exists) further description of the data coupling in the case of tightly coupled services provides a reference to the dataset on which the service operates