LEAP as Atom

Part of LEAP 2.0 and Portfolio interoperability prototyping

A Strawman by Scott Wilson edited by Simon

Can LEAP 2.0 be expressed using the existing IETF Atom specification?


 * Use the existing Atom:Entry element to express the basic LEAP entry
 * Use extensions to express any required specific attributes of subclasses of LEAP entry
 * Use Atom:Link:Enclosure within an Atom:Entry to express such things as a LEAP file (Simon adds: or if it stands for the content, then atomOutOfLineContent.)
 * Use Atom:Category to express tag links in LEAP. Use the Atom:Category:Scheme attribute to identify the source vocabulary for the term (e.g. competence, personality, interest) (Simon qualifies this in the discussion.)
 * Use Atom:Link to express LEAP relationships. E.g. LINK REL="evidences".

I think this looks doable. It also has the advantage that there are already Atom-aware but (obviously) LEAP-unaware parsers out there to test the "graceful degradation" aspects.