[OASIS Issue Tracker] Updated: (ODATA-447) Rename Metadata URL to Context and make it structured information

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

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

Ralf Handl updated ODATA-447:
-----------------------------

        Summary: Rename Metadata URL to Context and make it structured information  (was: Rename Metadata URL to Context URL)
       Proposal: 
JSON
- rename the odata.metadata annotation to odata.context
- make it an object with properties
-- url: string
-- set: string
-- type: string (qualified name, (relative) url, "$ref")
-- projection: array of selected properties as strings or objects, the latter having name-value pairs name, recursive, projection

Atom
- replace the metadata:metadata attribute with a metadata:context element
- structure is
-- url: xs:anyUri
-- set: SimpleIdentifier
-- type: string
-- projection: ...

No change to the odata.metadata=none | full | minimal in the json format parameter.

In the docs refer to the "odata context".

  was:
rename the odata.metadata annotation (JSON) and metadata:metadata attribute (ATOM) to odata.context and metadata:context.
no change to the odata.metadata=none | full | minimal in the json format parameter.
in the docs, likely refer to the "odata context".

    Description: 
We've been adding a lot of information into the metadata URL: the metadata base URL, the entity set, the derived type, the selected properties, ...

This requires clients to parse this string, taking away some of the simplicity of using transport formats for structured data (JSON, XML).

> Rename Metadata URL to Context and make it structured information
> -----------------------------------------------------------------
>
>                 Key: ODATA-447
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-447
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ABNF Construction Rules, OData ATOM Format , OData CSDL, OData JSON Format, OData Protocol , OData URL Conventions 
>    Affects Versions: V4.0_CSD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_CSD02
>
>
> We've been adding a lot of information into the metadata URL: the metadata base URL, the entity set, the derived type, the selected properties, ...
> This requires clients to parse this string, taking away some of the simplicity of using transport formats for structured data (JSON, XML).

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