[OASIS Issue Tracker] Updated: (ODATA-389) JSON: use odata.kind values "Entity" and "deletedEntity"

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

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

Ralf Handl updated ODATA-389:
-----------------------------

        Summary: JSON: use odata.kind values "Entity" and "deletedEntity"  (was: Use odata.kind values "Entity" and "deletedEntity" instead of "Entry" and "deletedEntry")
       Proposal: 
Atom: use metadata:link and metadata:deleted-link instead of metadata:link-entry and metadata:deleted-link-entry

JSON: use odata.kind values "entity", "deletedEntity", "link", and "deletedLink" instead of "entry", "deletedEntry", "linkEntry", and "deletedLink"

  was:Use values entity, deletedEntity, link, deletedLink

    Component/s: OData ATOM Format 
    Description: 
The current naming of the odata.kind values "Entry", "deletedEntry", and "linkEntry" in JSON reflects the "Atom-origin" of the OData formats.

We now consistently use of "entity" when speaking in OData terminology and use "entry" only when intentionally using the Atom terminology, so it is odd to have Atom terminology in the new JSON format. Also different parts of the JSON document use different values, unintentionally reflecting the change history of this concept.

To increase consistency between JSON and Atom the OData-specific "link" and "deletedLink" are better represented using medata:link and metadata:deleted-link without the suffix "-entry". This is also more consistent with Atom as these OData-specific elements reflect changes to the atom:link element.

  was:
The current naming of the values reflects the "Atom-origin". 

We now consistently use of "entity" when speaking in OData terminology and use "entry" only when intentionally using the Atom terminology, so it is odd to have Atom terminology in the new JSON format.

Also different parts of the document use different values, unintentionally reflecting the change history of this concept


> JSON: use odata.kind values "Entity" and "deletedEntity"
> --------------------------------------------------------
>
>                 Key: ODATA-389
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-389
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData ATOM Format , OData JSON Format
>    Affects Versions: V4.0_CSD01
>         Environment: [Applied]
>            Reporter: Ralf Handl
>            Priority: Minor
>             Fix For: V4.0_CSD02
>
>
> The current naming of the odata.kind values "Entry", "deletedEntry", and "linkEntry" in JSON reflects the "Atom-origin" of the OData formats.
> We now consistently use of "entity" when speaking in OData terminology and use "entry" only when intentionally using the Atom terminology, so it is odd to have Atom terminology in the new JSON format. Also different parts of the JSON document use different values, unintentionally reflecting the change history of this concept.
> To increase consistency between JSON and Atom the OData-specific "link" and "deletedLink" are better represented using medata:link and metadata:deleted-link without the suffix "-entry". This is also more consistent with Atom as these OData-specific elements reflect changes to the atom:link element.

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