OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (ODATA-828) Update I-JSON reference

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

Ralf Handl updated ODATA-828:

    Fix Version/s: V4.0_ERRATA03
                       (was: V4.0_ERRATA01)

> Update I-JSON reference
> -----------------------
>                 Key: ODATA-828
>                 URL: https://issues.oasis-open.org/browse/ODATA-828
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData JSON Format
>    Affects Versions: V4.0_OS
>         Environment: [Applied]
>            Reporter: Stefan Drees
>            Assignee: Hubert Heijkers
>            Priority: Minor
>             Fix For: V4.0_ERRATA03
> The JSON RFC 4627 has been obsoleted. Let's update the references. The new RFC has widened a bit it's scope, but takes care to suggest keeping the old constraints allowing only array and object as top level elements for valid JSON text when interoperability is in focus (like is in our use cases).
> RFC 7159 became proposed standard only days after our products became standard, so it is not really an erratum, but it might be good style, to place info such as this inside an erratum to have an early indication on the future direction of a 4.1 or 5.0 as service to the users and decision help for international standardization bodies where our OASIS Standard might be submitted to. 

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]