OData TC face-to-face meeting #73 Thursday May 15, 2014 and Friday May 16, 2014

Day 1 - Thursday May 15, 2014

Chairs: Ralf and Ram

Acting Chair: Ram

Chat transcript from room: odatatc
2014-05-15 GMT-08:00

1. Roll call

Quorum achieved

2. Approve agenda

Agenda approved as published.

3. Approve minutes from previous meeting(s)

3.1 Minutes from May 1, 2014 TC meeting:

URL=Minutes of 2014-05-01 Meeting#72

Minutes approved unchanged as published

4. Review action items

URL=Action item list

4.1 Action items due by May 15, 2014

None

5. Process issues

(we will use the red-lined OData v4 docs incorporating errata as we process the issues)

All go through the changes by using a shared screen session

The documents are edited during the shared sessions to embed the agreed resolutions

Stefan: In case someone is interested in ISO stages of standards life cycle: http://www.iso.org/iso/stage_codes.pdf

Acting Chair: Ralf

The following issues have been OPENed during the meeting:

Status: OPEN

Hubert: I move to resolve issues ODATA-580, ODATA-600, ODATA-640, ODATA-643, ODATA-645, ODATA-650, ODATA-651, ODATA-652, ODATA-654, ODATA-657, ODATA-660, ODATA-661, ODATA-663, ODATA-668, ODATA-669, ODATA-670, ODATA-671, ODATA-672 and ODATA-673 as proposed. Stefan seconds

No objections the motion carries

Ralf: We will resume the formal meeting Friday 16-05-2014 9:00 AM PDT

Day 2 - Friday May 16, 2014

Chairs: Ralf and Ram

Acting Chair: Ram

Chat transcript from room: odatatc
2014-05-16 GMT-08:00

Changes on ABNF

Ralf does a WebSVN walkthrough of the ABNF versions.

5(Day 2) Issues that are in Applied state

5.1(Day 2) OData v4 Errata issues in Applied state (action: close as applied)

As a servcice these issues may be referenced in eventual motions as "the issues listed above":

  1. ODATA-580: 8.2.4 If-Match should refer to term Core.OptimisticConcurrency [Open]
  2. ODATA-600: Ensure future compatibility by reference to draft-bray-i-json-n (The I-JSON Message Format) [Open]
  3. ODATA-640: NavigationPropertyBinding cannot be annotated
  4. ODATA-643: Clarify that PUT must persist all "updatable" properties
  5. ODATA-645: Default for PUT/PATCH is not to return data [Open]
  6. ODATA-650: Clarify the use of $format in delta links and next links
  7. ODATA-651: Chapter 3: Rephrase "An entity can be a member of at most one entity set at any given point in time" [Open]
  8. ODATA-652: Errors in CSDL "16.1 Products and Categories Example" and "15.4 Properties"
  9. ODATA-654: OData-EntityId is only required for 204 No Content, but client may need it when server doesn't support canonical URLs
  10. ODATA-657: Clarity needed about if/when Control Information" must be specified in payload sent from client to server
  11. ODATA-660: Clarify whether or not PATCH can be used to update a primitive property using its edit URL
  12. ODATA-661: Chapter 15: describe key format for EnumTypeMember in MetadataService
  13. ODATA-663: Clarify construction rules for calling function in $filter
  14. ODATA-668: Fix minor editorial issues
  15. ODATA-669: Clarify that metadataEtag should be supported in minimal metadata
  16. ODATA-670: Clarify behavior wrt If-Match header on a GET request
  17. ODATA-671: The signature of the cast function uses an incorrect return-type. [Open]
  18. ODATA-672: Clean up definition of TargetPath and description of Target in navigation property binding, action import, and function import
  19. ODATA-673: Annotation target path syntax insufficient to annotate contained entity sets
  20. ODATA-559: Clarify that Derived types inherit HasStream property
  21. ODATA-562: 5.1.1.4.29: cast function is optional for first four rules
  22. ODATA-564: 5.1.1.4.28: define "assignable"
  23. ODATA-565: 2: Clarify interpretation of path segments and query option values with respect to percent-encoded punctuation
  24. ODATA-566: 6.2.4 Attribute Scale: clarify allowed range of Scale values
  25. ODATA-569: Allow type-cast segment after function/action call in path expressions
  26. ODATA-570: Clarify behavior of edm:UrlRef expression
  27. ODATA-578: Contains example has order of arguments backwards
  28. ODATA-587: Add example for complex value that is an empty object
  29. ODATA-590: Leading zeroes in values for $level
  30. ODATA-591: Part1, examples 36-40: replace "associated" with "related"
  31. ODATA-592: JSON example 11: "type":"Point" with uppercase P according to GeoJSON spec
  32. ODATA-597: Seeking clarification of naming for GeographyCollection with GeoJSON
  33. ODATA-598: Update JSON RFC reference
  34. ODATA-599: Let's update the GeoJSON reference
  35. ODATA-602: Explicitly state what's allowed after /$all
  36. ODATA-603: Primitive type Edm.Stream: use as type of collection, input parameter, return type, or underlying type of type definition
  37. ODATA-604: Add type cast segment for complex types in rules for $select and $expand
  38. ODATA-607: Section 4.5.4: explicitly state that @odata.count can be applied to expanded to-many navigation properties
  39. ODATA-608: Explicitly state that the path segment /$count can be combined with $search and $filter, and that the calculated count is identical to $count=true
  40. ODATA-609: Section 11.4.4 Upsert: key values in URL win over key values in request body
  41. ODATA-610: 11.4.4: Upsert and server-generated keys
  42. ODATA-611: Explicitly state that the service root URL ends with a forward-slash
  43. ODATA-612: Consistently use "edit link" and "edit URL"
  44. ODATA-620: Replace "scalar type" with "primitive type" and "scalar property" with "structural property"
  45. ODATA-621: Clarify: Specifying an unbound function with overloads in a function import should import all overloads of that function to the entity container
  46. ODATA-623: 11.4.3: be more specific on updating key properties
  47. ODATA-624: Clarify that (clients and) services may include additional format parameters in Content-Type header.
  48. ODATA-625: Add example for UrlRef in attribute notation
  49. ODATA-633: Rule pct-encoded-unescaped unintentionally omits hex pairs starting with 7
  50. ODATA-634: Specify the behaviour when a non-nullable property with no default value is omitted from a PUT
  51. ODATA-635: Clarify if a PUT request is allowed to change the odata.type of the entity (public comment c201403e00002)
  52. ODATA-636: Clarify that complex types and arrays can only be passed to functions through parameter aliases
  53. ODATA-637: ATOM and JSON formats do not define representation of operation results
  54. ODATA-638: Clarify Delta responses with Minimal Metadata
  55. ODATA-639: MetadataService.edmx: Schema annotations have to be represented inline
  56. ODATA-641: MetadataService.edmx: Property IncludeInServiceDocument is missing for entity type EntitySet
  57. ODATA-642: $select wording clarification; specify, rather than restrict, set of properties
  58. ODATA-644: Example 18 should use "Orders" instead of "Items"
  59. ODATA-646: Clarify; returning content from a data modification should be same as GET
  60. ODATA-647: Define "Edit URL" of primitive property
  61. ODATA-567: Rule hour does not allow 20
  62. ODATA-568: ABNF rules for headers list percent-encoded whitespace

