All Downloads are FREE. Search and download functionalities are using the official Maven repository.

ols.1.1.0.XLS.xsd Maven / Gradle / Ivy

There is a newer version: 1.1.0
Show newest version



	
	
		
			The top element of an OpenLS request-response  message; an XML document.
		
	
	
		
			Defines the top element of an XML document representing a message.
		
		
			
			
		
		
		
			
				Defines the preferred language used for formatting responses. 
			
		
	
	
		
			Defines the portion of a message that contains header information; see _Body for  the specific information needed to execute a request.
			Base element representing all types of header information.
		
	
	
		
			Defines the portion of a message that contains information orthogonal to the specific information needed to execute a request.  Typical header information includes infomation associated with authentication and authorization, transaction management, payment processing, tracing and auditing.
			Abstract type common to all types of header information.
		
	
	
		
			The portion of a message containing information that is core to the message; the request-response pair.
			Base element representing all types of body information.
		
	
	
		
			Defines the portion of a message containing information that is core to the message.
			Abstract type common to all types of body information.
		
	
	
		
			The header information for request messages.
		
	
	
		
			Defines the header information for request messages.
		
		
			
				
					
						The client name, used for authentication.
					
				
				
					
						
						The client password, used for authentication.
					
				
				
					
						A client-defined unique session Iidentifier, which should be returned in the response header.
					
				
				
					
						In general this reference points to a CRS instance of gml:CoordinateReferenceSystemType (see coordinateReferenceSystems.xsd). For well known references it is not required that the CRS description exists at the location the URI points to (Note: These "WKCRS"-ids still have to be specified).  If no srsName attribute is given, the CRS must be specified as part of the larger context this geometry element is part of, e.g. a geometric aggregate. Default value is WGS84
					
				
				
					
						A client-defined unique Iidentifier. Can be used for different purposes, for example billing.
					
				
			
		
	
	
		
			The core information of a service request message.
		
	
	
		
			Defines the core information of a service request message.
		
		
			
				
					
				
				
					
						The name of the method to be invoked by the service.
					
				
				
					
						The version level of the request parameters supported by the client.
					
				
				
					
						A client-defined request identifier, unique within the scope of the session.  The request identifier must be returned in the service response.
					
				
				
					
						This parameter will allow the request to control the number of responses generated. For example the POI request will use this as a contraint to generate a certain number of POIs. In the special cases where one of the responses can contain multiple values this will be controlled within the request itself, in those cases this parameter will not be applicable
					
				
			
		
	
	
		
			Base element representing the set of parameters for a service request.
		
	
	
		
			Abstract type representing the set of parameters for a service request.
		
	
	
		
			The header information for response messages.
		
	
	
		
			Defines the header information for response messages.
		
		
			
				
					
				
				
					
						The session identifier, specified by the client in the request header.
					
				
			
		
	
	
		
			The response information returned from a service request.
		
	
	
		
			Defines the response information returned from a service response.
		
		
			
				
					
					
				
				
					
						The version level of the response parameters supported by the service.
					
				
				
					
						The request identifier, unique within the scope of the session, specified by the client in the service request.
					
				
				
					
						This is the number of responses that are generated by the request. For example a map request can contain multiple requests for multiple maps, the responses will contain mulitple responses to that. In the case of Geocode, multiple responses will be equal to the number of requests, each response may contain one or more candidate addresses. For the scope of this specification, most of the time the number of responses will be equal to 1 
					
				
			
		
	
	
		
			Base element representing the response information returned from a service request.
		
	
	
		
			Abstract type representing the response information returned from a service request.
		
	
	
		
			A list of errors encountered while attempting to process a request.
		
	
	
		
			Defines a list of errors.
		
		
			
		
		
			
				Set to the highest severity of any of the Error elements. Specifically, if any of the Error elements have a severity of Error then highestSeverity must be set to Error, otherwise set highestSeverity to Warning.
			
		
	
	
		
			Contains error and/or status information.
		
	
	
		
			Defines the characteristics of a processing error.
		
		
			
				XML qualified name identifying the error. The well-known error codes within the "http://www.opengis.org/xls" namespace are enumerated in the type ErrorCodeEnum.
			
		
		
			
				Indicates the severity of the error.
			
		
		
			
				The ID of the element associated with the error.
			
		
		
			
				If the XML is well formed, then this attribute contains the path to the XML element or attribute associated with the error.
			
		
		
			
				Provides a human readable explanation of the error, which is not intended for algorithmic processing.
			
		
	
	
		
			Enumeration of error codes defined within the "http://www.opengis.net/xls" namespace.
		
		
			
				
					Version of Request Schema not supported.
				
			
			
				
					Version of Response Schema not supported.
				
			
			
				
					Element content or attribute value not recognized.  Although the document is well formed and valid, the element/attribute contains a value that could not be recognized and therefore could not be used by the service processing the message.
				
			
			
				
					Element or attribute not supported. Although the document is well formed and valid, an element or attribute is present that is consistent with the rules and constraints contained in the OpenLS specification, but is not supported by the service processing the message.
				
			
			
				
					Element content or attribute value inconsistent with other elements or attributes. Although the document is well formed and valid, according to the rules and constraints contained in the OpenLS specification the content of an element or attribute is inconsistent with the content of other elements or their attributes.
				
			
			
				
					Other error in an element content or attribute value. Although the document is well formed and valid, the element content or attribute value contains values that do not conform to the rules and constraints contained in the OpenLS specification and is not covered by other error codes. The Error message attribute should be used to indicate the nature of the problem.
				
			
			
				
					Message Delivery Failure. A message has been received that either probably or definitely could not be sent to its next destination. Note: if severity is set to Warning then there is a small probability that the message was delivered.
				
			
			
				
					Message Security Checks Failed. Validation of signatures or checks on the authenticity or authority of the sender of the message have failed.
				
			
			
				
					Unknown Error. Indicates that an error has occurred that is not covered explicitly by any of the other errors. The Error message attribute should be used to indicate the nature of the problem.
				
			
		
	
	
		
			Enumeration of the error severity levels.
		
		
			
				
					This indicates that although there is an error, other parts of the request will still be processed in the normal way.
				
			
			
				
					This indicates that there is an unrecoverable error in the request and no part of the request will processed.
				
			
		
	





© 2015 - 2024 Weber Informatics LLC | Privacy Policy