[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-630) Consider making odata the default namespace for annotations
[ https://issues.oasis-open.org/browse/ODATA-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Pizzo updated ODATA-630: -------------------------------- Environment: Simplified Payload;[Propposed] (was: Simplified Payload) > Consider making odata the default namespace for annotations > ----------------------------------------------------------- > > Key: ODATA-630 > URL: https://issues.oasis-open.org/browse/ODATA-630 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Improvement > Components: OData JSON Format > Affects Versions: V4.0_OS > Environment: Simplified Payload;[Propposed] > Reporter: Michael Pizzo > Assignee: Michael Pizzo > Labels: AdoptionBlocker > Fix For: V4.01_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.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]