Releases: emrex-eu/elmo-schemas
2.0.0
Added ResultsOfRecognition
Added security improvements suggested in #81
Removed deprecated "level" element
Made LearningOpportunitySpecification identifier mandatory
Added support for external grading scheme IDs
Renamed bday to dateOfBirth
Modified w3 link from http to https
Support for non latin name for learner according to request #82
1.7.0
1.6.0
1.5.0
1.4.0
1.3.0
- Added a way to connect attachment to a LOI. See this issue
- Added categories to LOI for grouping and sorting. See this issue
1.2.0
Version 1.2 of ELMO, which includes the following changes:
-
Added qualification level to LearningOpportunityInstance to open for adding
Qualification Framework levels, for instance EQF. -
New LOI
status
element (in thelearningOpportunityInstance
element). All
server implementers are STRONGLY RECOMMENDED to explicitly include this
status in all their ELMO files.
See this issue. -
Introduce optional list of
<identifier type="...">
elements in
<learningOpportunityInstance>
element. Previously, identifiers were allowed
on the LOS level only (but not the LOI level). See [this issue]
(#10). -
Prepared the EMREX ELMO format to be embedded in other contexts. Replaced
references to "NCP" and "EMREX Client" with more generic terms (which would
properly fit in other contexts). See [this issue]
(#13). -
The
Attachment/content
element can now occur multiple times
(maxOccurs="unbounded"
), and it can take an optionalxml:lang
attribute.
See this issue. -
Some more predefined identifier types were mentioned - the ones used in the
EWP (Erasmus Without Paper) project. -
New LOS element:
descriptionHtml
. It allows servers to add some basic
formatting to their descriptions. -
Grading schemes were introduced. Now servers can attach descriptions of their
grading schemes (via thereport/gradingScheme
element), and refer to these
descriptions in specific LOIs (via thegradingSchemeLocalId
element). See
this issue.
1.1.0
1.0.0: The first official release
There were some schemas in use before the 1.0.0
version, but this is the first
version which all the partners had agreed upon to be the common
backward-compatible (if possible) component of all the future versions of the schema.