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

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://tools.oasis-open.org/issues/browse/ODATA-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36974#comment-36974 ] 

Ralf Handl edited comment on ODATA-630 at 4/2/14 5:29 PM:
----------------------------------------------------------

This may lead to conflicts with JSON-LD (http://www.w3.org/TR/json-ld/ ): they already use @context, @id, and @type in their payloads, and we'd have to check whether these unprefixed annotations have compatible  semantics and interpretation of values.


was (Author: ralfhandl):
This may lead to conflicts with JSON-LD: they already use @context, @id, and @type in their payloads, and we'd have to check whether these unprefixed annotations have compatible  semantics and interpretation of values.

> 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)