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] (ODATA-795) Support annotations for expanded references

Michael Pizzo created ODATA-795:

             Summary: Support annotations for expanded references
                 Key: ODATA-795
                 URL: https://issues.oasis-open.org/browse/ODATA-795
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: OData JSON CSDL
    Affects Versions: V4.0_ERRATA02
         Environment: [Proposed]
            Reporter: Michael Pizzo
             Fix For: V4.0_ERRATA03

In OData V4 we have added the concept of fetching related references through appending /$ref to the navigation. This returns a result semantically more similar to RDF, which returns ids of related elements.

Some services, particularly in constrained environments, may be only be able to return the keys of related references. These services push the burden of the work on the client to build the graph from the individual pieces.

In other cases, especially for small nested/contained results, the service might only be able to represent the related elements as expanded relationships. 

We already support both of these representations, and having services return them in this format (even without an expand) is legal, but we don't have a way to tell the client that the service does this by default and may not support expand.

We should recognize such services exist and provide a way to tell clients of this behavior.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]