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-525) Remove Org.OData.Atom vocabulary

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

Ralf Handl updated ODATA-525:

Remove the Org.OData.Atom.xml vocabulary from the [Atom] work product.

Also remove the Atom vocabulary from the title page and the normative references
Remove second paragraph of section 6.1

  was:Remove the Org.OData.Atom.xml vocabulary from the [Atom] work product.

    Component/s: OData ATOM Format 

> Remove Org.OData.Atom vocabulary
> --------------------------------
>                 Key: ODATA-525
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-525
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData ATOM Format , Vocabularies
>    Affects Versions: V4.0_CS01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.0_CS02
> The Org.OData.Atom vocabulary defines the annotation terms that can be used to map properties to Atom elements. This is similar to an "Entity Property Mapping" feature in OData V3.
> The rules in OData V3 for how to do the mapping, the semantics and results of the mapping, were pretty complex (which is why we removed them from the OASIS spec). People wanted to be able to map to structured terms, repeating terms, etc. 
> The vocabulary was introduced as a cleaner, simpler way to specify that properties of the entity can be mapped to some of the defined Atom elements (like title, author, etc.)
> However, there isn't really a description of the vocabulary, just a bunch of terms that don't really describe how they are intended to be used. Also, the terms are incomplete (they are missing the "Author" term, for example). 
> Furthermore, our general intention is that vocabularies, which we expect to be more dynamic, be produced through the ecosystem, rather than through OASIS. The only exceptions to this rule are the Core, Capabilities and Aggregation vocabularies that we defined as part of the [Protocol] and [Aggregation] work products because we needed to normatively reference them.

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]