1
|
<?xml version="1.0" encoding="UTF-8"?>
|
2
|
<xsd:schema
|
3
|
targetNamespace="http://www.opengis.net/ogc"
|
4
|
xmlns:ogc="http://www.opengis.net/ogc"
|
5
|
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
|
6
|
elementFormDefault="qualified">
|
7
|
|
8
|
<xsd:element name="ServiceExceptionReport">
|
9
|
<xsd:annotation>
|
10
|
<xsd:documentation>
|
11
|
The ServiceExceptionReport element contains one
|
12
|
or more ServiceException elements that describe
|
13
|
a service exception.
|
14
|
</xsd:documentation>
|
15
|
</xsd:annotation>
|
16
|
<xsd:complexType>
|
17
|
<xsd:sequence>
|
18
|
<xsd:element name="ServiceException"
|
19
|
type="ogc:ServiceExceptionType"
|
20
|
minOccurs="0" maxOccurs="unbounded">
|
21
|
<xsd:annotation>
|
22
|
<xsd:documentation>
|
23
|
The Service exception element is used to describe
|
24
|
a service exception.
|
25
|
</xsd:documentation>
|
26
|
</xsd:annotation>
|
27
|
</xsd:element>
|
28
|
</xsd:sequence>
|
29
|
<xsd:attribute name="version" type="xsd:string" fixed="1.2.0"/>
|
30
|
</xsd:complexType>
|
31
|
</xsd:element>
|
32
|
|
33
|
<xsd:complexType name="ServiceExceptionType">
|
34
|
<xsd:annotation>
|
35
|
<xsd:documentation>
|
36
|
The ServiceExceptionType type defines the ServiceException
|
37
|
element. The content of the element is an exception message
|
38
|
that the service wished to convey to the client application.
|
39
|
</xsd:documentation>
|
40
|
</xsd:annotation>
|
41
|
<xsd:simpleContent>
|
42
|
<xsd:extension base="xsd:string">
|
43
|
<xsd:attribute name="code" type="xsd:string">
|
44
|
<xsd:annotation>
|
45
|
<xsd:documentation>
|
46
|
A service may associate a code with an exception
|
47
|
by using the code attribute.
|
48
|
</xsd:documentation>
|
49
|
</xsd:annotation>
|
50
|
</xsd:attribute>
|
51
|
<xsd:attribute name="locator" type="xsd:string">
|
52
|
<xsd:annotation>
|
53
|
<xsd:documentation>
|
54
|
The locator attribute may be used by a service to
|
55
|
indicate to a client where in the client's request
|
56
|
an exception was encountered. If the request included
|
57
|
a 'handle' attribute, this may be used to identify the
|
58
|
offending component of the request. Otherwise the
|
59
|
service may try to use other means to locate the
|
60
|
exception such as line numbers or byte offset from the
|
61
|
begining of the request, etc ...
|
62
|
</xsd:documentation>
|
63
|
</xsd:annotation>
|
64
|
</xsd:attribute>
|
65
|
</xsd:extension>
|
66
|
</xsd:simpleContent>
|
67
|
</xsd:complexType>
|
68
|
</xsd:schema>
|