Leap2A spec changes

Belongs to 2009-03/Leap2A specification

This is a record of changes, starting with those agreed at the meeting on 2008-07-10, up to the 2009-03 version of Leap2A, including only minor corrections since then. Future work is being carried forward at http://wiki.leapspecs.org/2A/spec_changes

2010-02
The orthography of the specification has been changed from "LEAP2A" to "Leap2A". This is retrospective, so that all versions will be called Leap2A, but will take some time to ensure that all appropriate instances of "LEAP2A" have been changed.

2009-07-14

 * A clarification has been added to 2009-03/Leap2A literals, clarifying that empty  leap:date elements, while not being encouraged, are not prohibited.

2009-03-25

 * The leap:field attribute values "im" and "voip" have been removed from persondata

2009-03-16

 * The term "Assessor" has been added to the person type category scheme

2009-03-12
A first stable version has been drafted at 2009-03/Leap2A specification.

Structured content has been revised and agreed.

2009-03-07

 * The term "Politics" has been added to the life area category scheme
 * The term "Note" has been added to the common item category scheme
 * The term "Printed" has been added to the resource type category scheme, and the term "Physical" redefined to exclude printed materials.

2009-02-27
Outcomes of the Huddersfield meeting.
 * Recognised that there is no need for a separate ordered part relationship, merged into the ordinary part relationships.
 * display_order removed as an optional attribute for persondata and orgdata elements.
 * A common item category scheme introduced, for personal statements and other items that may come up in the future.
 * A person type category scheme introduced, to distinguish significant types of person.
 * The documentation for resources changed to clarify the rules for how to include short summary descriptions (in the summary element) and how to link to alternate representations.

2009-02-06
Reasonable consensus reached on structured content, included in the spec.

2009-02-05
Introduced organization as a separate type, in parallel with person. As person does, organization also has its own data structures - see 2009-03/Leap2A organizational data. Organizational addresses also to be held in spatial elements, as with person.

2009-02-04
Reached a reasonably stable consensus on the person type, to hold names, contact details, and similar data relevant to CVs and presentations, and it corresponding data structures, specified in 2009-03/Leap2A personal data.

Agreed that addresses will be held in spatial elements, as addresslines, postcode and country.

2009-01-09
has ordered part and inverse respecified so that they use atom:link elements like all the other Leap2A relationshipa, with extra attributes. (Later withdrawn and instead merged with ordinary part relationships.)

2008-12-05
Added leap:activetime for time spent engaged in an activity.

2008-11-28
All the dc: namespace names changed to their leap: namespace names, for ease of reading and programming. It will remain clear that the names are exact equivalents.

2008-11-05
Whereas W3C date time formats were specified everywhere, it has been clarified that atom:published and atom:updated require rfc3339. See Time fields

2008-08-07
The name of the spec is now LEAP2A. This means that "PIOP" refers just to the project, which is less confusing and more appropriate. In particular, "PIOP_categories" has been changed to "Leap2A_categories".

2008-07-16
The life area category scheme introduced, in response to categories appearing in an example from Nottingham.

types
Goal has been dropped as a separate type, as no one was using it. Effectively, the goal is wrapped in to the plan.

relationships
Because we want to allow all relationships to be listed at both ends, attends has been introduced as the inverse of attended by.

The reference and presentation relationships were also dropped (for now at least) as not currently needed. Reference is implied by other relationships. The concept of presentation was not clearly agreed in any case.

Added a new relationship, reflects on, to distinguish entries in which reflections on other things are recorded.

The proposed sequencing relationships (follows, precedes, next) were not being used and were abandoned. A new element, leap:has_ordered_part was introduced. This was later withdrawn.

categories
The language ones have been moved back to being just possible, because they have not been tested in use yet.

A new one has been introduced for selection type.