Skip to content
This repository has been archived by the owner on Dec 31, 2020. It is now read-only.

Commit

Permalink
Allow to implement nominations without implementing LAs
Browse files Browse the repository at this point in the history 
Fixes erasmus-without-paper/ewp-mobility-vs-api-use-cases#3
  • Loading branch information
@wrygiel
wrygiel committed Jun 7, 2016
1 parent 57c8581 commit 7f34c49
Show file tree
Hide file tree
Showing 2 changed files with 50 additions and 1 deletion.
6 changes: 5 additions & 1 deletion entries_to_append.xsd
View file
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,11 @@
A list of Outgoing Mobility history entries, in the same format as returned by
the Outgoing Mobilities API.

Please note, that servers are allowed to reject some requests if they find it
Please note, that servers are allowed to implement only a subset of mobility
history features. See `timeline-features-supported` element in the
`manifest-entry.xsd` file for details!

Also note, that servers are allowed to reject some requests if they find it
suspicious (e.g. when a receiving institution is attempting to mark a Learning
Agreement as "accepted by the sending institution"). For more details on
available history entries (and who is allowed to append them), please see the
Expand Down
45 changes: 45 additions & 0 deletions manifest-entry.xsd
View file
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,51 @@
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="timeline-features-supported">
<xs:annotation>
<xs:documentation>
One of the requirements of the EWP Network was to allow the partners to
implement just the nomination part of the mobility process:

https://github.com/erasmus-without-paper/ewp-wp4-use-cases/issues/3

Therefore, we have split all the timeline entries into groups, and we allow the
server implementers to support only a subset of all the entries.

* Server implementers are RECOMMENDED (but not required) to implement all of
the Outgoing Mobility API features.

* Client implementers are REQUIRED to take the value of this element into
account before making the call to the Outgoing Mobility Remote Update API.
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction>
<xs:enumeration value="nominations-only">
<xs:annotation>
<xs:documentation>
The minimum required support level. This includes all the entries related to
the nominations. See the schemas of the Outgoing Mobilities API for details.

Notes for the client implementers: If this value is present in the Registry
response, then it means that the server does not (yet) support timeline entries
related to Learning Agreements. This means that your `entries_to_append`
parameter may include entries related to nominations only.
</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="all">
<xs:annotation>
<xs:documentation>
If this value is present in the Registry response, then the server MUST support
**all** the mobility timeline entries specified in the documentation of the
greatest version of the Outgoing Mobilities API implemented by this server.
</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
Expand Down

0 comments on commit 7f34c49

Please sign in to comment.