Copyright © 2002-2008 Open Geospatial Consortium, Inc. All Rights Reserved.
142
2 You should use meters as the default units of measure for distances and
coordinates.
3 You should express azimuth in degrees measured clockwise from true north. 4 You should use WGS 84 as the default datum and Coordinate Reference System.
5 You should follow the OGC recommendation for Coordinate Reference Systems
SRS.
6 You should follow the OGC recommendation for Units of Measure.
1.3.5.4 Name Spaces
1 All schemas generated under the OpenLS initiative must set the targetNameSpace
attribute value to: http:www.opengis.netxls
.
1.3.6 Request Requirements
Each OpenLS Core Service shall have an XML Request Packet that contains the Request. The XML Request Packet must include at least two main Blocks
1
, a Header Block and one or more Method Blocks which will contain the actual requests:
1
Request Header Block
a
A Request Header Block should contain the username and password for the Client Application.
b
A Request Header Block should contain the type of the client device, if applicable based upon a well-known list of known types.
c
A Request Header Block may contain a client-defined Session Identifier, to be echoed back by the server.
2
Request Method Blocks
a
An XML Request should contain zero or more Method Blocks.
b
A Request Method Block must contain a “global” unique method name Type NMT that identifies the method that will be invoked by the Core Service. The
term “global” refers to a unique ID that identifies a method in the context of the applicable OpenLS Core Service.
1
This structure is designed for compatibility with a SOAP-based API.
Copyright © 2002-2008 Open Geospatial Consortium, Inc. All Rights Reserved.
143
c
A Request Method Block must contain Request Version, which indicates the version of the Request that it supports.
d
A Request Method Block must contain Response Version, which indicates the version of the Response that the Client Application supports.
e
A Request Method Block must contain a maximum of one Sub-Block that contains the XML payload the request parameters for the specified method.
f
Each Request Method Block must have a Request Identifier. The Request Identifier is a string that must appear in the Method Request Tag as an ‘ID’
attribute. A Request Identifier must be unique within the scope of a session.
1.3.7 Response Requirements
The XML Response Packet must include at least two main Blocks, a Header Block and one or more Response Method Blocks:
1
Response Header Block
a
A Header Block may include the status of the Response use a standard list of enumerations for status -- TBD.
b
A Header Block should contain a Session Identifier, which corresponds with the applicable Request Session Identifier.
Note: The error list associated with the Header Block is for authentication errors and other errors generated for the envelop, whereas error lists associated with a Response Method Block are for individual responses.
2
Response Method Blocks
a
An XML Response must contain at least one Response Method Block.
b
The Response Method Block must contain zero or one Sub-Blocks that contain the XML payload for the specified method.
c
A Response Method Block must contain Response Version, which indicates the version used to encode the Response.
d
A Response Method Block may include the status of the Method Response use a standard list of enumerations for status -- TBD.
e
A Response Method Block may include zero or more Fault Error Elements, which indicate the error status use a standard enumerated list of errors -- TBD,
code and description generated during the scope of the session. [Note: Error handling is based upon the SOAP Fault Element.]
