← Prev in month ← Prev in thread

[OASIS Issue Tracker] (ODATA-630) Consider making odata the default namespace for annotations

From
OASIS Issues Tracker <>
Date
2014-03-26T06:26:26+00:00
ID
JIRA.23580.1395815089577.360.1395815190969@customer-jira-611
Thread
[OASIS Issue Tracker] (ODATA-630) Consider making odata the default namespace for annotations
Michael Pizzo created ODATA-630:
-----------------------------------

             Summary: Consider making odata the default namespace for annotations
                 Key: ODATA-630
                 URL: https://tools.oasis-open.org/issues/browse/ODATA-630
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: OData JSON Format
    Affects Versions: V4.0_OS
         Environment: [Proposed]
            Reporter: Michael Pizzo
             Fix For: V4.1_WD01


OData control information is represented in a JSON payload using annotations in the odata namespace, such as:
"@odata.nextlink":"http://..."
For services that want the payload to look as much as possible like handcrafted json, the fact that "odata" is explicitly called out in the payload is a distraction.

We might make it easier for services to ease into OData's JSON format by making odata the default namespace, such that the same annotation could be written equivalently as:
"@nextlink":"http://..."



--
This message was sent by Atlassian JIRA
(v6.1.1#6155)
← Prev in month ← Prev in thread