[OASIS Issue Tracker] (ODATA-561) odata.type shouldn't require "#" for primitive types

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

     [ https://issues.oasis-open.org/browse/ODATA-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-561:
--------------------------------

    Proposal: 
For 4.01 responses, the # is optional for primitive types.

Responses must only be returned without the "#" if the request does not specify odata.maximumversion=4.0.

Clients must only specify payloads that omit the "#" to services that support 4.01.

> odata.type shouldn't require "#" for primitive types
> ----------------------------------------------------
>
>                 Key: ODATA-561
>                 URL: https://issues.oasis-open.org/browse/ODATA-561
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData JSON Format
>    Affects Versions: V4.0_COS
>         Environment: Simplified Payload;[Proposed]
>            Reporter: Michael Pizzo
>            Assignee: Michael Pizzo
>            Priority: Minor
>              Labels: AdoptionBlocker, GoodIdea
>             Fix For: V4.01_WD01
>
>
> In JSON we currently require primitive types to be written as fragments, i.e.:
> "@odata.type":"#Double"
> The hash is not really required in this case, and doesn't really make sense as it is not a reference within the metadata document. Note that, in Atom, it is written without the hash, as in:
> <metadata:Salary metadata:type="Double">50000</metadata:Salary>
> In order not to make a breaking change for JSON we should continue to allow, but not require, the "#" for primitive types.
> Perhaps even add to an implementation note for 4.0 that clients should support primitive types without the "#".



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