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-1135) Document use of JSON $schema

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

Ralf Handl commented on ODATA-1135:

After cross-checking with JSON Schema draft 04 as well as the latest draft 07 it seems that the $schema keyword is only intended for JSON Schema documents to refer to their meta-schema, and that the presence of the $schema keyword suggests to clients that the JSON document it appears in is actually a JSON SChema document.

As CSDL JSON documents are no longer JSON Schema documents, a $schema keyword in a CSDL JSON document seems rather misleading, so we should rather remove it from the csdl.schema.json file. As we luckily never mentioned it in the CSDL JSON specification and explicitly state that the prose document has precedence over the csdl.schema.json file, this can be claimed as an error correction and non-material change.

> Document use of JSON $schema
> ----------------------------
>                 Key: ODATA-1135
>                 URL: https://issues.oasis-open.org/browse/ODATA-1135
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: CSDL JSON 
>            Reporter: George Ericson
>            Priority: Minor
> JSON recommends specification of the $schema attribute for validation.
> The specification silently supports this.
> Need to make this explicit.

This message was sent by Atlassian JIRA

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