UserPreferences

PaceRemoveOutOfLineCategoriesFromCategoryDocument


Abstract

Defines the root of a Category Document as appInlineCategories only, forbidding the use of an appOutOfLineCategories element in this case.

Status

Open

Rationale

As discussed [WWW]on the list, a Category Document consisting of a single appOutOfLineCategories is useless (redirections should use HTTP-level redirections) and bugprone.

Proposal

In protocol-10, remove the second paragraph of section 7.2.1.1 and fix the RNC as follows:

atomCategory =
    element atom:category {
       atomCommonAttributes,
       attribute term { text },
       attribute scheme { atomURI }?,
       attribute label { text }?,
       undefinedContent
    }

appInlineCategories =
    element app:categories {
        appCommonAttributes,
        attribute fixed { "yes" | "no" }?,
        attribute scheme { atomURI }?,
        (atomCategory*)
    }

appCategories = appInlineCategories

(Note that appInlineCategories has been fixed to include appCommonAttributes).

Don't forget to fix the RNC schema in Appendix B.

Impacts

Simplifies Category Document processing.

Notes

The RNC schema could directly define appCategories without the indirection of appInlineCategories.


CategoryProposals