Updating Leap2A to 2010-07

From Leapspecs

Jump to: navigation, search

Belongs to the Leap2A/specification

This is an explanation of the changes and clarifications made between the 2009-03 and 2010-07 versions of Leap2A. It is based on the Leap2A/spec changes

Contents

Namespaces

Change the namespaces, along with all uses of them from

xmlns:leap="http://wiki.cetis.ac.uk/2009-03/Leap2A_predicates#"
xmlns:leaptype="http://wiki.cetis.ac.uk/2009-03/Leap2A_types#"
to
xmlns:leap2="http://terms.leapspecs.org/"

Version element

Under the Atom feed, put a version element

<leap2:version>http://www.leapspecs.org/2010-07/2A/</leap2:version>

Files

All references within the leap2a.xml to files included in the zip archive should now be done with

<link rel="enclosure" href="..." type="..." length="..." />

Length is recommended but not mandatory.

Maintain the ability to import atomOutOfLineContent (using the src attribute in atom:content), interpreting this as equivalent to having a link rel="enclosure" but having no content as description. Expect a summary element.

Ensure that link rel="enclosure" is used only for linking entries to their included files, and not entries to other entries.

Publications

If you hold information about publications, export this using the new Leap2A/publication type — a subtype of resource.

If you don't represent publications in any special way, import Leap2A/publications as you do resources in general. If there is an issued date (dcterms:issued) element, try to append this to the content/description.

Intermissions

If you hold information about time away from activities, use the new category "Intermission" to categorise an activity item as representing the time spent away from the containing activity. The Intermission activity should be represented as "part of" the whole activity.

Spatial

If you represent any spatial information as plain text, rather than structured address information, change the export from exporting as plain text to exporting as xhtml, as explained at Leap2A/literals#spatial.

Obviously this has implications for import as well.

Affiliation

If you represent anything like membership information, change from exporting a custom activity to exporting Leap2A/affiliation items, including the new myrole and roleid elements.

If you do not represent membership information, import affiliation entries as if they were activities, ideally appending any contents of myrole and roleid to the content/description.

Web resources

Leap2A/resources of type Web that are available publicly on the Web should be linked using link rel="self". A type attribute should be supplied.

Changing from HTML to XHTML content

If you export any content of type="html", with the markup escaped, please if you possibly can change this to xhtml, as explained in the content documentation. You may find HTML Tidy a useful resource. However, take care with empty content. If you give it as type xhtml, it should contain an empty div element. Otherwise, make it explicitly or implicitly type text.


Personal tools