view Side-By-Side changes
Network Working Group J. Snell Internet-DraftMay 23,June 17, 2007 Intended status: Standards Track Expires:November 24,December 19, 2007 Atom Publishing Protocol Features Extensiondraft-snell-atompub-feature-04.txtdraft-snell-atompub-feature-05.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire onNovember 24,December 19, 2007. Copyright Notice Copyright (C) The IETF Trust (2007). Abstract This document introduces extensions to the Atom Publishing Protocol introspection format for expressing metadata about the behaviors, functions and capabilities supported by an Atom Publishing Protocolserver implementation.collection. Snell ExpiresNovember 24,December 19, 2007 [Page 1] Internet-Draft APP FeaturesMayJune 2007 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Notational Conventions . . . . . . . . . . . . . . . . . . . . 3 3. The 'f:feature' element . . . . . . . . . . . . . . . . . . .34 3.1. Example . . . . . . . . . . . . . . . . . . . . . . . . .56 4. Security Considerations . . . . . . . . . . . . . . . . . . .56 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . .56 5.1. Registry of Atom Publishing Features . . . . . . . . . . .56 5.1.1. Initial Assignments . . . . . . . . . . . . . . . . .67 6. Normative References . . . . . . . . . . . . . . . . . . . . . 12 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 13 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 13 Intellectual Property and Copyright Statements . . . . . . . . . . 14 Snell ExpiresNovember 24,December 19, 2007 [Page 2] Internet-Draft APP FeaturesMayJune 2007 1. Introduction This document introduces extensions for the Atom Publishing Protocol service document format for expressing metadata about the behaviors, functions and capabilities supported by an Atom Publishing Protocolserver implementation.collection. 2. Notational Conventions 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 BCP 14, [RFC2119]. This specification uses XML Namespaces [W3C.REC-xml-names-19990114] to uniquely identify XML element names. It uses the following namespace prefix for the indicated namespace URI; "f": "http://purl.org/atompub/features/1.0" This specification uses terms from the XML Infoset [W3C.REC-xml-infoset-20040204]. However, this specification uses a shorthand; the phrase "Information Item" is omitted when naming Element Information Items. Therefore, when this specification uses the terms "element" and "attribute" it is referring, respectively, to the Element and Attribute Information Items in Infoset terms. This specification uses the terms "atomUri" and "atomCommonAttributes" from the non-normative RELAX NG Compact schema included in [RFC4287]. Where used, these serve the same purpose and have the same meaning as their use in [RFC4287]. Atom allows the use of IRIs [RFC3987]. Every URI [RFC3986] is also an IRI, so a URI may be used wherever below an IRI is named. There are two special considerations: (1) when an IRI that is not also a URI is given for dereferencing, it MUST be mapped to a URI using the steps in Section 3.1 of [RFC3987] and (2) when an IRI is serving as an identifier, it MUST NOT be so mapped. Any element defined by this specification MAY have an xml:base attribute [W3C.REC-xmlbase-20010627]. When xml:base is used in an, it serves the function described in section 5.1.1 of [RFC3986], establishing the base URI (or IRI) for resolving any relative references found within the effective scope of the xml:base attribute. Any element defined by this specification MAY have an xml:lang attribute, whose content indicates the natural language for the Snell Expires December 19, 2007 [Page 3] Internet-Draft APP Features June 2007 element and its descendents. The language context is only significant for elements and attributes declared to be "Language- Sensitive". Requirements regarding the content and interpretation of xml:lang are specified in XML 1.0 [W3C.REC-xml-20040204], Section 2.12. 3. The 'f:feature' element A feature is an abstract behavior, function and capability supported by an Atom Publishing Protocolserver.collection. Examples of features that might be supported by an APP server include support for draft entries, scheduled publication of entries, use of a particular set of Atom format extensions, use of a particular authentication scheme, and so on. The presence of a f:feature element in an app:collection element is an indication that the collection supports the feature specified and may require that a client wishing to use the endpoint use that feature. Features are identified using permanent, universally unique IRI's.Snell Expires November 24, 2007 [Page 3] Internet-Draft APP Features May 2007feature = element f:feature { atomCommonAttributes, attribute ref { atomUri }, attribute required { 'yes' | 'no' }?, attribute href { atomUri }?, attribute label { text }?, (anyElement)* } anyElement = element * - f:* { (attribute * { text } | text | anyElement)* } The "ref" attribute specifies a globally unique IRI identifying a feature supported by a collection. The value of the ref attribute MUST be compared on a case-sensitive, character-by-character basis. Relative references MUST NOT be used. A 'required' attribute value of "yes" indicates that clients MUST utilize the identified feature when interacting with the collection. A server MAY reject requests from clients that do not support or use the feature. If not specified, the value is assumed to be "no". An optional 'href' attribute MAY be used to specify the URI of a human-readable description of the feature. Relative references MAY be used. Snell Expires December 19, 2007 [Page 4] Internet-Draft APP Features June 2007 The optional 'label' attribute MAY be used to specify a human- readable label for the feature. The value of the 'label' attribute is Language-Sensitive as defined by Section 2 of [RFC4287]. The f:feature element MAY contain child elements and attributes other than those defined in this specification. Such "foreign markup" are considered to be metadata applicable to the feature identified by the f:feature element. Software agents MUST NOT stop processing or signal an error or change their behavior as a result of encountering such foreign markup. An app:collection element MAY contain zero or more f:feature elements but MUST NOT contain more than one with the same ref attribute value. The order in which f:feature elements appear within the app: collection element is insignificant. The f:feature element MAY contain attributes included as part of the atomCommonAttributes production defined by Section 2 of [RFC4287] or any update thereof. When used on an f:feature element, suchSnell Expires November 24, 2007 [Page 4] Internet-Draft APP Features May 2007attributes serve the same purpose described in [RFC4287] or their corresponding specifications. Snell Expires December 19, 2007 [Page 5] Internet-Draft APP Features June 2007 3.1. Example The following is an example of a collection supporting one hypothetical required feature and a number of optional features. <servicexmlns="..."> <workspace title="My Atom Service">xmlns="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:f="http://purl.org/atompub/features/1.0"> <workspace> <atom:title>My Workspace</atom:title> <collectiontitle="My Atom Collection"href="...">...<atom:title>My Atom Collection</atom:title> <accept>application/atom+xml;type=entry</accept> <f:featureref="http://purl.org/atom/app/drafts"ref="http://www.w3.org/2007/app/drafts" /> <f:featureref="http://purl.org/atom/app/xhtml-content"ref="http://www.w3.org/2007/app/xhtml-content" /> <f:featureref="http://purl.org/atom/app/preserve-extensions"ref="http://www.w3.org/2007/app/preserve-extensions" /> <f:feature ref="http://purl.org/syndication/thread/1.0" /> <f:feature ref="http://code.google.com/apis/gdata/GoogleLogin" href="http://code.google.com/apis/gdata/" label="Google Login" required="yes" /> </collection> </workspace> </app:server> 4. Security Considerations Specific features supported by a collection may introduce security considerations and concerns beyond those discussed by the Atom Publishing Protocol and Atom Syndication Format specifications. Implementors must refer to the specifications and description of each feature to determine the security considerations relevant to each. 5. IANA Considerations 5.1. Registry of Atom Publishing Features The Registry of Atom Publishing Features is maintained by IANA and contains information about known features that can be supported by Atom Publishing Protocol implementations. New assignments are subject to IESG approval, as outlined in [RFC2434]. Requests should be made by email to IANA, which will then forward the request to the IESG, requesting approval. The request should use the followingtemplate:Snell ExpiresNovember 24,December 19, 2007 [Page5]6] Internet-Draft APP FeaturesMayJune 2007 template: o Ref: (A globally unique IRI identifying the feature) o Label: (A human-readable label for the feature) o Description: (A human-readable description of the feature) o Href: (A URI referencing a document containing a detailed definition of the feature) o Security Considerations: 5.1.1. Initial Assignments The Registry of Features initially contains the following assignments: 5.1.1.1. Drafts -http://purl.org/atom/app/draftshttp://www.w3.org/2007/app/drafts o Ref:http://purl.org/atom/app/draftshttp://www.w3.org/2007/app/drafts o Label: Drafts o Description: The "Drafts" feature indicates that a collection supports the use of the app:draft control element as defined in section 13.1.1 of [I-D.ietf-atompub-protocol].o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations:5.1.1.2.Preserve EntriesXHTML Content -http://purl.org/atom/app/preserve-entryhttp://www.w3.org/2007/app/xhtml-content o Ref:http://purl.org/atom/app/preserve-entryhttp://www.w3.org/2007/app/xhtml-content o Label:Preserve EntriesXHTML Content o Description: The"Preserve Entries""XHTML Content" feature indicates that a server willpreserveaccept thesemantic contentuse ofentries POST and PUT toan XHTML value within thecollection without making any modifications. o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations:atom:content element. 5.1.1.3.Preserve IDsHTML Content -http://purl.org/atom/app/preserve-idhttp://www.w3.org/2007/app/html-content o Ref:http://purl.org/atom/app/preserve-idhttp://www.w3.org/2007/app/html-content o Label:Preserve IDsHTML Content o Description: The"Preserve IDs""HTML Content" feature indicates that a server willpreserveaccept theatom:iduse ofentries added to a collection. o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations: 5.1.1.4. XHTML Content - http://purl.org/atom/app/xhtml-content Snell Expires November 24, 2007 [Page 6] Internet-Draft APP Features May 2007 o Ref: http://purl.org/atom/app/xhtml-content o Label: XHTML Content o Description: The "XHTML Content" feature indicates that a server will accept XHTML within the atom:content element. o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations: 5.1.1.5. HTML Content - http://purl.org/atom/app/html-content o Ref: http://purl.org/atom/app/html-content o Label: HTML Content o Description: The "HTML Content" feature indicates that a server will acceptan escaped HTML value within theatom:contentatom: content element.o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations: 5.1.1.6.5.1.1.4. Text Content -http://purl.org/atom/app/text-contenthttp://www.w3.org/2007/app/text-content o Ref:http://purl.org/atom/app/text-contenthttp://www.w3.org/2007/app/text-content o Label: Text Content o Description: The "Text Content" feature indicates that a server will accept the use of a plain text value within the atom:content element.o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations: 5.1.1.7.Snell Expires December 19, 2007 [Page 7] Internet-Draft APP Features June 2007 5.1.1.5. XML Content -http://purl.org/atom/app/xml-contenthttp://www.w3.org/2007/app/xml-content o Ref:http://purl.org/atom/app/xml-contenthttp://www.w3.org/2007/app/xml-content o Label: XML Content o Description: The "XML Content" feature indicates that a server will accept the use of well-formed XML content within theatom:contentatom: content element.o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations: 5.1.1.8.5.1.1.6. Binary Content -http://purl.org/atom/app/binary-contenthttp://www.w3.org/2007/app/binary-content o Ref:http://purl.org/atom/app/xhtml-contenthttp://www.w3.org/2007/app/xhtml-content o Label: Binary Content o Description: The "Binary Content" feature indicates that a server will accept Base-64 encoded binary data within the atom:content element.Snell Expires November 24, 2007 [Page 7] Internet-Draft APP Features May 2007 o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations: 5.1.1.9.5.1.1.7. Referenced Content -http://purl.org/atom/app/src-contenthttp://www.w3.org/2007/app/src-content o Ref:http://purl.org/atom/app/ref-contenthttp://www.w3.org/2007/app/ref-content o Label: XHTML Content o Description: The "Referenced Content" feature indicates that a server will accept atom:content elements that use the src attribute to reference external content resources.o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations: 5.1.1.10.5.1.1.8. XHTML Title -http://purl.org/atom/app/xhtml-titlehttp://www.w3.org/2007/app/xhtml-title o Ref:http://purl.org/atom/app/xhtml-titlehttp://www.w3.org/2007/app/xhtml-title o Label: XHTML Title o Description: The "XHTML Title" feature indicates that a server will accept the use of an XHTML value within the atom:title element.o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations: 5.1.1.11.5.1.1.9. HTML Title -http://purl.org/atom/app/html-titlehttp://www.w3.org/2007/app/html-title o Ref:http://purl.org/atom/app/html-titlehttp://www.w3.org/2007/app/html-title o Label: HTML Title o Description: The "HTML Content" feature indicates that a server will accept the use of an escaped HTML value within the atom:title element.o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations: 5.1.1.12.5.1.1.10. Text Title -http://purl.org/atom/app/text-titlehttp://www.w3.org/2007/app/text-title o Ref:http://purl.org/atom/app/text-titlehttp://www.w3.org/2007/app/text-title o Label: Text Title o Description: The "Text Content" feature indicates that a server will accept the use of a plain text value within the atom:title element.o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations:Snell ExpiresNovember 24,December 19, 2007 [Page 8] Internet-Draft APP FeaturesMayJune 20075.1.1.13.5.1.1.11. XHTML Summary -http://purl.org/atom/app/xhtml-summaryhttp://www.w3.org/2007/app/xhtml-summary o Ref:http://purl.org/atom/app/xhtml-summaryhttp://www.w3.org/2007/app/xhtml-summary o Label: XHTML Summary o Description: The "XHTML Summary" feature indicates that a server will accept the use of an XHTML value within the atom:summary element.o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations: 5.1.1.14.5.1.1.12. HTML Summary -http://purl.org/atom/app/html-summaryhttp://www.w3.org/2007/app/html-summary o Ref:http://purl.org/atom/app/html-summaryhttp://www.w3.org/2007/app/html-summary o Label: HTML Summary o Description: The "HTML Summary" feature indicates that a server will accept the use of an escaped HTML value within theatom:summaryatom: summary element.o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations: 5.1.1.15.5.1.1.13. Text Summary -http://purl.org/atom/app/text-summaryhttp://www.w3.org/2007/app/text-summary o Ref:http://purl.org/atom/app/text-summaryhttp://www.w3.org/2007/app/text-summary o Label: Text Summary o Description: The "Text Summary" feature indicates that a server will accept the use of a plain text value within the atom:summary element.o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations: 5.1.1.16.5.1.1.14. Auto Summary -http://purl.org/atom/app/auto-summaryhttp://www.w3.org/2007/app/auto-summary o Ref:http://purl.org/atom/app/auto-summaryhttp://www.w3.org/2007/app/auto-summary o Label: Auto Summary o Description: The "Auto Summary" feature indicates that a server will autogenerate the value of the atom:summary element and will either reject or ignore attempts by the client to modify the value of atom:summary.o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations: 5.1.1.17.5.1.1.15. XHTML Rights -http://purl.org/atom/app/xhtml-rightshttp://www.w3.org/2007/app/xhtml-rights o Ref:http://purl.org/atom/app/xhtml-rightshttp://www.w3.org/2007/app/xhtml-rights o Label: XHTML RightsSnell Expires November 24, 2007 [Page 9] Internet-Draft APP Features May 2007o Description: The "XHTML Rights" feature indicates that a server will accept the use of an XHTML value within the atom:rights element.o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations: 5.1.1.18.5.1.1.16. HTML Rights -http://purl.org/atom/app/html-rightshttp://www.w3.org/2007/app/html-rights o Ref:http://purl.org/atom/app/html-rightshttp://www.w3.org/2007/app/html-rights o Label: HTML Rights o Description: The "HTML Rights" feature indicates that a server will accept the use of an escaped HTML value within theatom:rightsatom: rights element.o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations: 5.1.1.19.Snell Expires December 19, 2007 [Page 9] Internet-Draft APP Features June 2007 5.1.1.17. Text Rights -http://purl.org/atom/app/text-rightshttp://www.w3.org/2007/app/text-rights o Ref:http://purl.org/atom/app/text-rightshttp://www.w3.org/2007/app/text-rights o Label: Text Rights o Description: The "Text Rights" feature indicates that a server will accept the use of a plain text value within the atom:rights element.o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations: 5.1.1.20.5.1.1.18. Authenticated Author -http://purl.org/atom/app/auth-authorhttp://www.w3.org/2007/app/auth-author o Ref:http://purl.org/atom/app/auth-authorhttp://www.w3.org/2007/app/auth-author o Label: Authenticated Author o Description: The "Authenticated Author" feature indicates that a server will use the authenticated identity of the client to determine the values to use within the atom:author element. Attempts by a client to manually set or modify the author information will either be rejected or ignored by the server. 5.1.1.19. Slug - http://www.w3.org/2007/app/slug oHref: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txtRef: http://www.w3.org/2007/app/slug oSecurity Considerations:Label: Slug o Description: The "Slug" feature indicates that a server will use the Slug request header defined in section 9.7 of [I-D.ietf-atompub-protocol] to set the URI of newly created resources. 5.1.1.20. Multiple Categories - http://www.w3.org/2007/app/multiple-categories o Ref: http://www.w3.org/2007/app/multiple-categories o Label: Multiple Categories o Description: The "Multiple Categories" feature indicates that a server will accept entries that contain multiple atom:category elements. 5.1.1.21.Preserve UpdatedMultiple Authors -http://purl.org/atom/app/preserve-updatedhttp://www.w3.org/2007/app/multiple-authors o Ref:http://purl.org/atom/app/preserve-updatedhttp://www.w3.org/2007/app/multiple-authors o Label:Preserve UpdatedMultiple Authors o Description: The"Preserve Updated""Multiple Authors" feature indicates that a server will accept and preservethe value of the atom:updated element providedmultiple atom:author elements contained bya client.an entry. Snell ExpiresNovember 24,December 19, 2007 [Page 10] Internet-Draft APP FeaturesMayJune 2007o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations:5.1.1.22.Preserve ExtensionsMultiple Contributors -http://purl.org/atom/app/preserve-extensionshttp://www.w3.org/2007/app/multiple-contributors o Ref:http://purl.org/atom/app/preserve-extensionshttp://www.w3.org/2007/app/contributors o Label:Preserve ExtensionsMultiple Contributors o Description: The"Preserve Extensions""Multiple Contributors" feature indicates that a server will accept and preservearbitrary unknown foreign markupatom:contributor elements containedwithinby an entry.o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations:5.1.1.23. PreserveLinksInfoset - http://www.w3.org/2007/app/preserve-infoset Label: Preserve Infoset Description: The "Preserve Infoset" feature indicates that a server will preserve the complete XML XML Infoset [W3C.REC-xml-infoset-20040204] of entries POST or PUT to a collection. 5.1.1.24. Preserve IDs -http://purl.org/atom/app/preserve-linkshttp://www.w3.org/2007/app/preserve-id o Ref:http://purl.org/atom/app/preserve-linkshttp://www.w3.org/2007/app/preserve-id o Label: PreserveLinksIDs o Description: The "PreserveLinks"IDs" feature indicates that a server will preserveall atom:linkthe value of atom:id elementscontained within an entry. o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations: 5.1.1.24.as provided by a client. 5.1.1.25. PreserveLinksDates -http://purl.org/atom/app/preserve-rightshttp://www.w3.org/2007/app/preserve-dates o Ref:http://purl.org/atom/app/preserve-rightshttp://www.w3.org/2007/app/preserve-updated o Label: PreserveRightsDates o Description: The "PreserveRights"Dates" feature indicates that a server will preserveall atom:rightsthe value of the atom:updated and atom:published elementscontained within an entry. o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations: 5.1.1.25. Slugas provided by a client. 5.1.1.26. Preserve Extensions -http://purl.org/atom/app/slughttp://www.w3.org/2007/app/preserve-extensions o Ref:http://purl.org/atom/app/slughttp://www.w3.org/2007/app/preserve-extensions o Label:SlugPreserve Extensions o Description: The"Slug""Preserve Extensions" feature indicates that a server willuse the Slug request header defined in section 9.7 of [I-D.ietf-atompub-protocol] to set the URI of newly created resources. o Security Considerations:preserve unknown foreign markup contained within an entry. 5.1.1.27. Preserve Links - http://www.w3.org/2007/app/preserve-links Snell ExpiresNovember 24,December 19, 2007 [Page 11] Internet-Draft APP FeaturesMayJune 20075.1.1.26. Multiple Categories - http://purl.org/atom/app/multiple-categories o Ref: http://purl.org/atom/app/multiple-categories o Label: Multiple Categories o Description: The "Multiple Categories" feature indicates that a server will accept entries that contain multiple atom:category elements. o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations: 5.1.1.27. Contributors - http://purl.org/atom/app/contributorso Ref:http://purl.org/atom/app/contributorshttp://www.w3.org/2007/app/preserve-links o Label:ContributorsPreserve Links o Description: The"Contributors""Preserve Links" feature indicates that a server willaccept andpreserveatom:contributorall atom:link elements containedbywithin an entry.o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations:5.1.1.28.Multiple AuthorsPreserve Rights -http://purl.org/atom/app/multiple-authorshttp://www.w3.org/2007/app/preserve-rights o Ref:http://purl.org/atom/app/multiple-authorshttp://www.w3.org/2007/app/preserve-rights o Label:Multiple AuthorsPreserve Rights o Description: The"Multiple Authors""Preserve Rights" feature indicates that a server willaccept andpreservemultiple atom:authorall atom:rights elements and License Links [I-D.snell-atompub-feed-license] containedbywithin an entry.o Href: http://www.ietf.org/internet-drafts/ draft-ietf-atompub-protocol-14.txt o Security Considerations:5.1.1.29.Feed ThreadThreading - http://purl.org/syndication/thread/1.0 o Ref: http://purl.org/syndication/thread/1.0 o Label:Feed ThreadThreading o Description: The Feed Thread feature indicates that the APP server accepts entries that contain the in-reply-to element as defined by [RFC4685].o Security Considerations:6. Normative References [I-D.ietf-atompub-protocol] Hora, B. and J. Gregorio, "The Atom Publishing Protocol",Snell Expires November 24, 2007 [Page 12] Internet-Draft APP Featuresdraft-ietf-atompub-protocol-15 (work in progress), May2007 draft-ietf-atompub-protocol-142007. [I-D.snell-atompub-feed-license] Snell, J., "Atom License Extension", draft-snell-atompub-feed-license-11 (work in progress), March 2007. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005. [RFC3987] Duerst, M. and M. Suignard, "Internationalized Resource Identifiers (IRIs)", RFC 3987, January 2005. Snell Expires December 19, 2007 [Page 12] Internet-Draft APP Features June 2007 [RFC4287] Nottingham, M., Ed. and R. Sayre, Ed., "The Atom Syndication Format", RFC 4287, December 2005. [RFC4685] Snell, J., "Atom Threading Extensions", RFC 4685, September 2006.[W3C.REC-xml-infoset-20040204] Cowan, J.[W3C.REC-xml-20040204] Yergeau, F., Maler, E., Bray, T., Paoli, J., andR.C. Sperberg-McQueen, "Extensible Markup Language (XML) 1.0 (Third Edition)", World Wide Web Consortium FirstEdition REC-xml-20040204, February 2004, <http://www.w3.org/TR/2004/REC-xml-20040204>. [W3C.REC-xml-infoset-20040204] Tobin, R. and J. Cowan, "XML Information Set (Second Edition)", World Wide Web Consortium Recommendation REC- xml-infoset-20040204, February 2004, <http://www.w3.org/TR/2004/REC-xml-infoset-20040204>. [W3C.REC-xml-names-19990114]Bray, T.,Hollander, D., Bray, T., and A. Layman, "Namespaces in XML", World Wide Web Consortium FirstEdition REC-xml- names-19990114, January 1999, <http://www.w3.org/TR/1999/REC-xml-names-19990114>. [W3C.REC-xmlbase-20010627] Marsh, J., "XML Base", World Wide Web Consortium Recommendation REC-xmlbase-20010627, June 2001, <http://www.w3.org/TR/2001/REC-xmlbase-20010627>. Appendix A. Acknowledgements The author acknowledges the feedback from Elias Torres, Robert Yates, David Johnson, Byrne Reese, Joe Gregorio, Bill de hO`ra and the other members of the IETF Atom Publishing working group during the development of this specification. Author's Address James M Snell Phone: Email: jasnell@gmail.com URI: http://snellspace.com Snell ExpiresNovember 24,December 19, 2007 [Page 13] Internet-Draft APP FeaturesMayJune 2007 Full Copyright Statement Copyright (C) The IETF Trust (2007). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). Snell ExpiresNovember 24,December 19, 2007 [Page 14] ----