[OASIS Issue Tracker] (ODATA-648) Ambiguity between prose and examples for atom:category element

Evan Ireland created ODATA-648:
----------------------------------

             Summary: Ambiguity between prose and examples for atom:category element
                 Key: ODATA-648
                 URL: https://tools.oasis-open.org/issues/browse/ODATA-648
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: OData ATOM Format 
    Affects Versions: V4.0_CSD02
            Reporter: Evan Ireland
            Priority: Minor
             Fix For: V4.0_ERRATA01


It appears there is some ambiguity in the (draft) spec.

  http://docs.oasis-open.org/odata/odata-atom-format/v4.0/cs02/odata-atom-format-v4.0-cs02.html#_Toc372792708

See the snippet below. The prose says there must be a “scheme” attribute, but the examples show a “rel” attribute.

----

6.3 Element atom:category
An OData entry MUST contain a single atom:category element with a scheme attribute equal to
http://docs.oasis-open.org/odata/ns/scheme 
to identify the entity type of the entry. 
An atom:category element describing an OData entity type MUST have a term attribute whose value is a URI indicating the type of the entity. The URI may be an absolute or relative URL containing the namespace-qualified or alias-qualified type name as a fragment, or may simply contain the qualified type name prefixed with hash (#). In the latter case, the type MUST be defined or referenced in the metadata document defined by the current context URL.
Example 6: entity of type Model.VipCustomer defined in the metadata document of the same service
<category rel="http://docs.oasis-open.org/odata/ns/scheme"
term="#Model.VipCustomer"/>
Example 7: entity of type Model.VipCustomer defined in the metadata document of a different service
<category rel="http://docs.oasis-open.org/odata/ns/scheme"
term="http://host/alternate/$metadata#Model.VipCustomer"/>
For more information on namespace-qualified and alias-qualified names, see [OData-CSDL]. 
The entry MAY contain additional atom:category elements with different scheme values; such atom:category elements have no semantic meaning in OData.




--
This message was sent by Atlassian JIRA
(v6.2.2#6258)