[OASIS Issue Tracker] Commented: (ODATA-246) IDs should be dereferenceable URIs

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

    [ http://tools.oasis-open.org/issues/browse/ODATA-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32651#action_32651 ] 

Michael Pizzo commented on ODATA-246:
-------------------------------------

ODATA-276, if accepted, addresses the issue with $links.

I don't think we can *require* that the ID be the self-link, as the link for a resource may change even though its identity remains the same (i.e., it's moved to a different server). I think we can say, in JSON, that the self-link is only returned if it differs from the ID (in fact, I think we already say that, at least for minimal metadata).

I think this ends up being a strong recommendation, and perhaps a requirement for a particular conformance level, but not a MUST in the normative spec.

> IDs should be dereferenceable URIs
> ----------------------------------
>
>                 Key: ODATA-246
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-246
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol 
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>            Assignee: Michael Pizzo
>             Fix For: V4.0_WD01
>
>
> In OData, entity instances have unique ids.
> In addition, ATOM defines selflinks, for refreshing the contents of an entry, and editlinks for updating the contents of an entry. In our JSON format we have said that the self/edit links are only written if they are different from the ID, and the ID is not written if it can be generated from the payload based on conventions (i.e., if the payload contains the key fields, and the service supports the convention for looking indexing a set by key, such as ~/Customers('ALFKI').
> Ids can also be used in place of entries in navigation links to reduce payload size, in deltas to represent relationships and deleted entries, and can be explicitly selected using $ref.
> $links, on the other hand, returns a "canonical URL" for the related entity.
> In order to be a better citizen of the Semantic Web, in addition to supporting the types of optimizations that we have in JSON and other uses of ids, we should state that IDs are URIs and recommend to service implementers that those URIs be dereferenceable. Then we can say that the URLs returned by $links are the same as the values returned by $id, etc.

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