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] Commented: (ODATA-351) Define ID, ReadLink and EditLink in Part 1: Protocol, define representation in Atom and JSON

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

Michael Pizzo commented on ODATA-351:

-I would not use absence of a readlink to imply transience, as this optimizes what is likely to be the less common case (transient entities) at the expense of the more common case where the entity can be refreshed. I would instead define a value (odata.id=null?) making it explicit that an entry is transient.
-I don't think there's any value in defining an odata.id for a JSON feed; I don't know what the client would do with this information and it just bloats the response with unnecessary "control" information.
-I think there is only marginal value in having a selflink for JSON, and would support removing it as well

-currently the feed's self link does not encode query options; it is the url for the parent resource (I.e., collection). This is nice, because (for updatable services) it gives you the link of the resource you can post to for the relevant collection. However, I'm not really sure the self link is very interesting for a feed, and would support removing it all together.
-ids for transient entities in ATOM is tricky. We could do <id/>, or (if we think that would break ATOM parsers), define some convention like <id>transient;{some-unique-identiifer}</id>

> Define ID, ReadLink and EditLink in Part 1: Protocol, define representation in Atom and JSON
> --------------------------------------------------------------------------------------------
>                 Key: ODATA-351
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-351
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ATOM Format , OData JSON Format, OData Protocol 
>    Affects Versions: V4.0_WD01, V4.0_CSD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_CSD02
> In certain situations, especially Data Aggregation, we need the concept of "transient" entities and feeds in addition to the already defined "addressable" entities and feeds.
> Protocol should define the concepts ID, ReadLink and EditLink.
> Restrictions due to Atom and AtomPub
> - ID required, MUST be IRI
> - Feed: MAY have Self-Link to re-retrieve THIS feed 
> - Entry
> -- Links are optional
> -- <link rel="self"> identifies resource equivalent to current resource
> -- AtomPub: <link rel="edit"> can be used to retrieve, update, and delete the Resource represented by that Entry

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]