The [SWORD] profile provides a number of useful extensions to the [AtomPub] protocol, some of which provide support for packaged data and rely on the identification of packaging types. This document provides a number of predefined types that implementers SHOULD use in order to promote interoperability between implementations. It also specifies the mechanism by which new content package types are incorporated into this document.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
|Name||REQUIRED. Short name to identify the type. MUST be unique in the scope of this document.|
|Description||REQURED. Text description of the purpose, utility and application of the type.|
|URI||REQUIRED. URI identifying this type. MUST be unique in
the scope of this document. Need not resolve.
Note: This field is not a direct replacement for the @formatNamespace attribute in SWORD 1.2. @formatNamespace implied the involvement of an XML namespace, the URI field here is not bound to an XML namespace, since it is not required that packaging types use XML at all.
|Specification Documentation||RECOMMENDED. URL of web resources providing technical documentation for the type.|
|IMS Content Packaging 1.1.x||For packaging e-learning content, including SCORM 1.2 and SCORM 2004 packages||http://www.imsglobal.org/xsd/imscp_v1p1||IMS Global|
|IMS Content Packaging 1.2||For packaging e-learning content, including SCORM 1.2 and SCORM 2004 packages||http://www.imsglobal.org/xsd/imscp_v1p2||IMS Global|
|IMS Common Cartridge||for packaging e-learning content, including SCORM 1.2 and SCORM 2004 packages||tbc||Common Cartridge Alliance|
[This section will define how new types can be added to this document].
[SWORD] Allinson, J. et al, SWORD AtomPub Profile version 1.3, October 2008.
[Atom] Nottingham, M. and R. Sayre, "The Atom Syndication Format", RFC 4287, December 2005. http://www.ietf.org/rfc/rfc4287.txt (see also non-normative html version at http://APP.org/rfc4287.html)
[AtomPub] Gregario, J. and B. de hOra, "The Atom Publishing Protocol", RFC 5023, October 2007. http://www.ietf.org/rfc/rfc5023.txt (see also non-normative html version at http://bitworking.org/projects/atom/rfc5023.html)
[HTTP1.1] Fielding et al, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999 http://www.w3.org/Protocols/rfc2616/rfc2616.html
[RFC2183] Troost, R., Dorner, S. and Moore, K., "Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field", RFC 2183, August 1997 http://www.ietf.org/rfc/rfc2183.txt
[OAUTH] Atwood, A., Conlan, R. et al OAuth Core 1.0 http://oauth.net/core/1.0/, December 2007
[ORE] Lagoze, C., Van de Sompel, H et al, Open Archives Initiative Object Reuse and Exchange, http://www.openarchives.org/ore/, June 2008
[RFC2617] Franks, J. et al, "HTTP Authentication: Basic and Digest Access Authentication". http://www.ietf.org/rfc/rfc2617.txt , June 1999
[RFC2818] Rescorla, E. "HTTP over TLS". http://www.ietf.org/rfc/rfc2818.txt, May 2000.
[RFC2119] Bradner, S. "Key words for use in RFCs to Indicate Requirement Levels". http://www.ietf.org/rfc/rfc2119.txt, March 1997.