OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Updated: (ODATA-133) Attributes defined on odata elements should be in empty namespace

     [ http://tools.oasis-open.org/issues/browse/ODATA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-133:

        Fix Version/s: WD01
    Affects Version/s: WD01

> Attributes defined on odata elements should be in empty namespace
> -----------------------------------------------------------------
>                 Key: ODATA-133
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-133
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData ATOM Format v1.0, OData CSDL v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>            Assignee: Michael Pizzo
>            Priority: Minor
>             Fix For: WD01
> Attributes of elements defined within the odata metadata namespace should not be defined in the empty namespace.
> It is common practice, when defining an element and attributes within that element, not to namespace the attributes. For example, the <atom:link> element defines attributes for rel, href, title and so forth. These attributes are not in the atom namespace, because atom defines the element. This allows the link element to be written without having to namespace qualify all of the attributes, as:
>        <atom:link rel="..." href="..." title="..."/>
> Note that attributes do not inherit the namespace of their element (or any other implicit namespace); unprefixed attributes always live in an empty namespace.
> Currently , a number of elements defined within the odata namespace have attributes that are (erroneously) defined within that namespace. This would require each attribute to be namespace qualified, as in:
>       <edm:Property edm:Name="FirstName" edm:Type="Edm.String"/>
> This was not the intention, and not how the examples are shown.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]