[OASIS Issue Tracker] Created: (ODATA-426) Metadata URL for reference, link, deleted link, and deleted entity don't vary by service so shouldn't append to the service's metadata url

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

Metadata URL for reference, link, deleted link, and deleted entity don't vary by service so shouldn't append to the service's metadata url
------------------------------------------------------------------------------------------------------------------------------------------

                 Key: ODATA-426
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-426
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
         Environment: [Proposed]
            Reporter: Michael Pizzo


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