RE: Agenda for OData TC face-to-face meeting Thursday May 15, 2014 and F

From: Ram Jeyaraman (MS OPEN TECH)
Sent: Wednesday, May 14, 2014 11:21 PM
To: odata@lists.oasis-open.org
Subject: Agenda for OData TC face-to-face meeting Thursday May 15, 2014 and Friday May 16, 2014

Here [1] is a draft agenda for the OData TC (Technical Committee) face-to-face meeting scheduled on Thursday May 15, 2014 and Friday May 16, 2014 during 9am – 12noon PT on both days.

The meeting will be held in Building 99, room 2300. Upon arrival at building 99, please have the receptionist contact Mike Pizzo, or contact Mike directly @ 425 765-2286. For logistics, refer to https://lists.oasis-open.org/archives/odata/201405/msg00031.html.

For additional information, such as dial-in details and chat room, refer to [2]. For TC timeline, see [3]. Feel free to suggest additions or modifications.

Thanks.

[1] Agenda for the OData TC face-to-face meeting Thursday May 15, 2014 and Friday May 16, 2014

Thursday May 15, 2014

1. Roll call [9:00am PT]

a. Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=37713

2. Approve agenda [9:05am PT]

3. Approve minutes from previous meeting(s) [9:10am PT]

a. Minutes from May 1, 2014 TC meeting: https://www.oasis-open.org/committees/download.php/52887/odata-meeting-72_on-20140501-minutes.html

4. Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [9:15am PT]

a. Action items due by May 15, 2014

i. None

5. Process issues [9:20am PT] (we will use the red-lined OData v4 docs incorporating errata as we process the issues)

a. OData v4 Errata issues in New or Open state with an [Applied] flag (action: resolve as proposed and close as applied)

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

b. OData v4 Errata issues in Resolved state with an [Applied] flag (action: close as applied)

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

c. OData v4 Errata issues in Applied state (action: close as applied)

61. ODATA-567: Rule hour does not allow 20

62. ODATA-568: ABNF rules for headers list percent-encoded whitespace

d. OData v4 Errata issues in Closed state (action: close with no action)

63. ODATA-594: Discrepancy between ATOM and JSON formats (GML, GeoJson) for Polygon information content

64. ODATA-605: Annotation target path syntax insufficient to annotate contained entity sets

65. ODATA-632: "Core.OptimisticConcurrencyControl" should be "Core.OptimisticConcurrency"

e. OData v4 Errata issues in New state (new arrivals with no review so far) (action: resolve as proposed)

66. None

Friday May 16, 2014

6. Review the OData v4 and OData JSON Format v4 errata working drafts [9am PT]

a. We will review the errata docs (list of corrections) prepared by the editors

7. Review timeline and next steps [9:30am PT]

a. See [3] below

8. OData v4 Errata Draft 01 and OData JSON Format v4 Errata Draft 01 approval [9:40am PT]

a. Sample motion: I move that the TC approve OData v4.0 Errata Working Draft 01 (<URL to file in TC’s Kavi document repository>) and the accompanying OData v4.0 OASIS Standard (marked version) incorporating the proposed errata corrections contained in <URL to ZIP file in TC's Kavi document repository> as an 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 <URL to file in TC's Kavi document repository> for 15 day public review.

b. Sample motion: I move that the TC approve OData JSON Format v4.0 Errata Working Draft 01 (<URL to file in TC’s Kavi document repository>) and the accompanying OData JSON Format v4.0 OASIS Standard (marked version) incorporating the proposed errata corrections contained in <URL to ZIP file in TC's Kavi document repository> as an 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 <URL to file in TC's Kavi document repository> for 15 day public review.

9. Other topics [10am PT]

a. We will discuss progress on other normative and non-normative work products and related topics of interest

10. Next meeting [11:50am PT]

a. Thursday March 29, 2014 @ 8am PT?

11. AOB and wrap up [11:55am PT]

[2] References

· Conference call details: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/46401/TC%20meeting%20dial-in%20details.htm

· Chat room: http://webconf.soaphub.org/conf/room/odatatc

[3] Timeline

· https://www.oasis-open.org/apps/org/workgroup/odata/download.php/52831/TC%20Timeline%207.htm

odata message