[OASIS Issue Tracker] Updated: (ODATA-259) Add Annotation Groups to JSON format

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

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

Ralf Handl updated ODATA-259:
-----------------------------

    Environment:     (was: [Deferred])

> Add Annotation Groups to JSON format
> ------------------------------------
>
>                 Key: ODATA-259
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-259
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData JSON Format
>    Affects Versions: V4.0_WD01
>            Reporter: Ralf Handl
>             Fix For: V5.0_WD01
>
>
> Annotation values may vary per entity, so they can be included in the JSON representation if they deviate from the default specified in $metadata.
> A common case is that the lifecycle of an entity is decribed by a finite and typically small set of states, and that some or all instance annotations depend on the state only.
> So it would really compress JSON responses if the response could define several named groups of annotation values and refer to them in other entities.
> Example: as long as an order item hasn't been shipped, its quantity and delivery address can be updated. Once it has been shipped these properties become read-only. The first order item in state "shipped" defines an annotation group named "Shipped" that annotates the quantity- and address-related properties as read-only. Subsequent "shipped" items only refer to that group without having to repeat all annotations in that group.

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