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-686) Alert clients that odata may be default namespace in future versions of the protocol


Michael Pizzo created ODATA-686:
-----------------------------------

             Summary: Alert clients that odata may be default namespace in future versions of the protocol
                 Key: ODATA-686
                 URL: https://tools.oasis-open.org/issues/browse/ODATA-686
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Sub-task
          Components: OData JSON Format
    Affects Versions: V4.0_OS
         Environment: [Proposed]
            Reporter: Michael Pizzo
             Fix For: V4.0_ERRATA01


OData control information is represented in a JSON payload as an annotation within the "odata" namespace. However, many services would like to return such control information without specifying the default "odata" namespace. ODATA-630 proposes allowing services to omit the "odata" namespace for OData control information, effectively making OData the default namespace. This would be more consistent with other formats such as JSON-LD.

It would be nice to make clients aware that this change is likely, to allow them to anticipate it when implementing their V4 implementations.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


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