[ https://tools.oasis-open.org/issues/browse/ODATA-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36976#comment-36976 ]
Michael Pizzo commented on ODATA-630:
-------------------------------------
I brought this up with the JSON-LD folks. They don't think it's a problem since JSON-LD has it's own content type, and they have an extensibility mechanism that lets them basically rewrite the names of their well-known properties.
> 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)
