[OASIS Issue Tracker] Created: (ODATA-351) Define ID, ReadLink and EditLink in Part 1: Protocol, define representation in Atom and JSON

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

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
         Environment: [Proposed]
            Reporter: Ralf Handl
             Fix For: V4.0_WD01


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