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-911) Miscellanous feedback (public comment c201602e00003)

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

Ralf Handl updated ODATA-911:

    Environment: Applying

> Miscellanous feedback (public comment c201602e00003)
> ----------------------------------------------------
>                 Key: ODATA-911
>                 URL: https://issues.oasis-open.org/browse/ODATA-911
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData JSON CSDL
>    Affects Versions: V4.0_CSD01
>         Environment: Applying
>            Reporter: Ralf Handl
>             Fix For: V4.0_CSD02
> Public Review Comment https://lists.oasis-open.org/archives/odata-comment/201602/msg00003.html.
> Summary
> - 4.1.1 prose text describing structure of "keys" array doesn't match example 6 
> (editor's note: example is correct, prose text is garbled)
> - Nullable Properties, Example 36: "format":"decimal" seems to be missing
> (editor's note: it is missing, should be there according to table in
> - a flag "nullable" would avoid the need to reverse-engineer this information from the type array tailored for validators
> (editor's note: this is currently discussed for Swagger, see https://github.com/OAI/OpenAPI-Specification/issues/229)
> - Path Expressions: The 2nd list does not contain @odata.navigationPropertyPath
> (editor's note: needs to be added)
> - Expression Apply: mismatch between prose text and example
> (editor's note: needs to be fixed)
> - Expression Not: can this contain annotations?
> (editor's note: yes)
> - Expression Null: Why do annotations not live next to @odata.null, like it is the case for @odata.if etc.? Comment gives two proposals for a simpler syntax
> (editor's note: if edm:Null is an item in a collection it needs to be represented as either just null or as an object. Could make that dependent on the existence of annotations within edm:Null or accept feature loss in JSON representation)
> - Expression UrlRef: The text does not fit to the example, but I think the example is better and should win ;-)
> (editor's note: agreed :-)

This message was sent by Atlassian JIRA

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