UserPreferences

PaceAllowOutOfLineCategoriesExtensions


Abstract

Allow extensions as content of app:categories when @href is specified.

Status

Proposed based on Draft-12

Rationale

There is demand for APP to have the facility to support other category functionality. There is argument that APP should provide just a baseline to support atom:category and any else should be done via extensions.

This proposal removes the restriction from app:categories elements that prevent extensions as content when app:categories has an href attribute (ie. references an out of line category document).

Example:

<collection href="1">
    <categories href="photo-sharing-site">
        <my-magic-thesaurus:lookup-tool href="2" />
        <my-magic-thesaurus:term-validation-tool href="3" />
        <my-magic-thesaurus:term-statistics-tool href="4" />
    </categories>
    <categories href="bookmarks-sharing-site">
        <my-magic-thesaurus:lookup-tool href="5" />
        <my-magic-thesaurus:term-validation-tool href="6" />
        <my-magic-thesaurus:term-statistics-tool href="7" />
    </categories>
</collection>

Proposal

In the last sentence of section 8.2.5, change this:

      If the "href" attribute is provided,  
      the app:categories element MUST be empty 
      and the "fixed" and "scheme" attributes MUST NOT be present.

to this:

      If the "href" attribute is provided,  
      the app:categories element MUST NOT contain any atom:category elements 
      and the "fixed" and "scheme" attributes MUST NOT be present.

The RELAX NG does not need to be updated to reflect this prose (thus resolving a discrepancy in draft-12).

Impacts

None

Notes


CategoryProposals