Upload
mariah-dorsey
View
212
Download
0
Embed Size (px)
Citation preview
XCRI-CAP: From 1.1 to 1.2
Scott Wilson
What’s changed since 2008?
• CEN Metadata For Learning Opportunities became an EU standard
• 14-19 regional pilots• Lots of mini-projects• HEAR• KIS• HEDD
What’s changed from 1.1?
• Harmonization with MLO• Some new elements (especially for non-HE)• Some Terms moved into main spec• Some elements removed that weren’t being used• Improved temporal (date/time) elements• Improved engagement type elements• Specification developed as a single W3C-style
document• Factoring out the update model
CEN Harmonization
• Added Contributor, Date, and Type properties to Catalog, Provider, Course and Presentation
• Replaced Relation with HasPart, and allowed both by-reference and inclusion
• Venue property of a Presentation now contains a Provider instance for the venue Location
• Added Location property to Provider, containing the information previously supplied in OrganisationDType
• Replaced Credit with CEN CWA 16077• Added engagement as parent of studymode etc• Uses MLO namespace wherever possible• MLO conformance table• Some renaming (e.g. assessmentStrategy -> assessment)
New Elements
<age> in <presentation> Intended age range of the presentation (e.g. 14-16)
<url> in <location>URL for information about the location
<type> in <provider>Supports provider types (e.g. college, university)
<abbr> in <qualification>Abbreviated name of a qualification (e.g. BsC, HNC)
Simplifying common descriptions
Common descriptive elements - moves common Terms into the core namespace: <abstract>, <applicationProcedure>, <assessment>, <learningOutcome>, <objective>, <prerequisite>, <regulations>
This makes it much easier to use these elements as you don’t need <xsi:type> - they also go into the BSI standard.
Simpler engagement terms
<studyMode> <attendanceMode> <attendancePattern> are all now in the main specification and namespace. They are also defined as refinements of mlo:engagement
The optional identifier attribute is used for referencing vocabulary terms:
• NK [Not known]• FL [Flexible]• FT [Full time]• PF [Part of a full time programme]• PT [Part]
<studyMode identifier="FT">Full time</studyMode>
Improved temporal elements I
Support for both machine-readable and human-readable temporal information.
• Human-readable information goes in the element content• Machine-readable data goes in the optional dtf attribute
<start dtf="2011-09">September 2011</start> <end dtf="2012-05">May 2012</end>
<start>As soon as enough students have enrolled, usually once every four weeks</start>
Improved temporal elements II
<duration> follows the same pattern, but uses the interval attribute:
<duration interval="P3Y">Three years</duration>
(The interval format uses the ISO 8601 interval specification)
Simpler Subject handling
Same as for studymode (etc) we added an identifier attribute to make it easier to distinguish human-readable subject labels from vocabulary identifiers
<dc:subject identifier=“http://id.loc.gov/authorities/sh85012832#concept“>Beer</dc:subject>
<dc:subject identifier=“http://id.loc.gov/authorities/sh85105075#concept“>Porter</dc:subject>
(Note the use here of an LoC URI)
Removed
<entryProfile> wasn’t used (we may revisit as a separate spec)
<entryRequirements> was a duplicate of <prerequisite>
<startUntil> and <endFrom> were confusing, and can be handled by improved <start> and <end>
Refactored
Attributes supporting delta update processing (recstatus) have been removed and a new draft specification started:
http://www.xcri.org/wiki/index.php/XCRI_1.2_Updates
The idea is that this spec can be developed and maintained outside of the BSI standard and can take account of changes in implementation practice.
Namespace Soup
<provider> <dc:title>The College of Art, Bolton</dc:title>
<mlo:location> <street>Deane Road</street>
<town>Bolton</town> <postcode>BL3 1EX</postcode>
</mlo:location> </provider>
Note the use of DC, XCRI and MLO namespaces. Aggregators may need to be tolerant of mis-applied NSs in document instances.
New documentation style
Uses W3C-style specification formatting
About 25 pages long
Much easier to read and navigate than the old wiki-style spec.
http://www.xcri.org/wiki/index.php/XCRI_1.2
This is the FINAL version of XCRI 1.2
BS/EN XCRI
UK residual standard for CEN MLO; adds extensions from XCRI and XML binding for implementation in UK context