You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
4.1.2.5 Nullable Properties, Example 36: "format":"decimal" seems to be missing
(editor's note: it is missing, should be there according to table in 4.1.2.1)
4.5.3.2 Path Expressions: The 2nd list does not contain @odata.navigationPropertyPath
(editor's note: needs to be added)
4.5.3.6 Expression Apply: mismatch between prose text and example
(editor's note: needs to be fixed)
4.5.3.10 Expression Not: can this contain annotations?
(editor's note: yes)
4.5.3.11 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)
4.5.3.12 Expression UrlRef: The text does not fit to the example, but I think the example is better and should win ;-)
(editor's note: agreed :-)
Proposal
Apply to next draft revision
Introduce x-nullable keyword
Represent edm:Null just as null if it doesn't contain annotations
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)
4.1.2.5 Nullable Properties, Example 36: "format":"decimal" seems to be missing
(editor's note: it is missing, should be there according to table in 4.1.2.1)
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 add "null value support" in spec? OAI/OpenAPI-Specification#229)
4.5.3.2 Path Expressions: The 2nd list does not contain @odata.navigationPropertyPath
(editor's note: needs to be added)
4.5.3.6 Expression Apply: mismatch between prose text and example
(editor's note: needs to be fixed)
4.5.3.10 Expression Not: can this contain annotations?
(editor's note: yes)
4.5.3.11 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)
4.5.3.12 Expression UrlRef: The text does not fit to the example, but I think the example is better and should win ;-)
(editor's note: agreed :-)
Proposal
Apply to next draft revision
Introduce x-nullable keyword
Represent edm:Null just as null if it doesn't contain annotations
Imported from ODATA-911
The text was updated successfully, but these errors were encountered: