Abstract
In an implementation of APP that I'm putting together, we need the ability to unambiguously (and without human intervention) identify the various collections in a workspace based on their role. For instance, we have a main entry collection, we have a trash collection, etc. Given that we will be localizing the value of the title attribute, it would be very helpful to have some kind of id or role attribute for collections in the introspection. To address the problem, I suggest allowing a collection element to contain one atom:id element whose value is identical to the atom:id in the feed representing the collection.
<service xml:lang="de"> <workspace title="..."> <collection title="Meine Eintragungen" href="..."> <member-type>entry</member-type> <atom:id>tag:example.org,2006:entries</atom:id> </collection> <collection title="Mein Abfall" href="..."> <member-type>entry</member-type> <atom:id>tag:example.org,2006:trash</atom:id> </collection> </workspace> </service>
Status
Withdrawn
Rationale
There is currently no way of unambiguously identifying collections in an introspection workspace.
Proposal
Modify Section 7.2.3 of draft -07 to:
The "app:collection" describes a collection. This specification defines one child element: app:member-type. appCollection = element app:collection { appCommonAttributes, attribute title { text }, attribute href { text }, ( appMemberType & atomId? & extensionElement* ) }
Add Section 7.2.5
7.2.5 The "atom:id" Element The "app:collection" element MAY contain one atom:id element whose value specifies the atom:id value of the Atom Feed Document referenced by the "app:collection" element's "href" attribute.