generated from ivoa-std/doc-template
-
Notifications
You must be signed in to change notification settings - Fork 4
/
VOEventRegExt-v2.0.xsd
54 lines (50 loc) · 2.04 KB
/
VOEventRegExt-v2.0.xsd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:vr="http://www.ivoa.net/xml/VOResource/v1.0"
xmlns:voe="http://www.ivoa.net/xml/VOEventRegExt/v2"
xmlns:vm="http://www.ivoa.net/xml/VOMetadata/v0.1"
targetNamespace="http://www.ivoa.net/xml/VOEventRegExt/v2"
elementFormDefault="unqualified" attributeFormDefault="unqualified"
version="2.0pre1">
<xs:annotation>
<xs:appinfo>
<vm:schemaName>VOEventRegExt</vm:schemaName>
<vm:schemaPrefix>xs</vm:schemaPrefix>
<vm:targetPrefix>voe</vm:targetPrefix>
</xs:appinfo>
<xs:documentation>
Types for registering VOEvent services.
</xs:documentation>
</xs:annotation>
<xs:import namespace="http://www.ivoa.net/xml/VOResource/v1.0"
schemaLocation="http://www.ivoa.net/xml/VOResource/v1.0"/>
<xs:complexType name="StreamEndpoint">
<xs:annotation>
<xs:documentation>
An endpoint through which a VOEvent stream can be followed.
</xs:documentation>
<xs:documentation>
Since VOEvent streams can be served through several
protocols, the actual protocol used on a particular endpoint
must be given in a standardID attribute.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="vr:Interface">
<xs:attribute name="standardID" type="xs:anyURI" use="required">
<xs:annotation>
<xs:documentation>
A URI of the standard or convention this endpoint follows.
</xs:documentation>
<xs:documentation>
This will normally be a key from
ivo://ivoa.net/std/VOEvent starting with acc-.
</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
<!-- vim:et:sw=3
-->