[OASIS Issue Tracker] Updated: (ODATA-202) Custom Mapping to Atom Elements not defined

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Michael Pizzo updated ODATA-202:
--------------------------------

    Environment: [Proposed]
     Resolution: Remove references to ATOM mapping in Section 9 and throughout.

I would rather not add a format-specific mapping to CSDL. Instead, if the committee feels it would be valuable, I would suggest defining an atom-specific vocabulary for specifying such a mapping.

> Custom Mapping to Atom Elements not defined
> -------------------------------------------
>
>                 Key: ODATA-202
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-202
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData ATOM Format v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: WD01
>
>
> Section 9 "Custom Mapping to Atom Elements" mentions that property values may be mapped to predefined atom elements or custom content within an entry. It then refers to CSDL, which also doesn't define this mapping.

-- 
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