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-426) Metadata URL for nested objects can be relative to metadata URL of enclosing object


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

Ralf Handl updated ODATA-426:
-----------------------------

       Proposal: 
Specify in JSON that metadata URLs of "nested" objects are relative to the metadata URL of the enclosing object, thus shortening the metadata URL of references, links, deleted links, and deleted entities in collections to just

#$ref
#$link
#$deletedLink
#$deletedEntity

This allows single references to point back to their originating service, and is even shorter for the other three as these so far only appear within delta responses, i.e. wrapped in a collection.

Accepted: https://www.oasis-open.org/committees/download.php/49447/odata-meeting-40_on-20130606-minutes.html#odata-426

  was:
Specify in JSON that metadata URLs of "nested" objects are relative to the metadata URL of the enclosing object, thus shortening the metadata URL of references, links, deleted links, and deleted entities in collections to just

#$ref
#$link
#$deletedLink
#$deletedEntity

This allows single references to point back to their originating service, and is even shorter for the other three as these so far only appear within delta responses, i.e. wrapped in a collection.


    Environment: [Applying]  (was: [Proposed])
       Assignee: Ralf Handl

> Metadata URL for nested objects can be relative to metadata URL of enclosing object
> -----------------------------------------------------------------------------------
>
>                 Key: ODATA-426
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-426
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData JSON Format
>    Affects Versions: V4.0_CSD01
>         Environment: [Applying]
>            Reporter: Michael Pizzo
>            Assignee: Ralf Handl
>             Fix For: V4.0_CSD02
>
>
> In odata-422, we define a metadataurl representation for references, as well as links, deleted links, and deleted entities. This replaced "odata.kind" and established the metadataurl as the single place to look to understand what a particular object represented.
> However, understanding that a particular JSON object represents a reference, link, deleted link, or deleted entity is not dependent upon the base metadataurl of the service. these are defined by odata.
> Thus, the metadata urls should not depend on the metadataurl of the service, but should be defined relative to a (virtual) odata url. for example:
> {metadata-url}#$ref                  =>  odata:#ref 
> {metadata-url}#@deletedEntity  =>  odata:#deletedEntity
> {metadata-url}#@link                =>  odata:#link
> {metadata-url}#@deletedLink    =>   odata:#deletedLink

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