Taken from w3c schema for maxOccurs at: http://www.w3.org/2001/XMLSchema.xsd Any integer or the value "null" A simpleType to represent an xpath-type used for querying. A simpleType to represent an xpath-type used for querying. Concept binding based on xpath for a single concept within a known schema. Concept binding based on xpath for a single concept for any schema. Request message format. Must always contain and header and may or maynot contain a payload, based on the type of request being made. Used to specify parameters for a search or inventory only. Define a list of concepts to be treated as the base of a record in a search response. Used to specify the concepts to make an inventory on or to be used to specify the requested concepts for a search response. If for a search the list is empty, only the mandatory concepts will be returned. In case the path is pointing to a branch node, all its child nodes will be listed implicitly. A single qualified concept Inline request header used in request and response documents. The source of the request or response. Repeatable to trace back all servers of the cascading request or involved providers/datasources. For search requests, it starts with the original requestor, the client. For all other requests and for responses, its the accessPoint of the host machine. Holds the IP of the source with the timestamp as an attribute in ISO format. The attribute software should indicate the software incl its version used to generate or modify the document. The destination access point of the request or response. This will be the potentially multiple provider accesspoint(s) for requests to a portal or a single access point for provider/datasource destinations. For a response this is always the client address. A list of addressed datasources in case the destination is a provider access point. Optional because in the case of a datasource being the destination directly, a datasource does not need to be specified. Information about the used content compression method. This will allow to compress the "content" part of a response but leave the protocol envelope readable. software without decompression routines can still pass the data on and read its desitnation and source. For passing optional authentication parameters. Eg an id after an authentication has been reached. Define your own structur how the data should be returned refering to known concepts of another schema. Define a list of concepts to be treated as the base of a record. Use this concept if its repeatable or the closest repeatable parental element. Define a custom structure for the returned content starting with a root element. A base to group all COPs or literal values. Could be used in the future to implement arithmetics or even more sophisitcated expressions like the ones used in the openGIS filter specification. An element to represent literals / values. Substitutes an abstract expression element. An element to represent a concept of one specific conceptual schema. Substitutes an abstract expression element. An abstract element provided as a base to group all comparitive operator elements. Compares if concept is null. use equal element to compare for empty strings ''. The equals (=) comparator element. The less than (<) comparator element. The less than or equals (<=) comparator element. The greater than (>) comparator element. The greater than or equals (>=) comparator element. The like (LIKE) comparator element. The in (IN) comparator element. A logical operator clause. This is an abstract element to be substituted by concrete logical operator elements. The or logical operator. Responses are used by providers or portals to wrap several responses into one. Response message format for a single datasource. Not to be used by a provider. The content of a response, regardless of the request type. The diagnostics element can contain many diagnostic pieces of information. Should the possible diagnostic codes/messages be defined more granularly in a seperate XML Schema? The footer holds information about the number of records for paging purposes. This includes all 3 operators. AND, OR, NOT This includes the basic comparative operators =, <, >, <=, >= Version and name of the software involed in editing the protocol document. E.g provider software, portal, proxy, ... Name and version of the software component being used by the software. Information about the supported request types of this service. what security related capabilities does the provider have? encryption, access restriction, etc. holds the namespace of a supported schema. Version and name of the software involed in editing the protocol document. E.g provider software, portal, proxy, ... Name and version of the software component being used by the software. Information about the provider configuration for a datasource. Allow for more application specific settings. Each mapped/configured concept of a schema of this resource is listed here as a single concept returning a boolean flag if it is searchable. Information about the supported filter operators of this service. Information about the supported request types of this service. what security related capabilities does the provider have? encryption, access restriction, etc. Slot for future custom needs ... Simple generic build-in metadata response holds the namespace of a supported schema. Simple generic build-in metadata response Envelope to list all concepts that have been used for the inventory response. Header row giving the concept for each value of the sequence within a record below. A distinct combination of values for all "inventoried" concepts. The optional attribute "count" is used to count the number of occurences for this distinct combination and will only be set if the count flag was used when requesting an inventory. A single value for a single concept. The sequence of the values should correspond to the one given in the concept header row above. Records of a search response.