Skip to content

Commit c707753

Browse files
msdemleimsdemlei
committed
Updating the schema to include DALIInterface
1 parent fc70659 commit c707753

File tree

1 file changed

+121
-3
lines changed

1 file changed

+121
-3
lines changed

‎TAPRegExt-v1.0.xsd‎

Lines changed: 121 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,9 @@ xmlns:tr="http://www.ivoa.net/xml/TAPRegExt/v1.0"
77
version="1.0"
88
targetNamespace="http://www.ivoa.net/xml/TAPRegExt/v1.0"
99
elementFormDefault="unqualified"
10-
attributeFormDefault="unqualified">
10+
attributeFormDefault="unqualified"
11+
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
12+
xsi:schemaLocation="http://www.w3.org/2001/XMLSchema http://vo.ari.uni-heidelberg.de/docs/schemata/XMLSchema.xsd">
1113
<xs:annotation>
1214
<xs:appinfo>
1315
<vm:schemaName>TAPRegExt</vm:schemaName>
@@ -119,10 +121,126 @@ attributeFormDefault="unqualified">
119121
</xs:complexContent>
120122
</xs:complexType>
121123

124+
<xs:complexType name="DALIInterface">
125+
<xs:annotation>
126+
<xs:documentation>
127+
An interface for a complex, multi-endpoint interfaces as
128+
regulated by DALI.
129+
</xs:documentation>
130+
<xs:documentation>
131+
In addition to the standard vr:Interface elements, DALIInterfaces
132+
have endpoints, listed by name; that name doubles as a path segment
133+
to append to the interface's access URL, yielding the URI at
134+
which the endpoint is operated.
135+
</xs:documentation>
136+
</xs:annotation>
137+
138+
<xs:complexContent>
139+
<xs:extension base="vr:Interface">
140+
<xs:sequence>
141+
<xs:element name="endpoint" type="tr:Endpoint"
142+
minOccurs="0" maxOccurs="unbounded">
143+
<xs:annotation>
144+
<xs:documentation>
145+
An endpoint accessible through this interface.
146+
</xs:documentation>
147+
</xs:annotation>
148+
</xs:element>
149+
</xs:sequence>
150+
</xs:extension>
151+
</xs:complexContent>
152+
</xs:complexType>
153+
154+
<xs:complexType name="Endpoint">
155+
<xs:annotation>
156+
<xs:documentation>
157+
An endpoint of a complex interface.
158+
</xs:documentation>
159+
<xs:documentation>
160+
An endpoint is characterised and addrssed by its name;
161+
they can further be defined through RDF triples. This is a
162+
generic extension mechanism for endpoint-specific metadata,
163+
primarily intended for custom, vendor-specific extensions.
164+
</xs:documentation>
165+
</xs:annotation>
166+
<xs:sequence>
167+
<xs:element name="name" type="xs:token"
168+
minOccurs="1" maxOccurs="1">
169+
<xs:annotation>
170+
<xs:documentation>
171+
The endpoint name, which is also the last component of the
172+
path of its URI.
173+
</xs:documentation>
174+
<xs:documentation>
175+
Names without dashes are reserved for IVOA use and are expected to
176+
work the same way on all services. Well-known examples for
177+
such endpoint names include sync, async, and tables.
178+
</xs:documentation>
179+
</xs:annotation>
180+
</xs:element>
181+
182+
<xs:element name="meta" type="tr:MetaTriple"
183+
minOccurs="0" maxOccurs="unbounded">
184+
<xs:annotation>
185+
<xs:documentation>
186+
Auxiliary information on this endpoint.
187+
</xs:documentation>
188+
</xs:annotation>
189+
</xs:element>
190+
</xs:sequence>
191+
</xs:complexType>
192+
193+
<xs:complexType name="MetaTriple">
194+
<xs:annotation>
195+
<xs:documentation>
196+
A container for an RDFa triple giving information related to
197+
an endpoint.
198+
</xs:documentation>
199+
</xs:annotation>
200+
<xs:simpleContent>
201+
<xs:extension base="xs:token">
202+
<xs:attribute name="about" type="xs:anyURI" use="optional">
203+
<xs:annotation>
204+
<xs:documentation>
205+
The subject of the statement.
206+
</xs:documentation>
207+
<xs:documentation>
208+
If missing, the endpoint itself is assumed as the subject.
209+
</xs:documentation>
210+
</xs:annotation>
211+
</xs:attribute>
212+
<xs:attribute name="property" type="xs:anyURI" use="required">
213+
<xs:annotation>
214+
<xs:documentation>
215+
The property of the statement.
216+
</xs:documentation>
217+
<xs:documentation>
218+
This is a reference to an RDF resource. IVOA standards may define
219+
semantics for scheme-less URI; non-IVOA properties must use
220+
full URIs with at least scheme and authority; in this
221+
version, no vocab attributes are supported.
222+
</xs:documentation>
223+
</xs:annotation>
224+
</xs:attribute>
225+
<xs:attribute name="resource" type="xs:anyURI" use="optional">
226+
<xs:annotation>
227+
<xs:documentation>
228+
The object of the statement.
229+
</xs:documentation>
230+
<xs:documentation>
231+
If missing, the text content of the element is used as the
232+
object.
233+
</xs:documentation>
234+
</xs:annotation>
235+
</xs:attribute>
236+
</xs:extension>
237+
</xs:simpleContent>
238+
</xs:complexType>
239+
122240
<xs:complexType name="DataModelType">
123241
<xs:annotation>
124242
<xs:documentation>
125-
An IVOA defined data model, identified by an IVOID
243+
An IVOA defined data model, identified by an IVORN
126244
intended for machine consumption and a short label
127245
intended for human comsumption.
128246
</xs:documentation>
@@ -149,7 +267,7 @@ attributeFormDefault="unqualified">
149267
<xs:documentation>
150268
Each language element can describe one or more versions
151269
of a language. Either name alone or name-version can be
152-
used as values for the LANG parameter of the service.
270+
used as values for the server's LANG parameter.
153271
</xs:documentation>
154272
</xs:annotation>
155273

0 commit comments

Comments
 (0)