forked from erasmus-without-paper/ewp-specs-api-omobilities
-
Notifications
You must be signed in to change notification settings - Fork 0
/
manifest-entry.xsd
102 lines (92 loc) · 5.66 KB
/
manifest-entry.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
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xml="http://www.w3.org/XML/1998/namespace"
xmlns:ewp="https://github.com/erasmus-without-paper/ewp-specs-architecture/blob/stable-v1/common-types.xsd"
xmlns:sec="https://github.com/erasmus-without-paper/ewp-specs-sec-intro/tree/stable-v2"
elementFormDefault="qualified"
targetNamespace="https://github.com/erasmus-without-paper/ewp-specs-api-omobilities/blob/stable-v1/manifest-entry.xsd"
xmlns="https://github.com/erasmus-without-paper/ewp-specs-api-omobilities/blob/stable-v1/manifest-entry.xsd"
>
<xs:import
schemaLocation="https://raw.githubusercontent.com/erasmus-without-paper/ewp-specs-architecture/stable-v1/common-types.xsd"
namespace="https://github.com/erasmus-without-paper/ewp-specs-architecture/blob/stable-v1/common-types.xsd"
/>
<xs:import
schemaLocation="https://raw.githubusercontent.com/erasmus-without-paper/ewp-specs-sec-intro/stable-v2/schema.xsd"
namespace="https://github.com/erasmus-without-paper/ewp-specs-sec-intro/tree/stable-v2"
/>
<xs:annotation>
<xs:documentation>
This schema is a part of the Erasmus Without Paper project. Before you start
using it, make sure you have read the general rules described here:
http://developers.erasmuswithoutpaper.eu/
</xs:documentation>
</xs:annotation>
<xs:element name="omobilities">
<xs:annotation>
<xs:documentation>
If this element is present in EWP Host's manifest file, then the host states
that it implements the Outgoing Mobilities API described here:
https://github.com/erasmus-without-paper/ewp-specs-api-omobilities
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:complexContent>
<xs:extension base="ewp:ManifestApiEntryBase">
<xs:sequence>
<xs:element name="http-security" type="sec:HttpSecurityOptions" minOccurs="0" maxOccurs="1">
<xs:annotation>
<xs:documentation>
Describes which security policies the server supports for this API. If not
given, then the server states that it supports the default set of security
policies (as described in the annotations in sec:HttpSecurityOptions).
The policies described in this element apply to all endpoints of this API (the
`*-url` elements below). Clients SHOULD consult this element before accessing
any of these endpoints (otherwise, their request might be rejected by the
server).
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="get-url" type="ewp:HTTPS" minOccurs="1" maxOccurs="1">
<xs:annotation>
<xs:documentation>
An URL at which the `get` endpoint is being served.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="index-url" type="ewp:HTTPS" minOccurs="1" maxOccurs="1">
<xs:annotation>
<xs:documentation>
An URL at which the `index` endpoint is being served.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="max-omobility-ids" type="xs:positiveInteger" minOccurs="1" maxOccurs="1">
<xs:annotation>
<xs:documentation>
The maximum number of `omobility_id` parameters the server is willing to accept
in one request.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="sends-notifications" type="ewp:Empty" minOccurs="0" maxOccurs="1">
<xs:annotation>
<xs:documentation>
If this element is present, then the EWP Host states, that it has implemented a
Notification Sender for Outgoing Mobility objects - it will *try* to deliver
notifications to all Outgoing Mobility CNR APIs implemented throughout the EWP
Network whenever related mobility objects are updated.
It is HIGHLY RECOMMENDED for all EWP Hosts to implement this feature. If it is
not implemented, then receiving institutions will need to resolve into pulling
fresh data from your Outgoing Mobilities API quite often - this method
will increase both latency and the load on both servers.
</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>