Inline request header used in request and response documents. Version of the software running, as in beta3 or release 1.0. The time the request or response is being sent. The source of the request or response. For search requests, it is the IP of the original requestor. For all other requests and for responses, its the accessPoint of the host machine. The optional resource attibute should be set to the provider's resource code, in necessary. The destination of the request or response. This will be the provider accesspoint for requests and the portal for responses. The optional resource attibute should be set to the provider's resource code, in necessary. Type of operation being requested or being responded to. A simpleType to represent a URL that does a pattern match to verify a full URL without whitespace. A simpleType to represent an email address. A simpleType to represent an xpath-type used for querying. Request message format. Must always contain and header and may or maynot contain a payload, based on the type of request being made. A search operation, specifying query conditions and result details. Essentially, a representation of the "where" clause. An empty filter is prohibited. An abstract element provided as a base to group all comparitive operator elements. The equals (=) comparator element. The not 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. compares if concept(xpath) is null. use equal element to compare for empty strings ''. compares if concept(xpath) is not null. use equal element to compare for empty strings ''. 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. Response message format. The content of the response, as in the search results or status information. We use xsd:any because the content will be some XML that we do not know yet or that we will not know. The element is optional because certain types of request deliver all their response by way of the diagnostics. Optionally (for all search and scan requests) the "recordCount" attribute should be set. It counts all records delivered in the XML document, while totalSearchHits refers to the records in the database that matched the request. If a DB record could not be converted to a valid XML "record", it might have been dropped completely and shows up in the attribute "recordDropped". 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? holds the namespace of a supported schema. Uses attributes to indicate allowed usage for requests and/or responses. holds a xpath expression that is mapped to the providers DB. Repeatable to become a list of all mapped xpaths. The scan result for a scan response. list of distinct values.