10.9.4 Parameter descriptions
10.9.4.1 ElementSetName parameter
The ElementSetName parameter is used to specify a named, predefined set of metadata record elements from each source record that should be presented in the response to the
operation. The predefined set names of brief, summary and full are meant to represent different level of detail of the source record with brief representing the least amount of
detail and full representing all the metadata record elements. The sets of metadata record element names that correspond to brief, summary and full shall be defined in an
Application Profile. If the ElementSetName parameter is not set in a request the service shall respond with one or more summary records.
10.9.4.2 Id parameter
The Id parameter is a comma-separated list of record identifiers for the records that a CSW shall return to the client. In the XML encoding, one or more Id elements may be
used to specify the record identifier to retrieve.
If any of the identifiers specified in the operation is invalid, then the operation should fail and an exception message should be returned as described in subclause 10.3.7.
10.9.4.3 outputFormat parameter
The outputFormat parameter is used to control the format of the output that is generated n response to a GetRecordById request. Its value shall be a MIME type. The default value,
“applicationxml”, means that the output shall be an XML document. All catalogues shall at least support XML as an output format. Other output formats may be supported and
may include output formats such as TEXT MIME type textplain, or HTML MIME type texthtml. The list of output formats that a CSW instance provides shall be
advertised in the capabilities document.
In the case where the output format is applicationxml, the CSW shall generate an XML document that validates against a schema document that is specified in the output
document via the xsi:schemaLocation attribute defined in XML.
10.9.4.4 outputSchema parameter
The outputSchema parameter is included in the GetRecordById operation to allow clients to request a representation of a catalogue record other than the default representation.
By default, the GetRecordById operation generates a response that validates against the schema of the information model that the catalogue implements. This is the default
representation of a catalogue record. Thus, a catalogue that implements the ebRIM would generate a response that validates against rim.xsd, the ebRIM schema. Similarly, a
catalogue that uses ISO19115ISO19119 as its underlying information model would generate a response that validates against those schemas.
162
Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved.
A CSW server shall, in its Capabilities document, advertise which schemas it can use to represent a record in response to a GetRecordById request. This shall be done using the
Parameter element inside the Operation element in the Capabilities document. The list of values shall include the value “
http:www.opengis.netcatcsw2.0.2 ”, representing the
schema of the common queryable and returnable elements that all CSW implementation must support. This list may include a value that represents the schema of the underlying
information model, if that schema is different than the OGC common schema. The default value shall be the first value in the list.
EXAMPLE 1 The following XML fragment lists the possible values for the outputSchema parameter for a
catalogue that only support the OGC common schema: Operation name=GetRecordById
... Parameter name=outputSchema
Valuehttp:www.opengis.netcatcsw2.0.2Value Parameter
... Operation
EXAMPLE 2
The following XML fragment lists the possible values for the outputSchema parameter for a catalogue that uses ebRIM v3.0 as its underlying information model:
Operation name=GetRecordById ...
Parameter name=outputSchema Valueurn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0Value
Valuehttp:www.opengis.netcatcsw2.0.2Value Parameter
... Operation
EXAMPLE 3
The following XML fragment lists the possible values for the outputSchema parameter for a catalogue that uses ebRIM v3.0 as its underlying information model but also supports mappings to other catalogue
information models: Operation name=GetRecordById
... Parameter name=outputSchema
Valueurn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0Value Valuehttp:www.opengis.netcatcsw2.0.2Value
Valueurn:oasis:names:tc:ebxml-regrep:xsd:rim:2.5Value Parameter
... Operation
10.9.5 Response
The following XML Schema fragment defines the response to a GetRecordById request:
xsd:element name=GetRecordByIdResponse
type=csw:GetRecordByIdResponseType xsd:complexType
name=GetRecordByIdResponseType xsd:sequence
xsd:choice
Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved.
163
xsd:element ref=csw:AbstractRecord minOccurs=0 maxOccurs=unbounded
xsd:any processContents=strict namespace=other minOccurs=0 maxOccurs=unbounded
xsd:element xsd:choice
xsd:sequence xsd:complexType
This is simply the list of requested records. The response records should substitute for the element csw:AbstractRecord.
10.9.6 Examples
Kategori