Hubert: I move to close the issues listed above as applied. Mike seconds

No objections the motion carries

5.2(Day 2) OData v4 Errata issues in Closed state (action: close with no action)

  1. ODATA-594: Discrepancy between ATOM and JSON formats (GML, GeoJson) for Polygon information content
  2. ODATA-605: Annotation target path syntax insufficient to annotate contained entity sets
  3. ODATA-632: "Core.OptimisticConcurrencyControl" should be "Core.OptimisticConcurrency"

Hubert: I move to close ODATA-594, ODATA-605 and ODATA-632 as proposed with no action. Matt seconds

No objections the motion carries

5.3(Day 2) Issues that recently showed up

  1. ODATA-676: Clarify that clients shoudl not validate based on applies to attribute
  2. ODATA-675: Enumeration member values SHOULD be represented using the member name and not the integer member value

Discussion:

Hubert: I move to resolve ODATA-676 and ODATA-675 as proposed. Mike seconds

No objections the motion carries

Mike: I move to close ODATA-675 and ODATA-676 as applied. Hubert seconds

No objections the motion carries

No other issues on errata processing

6. Errata document walkthrough

Martin walks through Errata doc

All discuss relationship among related work, specifications, and references

7. Further additional standardization

Ram walks trough ISO process for ODATA acceptance

Ram discusses PASS submitter process

8. Reviewing the errata docs

Ralf walks through the remaining ERRATA issues

All put the documents in final shape for upload ...

Stefan: I move that the TC approve OData JSON Format v4.0 Errata Draft 01 Working Draft 01 and the accompanying OData JSON Format v4.0 OASIS Standard (marked version) incorporating the proposed errata corrections all contained in https://www.oasis-open.org/committees/download.php/53055/odata-json-format-v4.0-errata01-wd01-2014-05-16.zip as Errata Draft 01 to the OData JSON Format v4.0 OASIS Standard approved on 24 February 2014 and confirm that the errata corrections do not constitute Substantive Changes to the Standard. Further, I move that the TC approve submitting OData JSON Format v4.0 Errata Draft 01 contained in https://www.oasis-open.org/committees/download.php/53055/odata-json-format-v4.0-errata01-wd01-2014-05-16.zip for 15 day public review. Mike seconds

No objections the motion carries

Martin: I move that the TC approve OData v4.0 Errata Draft 01 Working Draft 01 and the accompanying OData v4.0 OASIS Standard (marked version) incorporating the proposed errata corrections all contained in https://www.oasis-open.org/committees/download.php/53057/odata-v4.0-errata01-wd01-2014-05-16.zip as Errata Draft 01 to the OData v4.0 OASIS Standard approved on 24 February 2014 and confirm that the errata corrections do not constitute Substantive Changes to the Standard. Further, I move that the TC approve submitting OData v4.0 Errata Draft 01 contained in https://www.oasis-open.org/committees/download.php/53057/odata-v4.0-errata01-wd01-2014-05-16.zip for 15 day public review. Matt seconds

No objections the motion carries

All discuss the next steps

9. Topics for afternoon session with focus "OData Future Directions"

Mike suggests ossible discussion topics for afternoon session:

Stefan adds:

Mark and Stefan are interested in the Implementing OData paper

Update from afternoon session on OData Future Directions

V4.1 Issues
FAQ
Tips & Tricks
Interpretations
Specific Scenarios
Other Technologies
Designing a Data Model
Extending OData

End of Update from afternoon session

10. Next meeting planned for May, 29 (tentatively)

Agreed

11. AOB

None

Meeting adjourned