RE: [odata] Agenda for OData TC meeting on 2015-06-18

Room information was updated by: Stefan

Please register your self at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=39103 (now open)

Stefan: Voting Members: 1 of 14 (7%) (used for quorum calculation)

Stefan: Voting Members: 2 of 14 (14%) (used for quorum calculation)

anonymous2 morphed into Matt Borges (SAP)

Stefan: Voting Members: 4 of 14 (28%) (used for quorum calculation)

Ralf Handl (SAP): Voting Members: 9 of 14 (64%)

Ralf Handl (SAP): Achieved quorum

Ralf Handl (SAP): 2.Approve agenda

Ralf Handl (SAP): Agenda is approved

Ralf Handl (SAP): 3.Approve minutes from previous meeting

Ralf Handl (SAP): a.Minutes from June 11, 2015 TC meeting: https://www.oasis-open.org/committees/download.php/55912/odata-meeting-99_on-20150611-minutes.html

Ralf Handl (SAP): Minutes are approved

anonymous morphed into Mark Biamonte (Progress)

Ralf Handl (SAP): 4.Review Timeline

Ralf Handl (SAP): a.https://www.oasis-open.org/committees/document.php?document_id=55904&wg_abbrev=odata

Ralf Handl (SAP): Draft timeline for OData Work Products

         July 2015

o   Internal review of Extension for Data Aggregation Version 4.0 WD03

o   Initiate public review of Extension for Data Aggregation Version 4.0 CSD03

         September 2015

o   Internal review of Extension for Temporal Data Version 4.0 WD01

o   Start work on OData Core and JSON Version 4.1 WD01

o   Internal review of JSON Format for CSDL Version 4.0 WD01

         October 2015

o   Initiate publication of Extension for Data Aggregation Version 4.0 CS02

o   Initiate public review of Extension for Temporal Data Version 4.0 CSD01

o   Initiate public review of JSON Format for CSDL Version 4.0 CSD01

         November 2015

o   Initiate public review of OData Core and JSON Version 4.1 CSD01

o   Start work on REST Profile for OData Version 4.1 WD01

         December 2015

         January 2016

o   Internal review of REST Profile for OData Version 4.1 WD01

o   Initiate public review of JSON Format for CSDL Version 4.0 CSD02

         February 2016

o   Initiate public review of Extension for Temporal Data Version 4.0 CSD02

         March 2016

o   Initiate public review of REST Profile for OData Version 4.1 CND01

o   Initiate publication of JSON Format for CSDL Version 4.0 CS01

         April 2015

o   Initiate publication of Extension for Temporal Data Version 4.0 CS01

         May 2016

o   Initiate public review of OData Core and JSON Version 4.1 CSD02

o   Initiate public review of REST Profile for OData Version 4.1 CND02

         June 2016

o   Initiate publication of OData Core and JSON Version 4.1 CS01

o   Initiate publication of REST Profile for OData Version 4.1 CN01

Ralf Handl (SAP): Goals for V4.1

Ralf Handl (SAP): Mike: replan for having V4.1 CS01 as early as possible (February 2016?)

Ralf Handl (SAP): Then if necessary have V4.1 CS02 in June 2016

Ralf Handl (SAP): TC will switch back to weekly meeting cycle from September 2015

Ralf Handl (SAP): 5.Process issues

Ralf Handl (SAP): a.Issues for V4.0_ERRATA03 in Applied state

Ralf Handl (SAP): i.Procedure

1.Review documents up-front for correct issue application

2.No live walk-through of the documents during the TC meeting

3.Discuss application of individual issues where necessary

4.Reject application of individual issues where necessary

5.Summarily move to close undisputed issues

Ralf Handl (SAP): ii. Issues

1.ODATA-479 Allow Content-ID referencing in request bodies for inserting links to newly created entities

2.ODATA-731 Explicitly state that JSON service documents may contain annotations

3.ODATA-732 Add enumeration member "Write" to "Permission" type

4.ODATA-733 Clarify handling of cycles in Extends for EntityContainers

5.ODATA-734 Unicode Facet is inadequate

6.ODATA-740 Let's update the GeoJSON reference (again)

7.ODATA-741 Mismatch between explanatory text and URL in example 96

8.ODATA-742 Usage of domain contoso.com and term name contoso in examples

9.ODATA-745 Sections 4.5.5, 7.3, and 7.4: is odata.nextLink allowed for all collections?

10.ODATA-746 12.2.3: IsComposable - clarify what is allowed even if set to false

11.ODATA-748 Section 4.5.4: odata.count needs to be allowed for all collections

12.ODATA-749 What should service return when attempting to related two entities that are already related?

13.ODATA-750 Explicitly mention the @ sign in instance annotations

14.ODATA-751 Clarification of Edm.NavigationPropertyPath and Edm.PropertyPath

15.ODATA-752 Bug in example 47

16.ODATA-753 Minor typo in references to bound function calls

17.ODATA-754 Clarify that numeric enum values are serialized as strings

18.ODATA-755 Construction rule for canonical URL is incomplete

19.ODATA-756 Clarify when odata.metadataEtag will be returned

20.ODATA-758 Example 81: wrong parameter style

21.ODATA-761 11.5.4.1 Invoking an Action: Location header for 201 Created responses

22.ODATA-762 Section 8.5: clarify that @odata.bind:null is valid for updating of 0..1 navigation properties

23.ODATA-765 Example 77 (invoking an action): show complex parameters

24.ODATA-766 8.2.4 and 8.2.5 should refer to RFC7232 (public comment c201501e00001)

25.ODATA-767 Adapt Acknowledgements

26.ODATA-768 Remove superfluous text after references

27.ODATA-769 5.2 Model Versioning: allow adding a new term to the model

28.ODATA-770 18.2: incomplete description of annotation name format

29.ODATA-771 Exponential notation for Edm.Decimal values in JSON payloads

30.ODATA-773 Qualifiers for instance annotations: JSON Format

31.ODATA-774 Qualifiers for annotations: Preference odata.include-annotations

32.ODATA-775 Should allow use of parameter aliases for key lookup

33.ODATA-776 Clarify function invocation

34.ODATA-777 Clarify multiply/divide duration by number

35.ODATA-778 Example in section 11.7.3.1, "Referencing Requests in a Change Set", should use JSON, not ATOM

36.ODATA-779 Org.OData.Core.V1 defines Term IsURL but references it as IsUrl

37.ODATA-780 indexof: what to return if the second argument does not appear in the first argument

38.ODATA-782 Example 57: choose better example

39.ODATA-783 Is it intentional that mindatetime/maxdatetime/now don't permit %-encoded parentheses in ABNF?

40.ODATA-787 Clarify how odata.Include-annotations preference affects odata.* markup

41.ODATA-788 Clarify precidence rules for odata.include-annotations preference

42.ODATA-789 Primitive type Edm.Decimal is ill-defined in regard to Precision

43.ODATA-790 Bug in example 70

44.ODATA-791 11.2.5.2 System Query Option $orderby: specify order of Edm.Boolean and Edm.Geo

45.ODATA-793 Expand * on complex type

46.ODATA-794 11.4.2.2: Create Related Entities When Creating an Entity

47.ODATA-795 Support annotations for expanded references

48.ODATA-796 Add annotation to specify whether additional properties may be returned for an entity

49.ODATA-797 Org.OData.Capabilities.V1 term property FilterRestrictions/RequiresFilter has wrong facets

50.ODATA-801 Consider supporting negative scale for decimal type

51.ODATA-803 Collection-valued property: Define default value for nullable facet

52.ODATA-806 Wrong description in capabilities vocabulary in term SearchRestrictions

53.ODATA-807 Don't need TargetId in a deleted link for a to 0..1 relationship

54.ODATA-808 ODATA-796 Minor changes to new OnlyDeclaredProperties annotation

55.ODATA-810 Part 3, 14.1.5 uses IsURI instead of IsURL

56.ODATA-815 Clarify that the values of the format parameters odata.metadata etc. are case-insensitive

Ralf Handl (SAP): iii.Documents

1.https://www.oasis-open.org/committees/download.php/55616/odata-v4.0-wd08-part1-protocol-2015-05-07.docx

2.https://www.oasis-open.org/committees/download.php/55614/odata-v4.0-wd08-part2-url-conventions-2015-05-07.docx

3.https://www.oasis-open.org/committees/download.php/55611/odata-v4.0-wd08-part3-csdl-2015-05-07.docx

4.https://www.oasis-open.org/committees/download.php/55921/odata-json-format-v4.0-wd08-2015-06-18.docx

5.https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/vocabularies/Org.OData.Core.V1.xml

6.https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/vocabularies/Org.OData.Capabilities.V1.xml

Ralf Handl (SAP): Mike commented ODATA-754

Ralf Handl (SAP): Section 7.1 reformulated

Ralf Handl (SAP): Enumeration values are represented as JSON strings whose content satisfies the rule enumValue in [OData-ABNF]. The preferred representation is the enumerationMember. If no enumerationMember (or combination of named enumeration members) is available, the enumMemberValue representation may used.

Ralf Handl (SAP): "rule" was missing in first sentence

Ralf Handl (SAP): iv. Summary Motion

1.I move to close ODATA-479, ODATA-731, ODATA-732, ODATA-733, ODATA-734, ODATA-740, ODATA-741, ODATA-742, ODATA-745, ODATA-746, ODATA-748, ODATA-749, ODATA-750, ODATA-751, ODATA-752, ODATA-753, ODATA-754, ODATA-755, ODATA-756, ODATA-758, ODATA-761, ODATA-762, ODATA-765, ODATA-766, ODATA-767, ODATA-768, ODATA-769, ODATA-770, ODATA-771, ODATA-773, ODATA-774, ODATA-775, ODATA-776, ODATA-777, ODATA-778, ODATA-779, ODATA-780, ODATA-782, ODATA-783, ODATA-787, ODATA-788, ODATA-789, ODATA-790, ODATA-791, ODATA-793, ODATA-794, ODATA-795, ODATA-796, ODATA-797, ODATA-801, ODATA-803, ODATA-806, ODATA-807, ODATA-808, ODATA-810, and ODATA-815 as applied.

Martin Zurmuehl: I move to close ODATA-479, ODATA-731, ODATA-732, ODATA-733, ODATA-734, ODATA-740, ODATA-741, ODATA-742, ODATA-745, ODATA-746, ODATA-748, ODATA-749, ODATA-750, ODATA-751, ODATA-752, ODATA-753, ODATA-754, ODATA-755, ODATA-756, ODATA-758, ODATA-761, ODATA-762, ODATA-765, ODATA-766, ODATA-767, ODATA-768, ODATA-769, ODATA-770, ODATA-771, ODATA-773, ODATA-774, ODATA-775, ODATA-776, ODATA-777, ODATA-778, ODATA-779, ODATA-780, ODATA-782, ODATA-783, ODATA-787, ODATA-788, ODATA-789, ODATA-790, ODATA-791, ODATA-793, ODATA-794, ODATA-795, ODATA-796, ODATA-797, ODATA-801, ODATA-803, ODATA-806, ODATA-807, ODATA-808, ODATA-810, and ODATA-815 as applied.

Hubert Heijkers1: I second

Mike Pizzo: I third

Ralf Handl (SAP): The motion passes, all listed issues are CLOSED

Ralf Handl (SAP): b.Issues for V4.0_ERRATA03 in New or Open state

Ralf Handl (SAP): i.OData CSDL

Ralf Handl (SAP): 1.ODATA-821 14.2.1 Attribute Target: targeting of nested properties of structured types

Ralf Handl (SAP): Add rule

 * QualifiedName of a structured type followed by zero or more property, navigation property, or type cast segments, each segment starting with a forward slash

 Add examples

 MySchema.MyEntityType/MyComplexProperty/MyProperty

 MySchema.MyEntityType/MyComplexProperty/MyNavigationProperty

 MySchema.MyComplexType/MyComplexProperty/MyProperty

 MySchema.MyComplexType/MyComplexProperty/MyNavigationProperty

Ralf Handl (SAP): ODATA-821 is OPEN

Martin Zurmuehl: I move to resolve OData-821 as proposed.

Mark Biamonte (Progress): I second

Ralf Handl (SAP): ODATA-821 is resolved as proposed

Ralf Handl (SAP): 2.ODATA-819 10.2.2: Clarify whether enum types allow multiple members with the same value

Mike Pizzo: Proposal: Allow services to support multiple members with the same value.Require that (where supported) members with the same underlying value compare equal, and caution that the choice of which value the service returns is indeterminant.

Hubert Heijkers1: I move to resolve ODATA-821 as proposed.

Mike Pizzo: I second

Martin Zurmuehl: I second

Ralf Handl (SAP): ODATA-819 is resolved as proposed

Ralf Handl (SAP): ii.OData Protocol

Ralf Handl (SAP): 1.ODATA-822 Async Batch Request: Bug in example 80

Ralf Handl (SAP): ODATA-822 is OPEN

Hubert Heijkers1: I move to resolve ODATA-822 as proposed.

Hubert Heijkers1: I move to resolve ODATA-822 as per the revised proposal.

Mike Pizzo: I second

Ralf Handl (SAP): ODATA-822 is resolved as proposed

Ralf Handl (SAP): 2.ODATA-823 Header Content-Transfer-Encoding not used in HTTP

Mike Pizzo: Revised proposal:

Mike Pizzo: Proposal: In Errata, specify that:

1) Services should not rely on the header being there in batch requests because it is expected to be made optional in 4.1.

2) Client should not rely on the header being there in the async/batch response fosr the same reason.

In 4.1, remove Header Field Content-Transfer-Encoding with value binary

Martin Zurmuehl: I move to resolve ODATA-823 as per the revised proposal.

Hubert Heijkers1: I second

Ralf Handl (SAP): Mike: make sure that we make the header optional in V4.1 and not forbid it

Ralf Handl (SAP): Mike opened cloned issue ODATA-824

Ralf Handl (SAP): ODATA-823 is resolved as proposed

Ralf Handl (SAP): 6.Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php]

Ralf Handl (SAP): a.Action items due

i.Overview presentation on HTTP/2 features

Ralf Handl (SAP): Servers able to push e.g. referenced resources to browsers so that they are already in the browser cache when the client requests them

Ralf Handl (SAP): Could be useful for async requests, pushing the monitor resource directly after the 202 Accepted with an expiration matching the retry-after period

Ralf Handl (SAP): Investigation needed in whether there will be _javascript_ APIs to allow applications access to that mechanism, or whether this is completely handled by the browser

Ralf Handl (SAP): HTTP/2 is non-disruptive, none of the semantics changed, only changes on the transport layer

Ralf Handl (SAP): Martin to give more details in next meeting on header compression, performance

Ralf Handl (SAP): Acceptance is high, supported by Chrome, Microsoft Edge

Ralf Handl (SAP): 7.Next meeting [9:50am PT]

a.Thursday July 09, 2015 during 8-10am PT?

Ralf Handl (SAP): Accepted

Ralf Handl (SAP): 8.AOB and wrap up

Martin Zurmuehl: GET ~/Monitorresource Accept: application/http

Martin Zurmuehl: GET ~/Monitorresource Accept: application/json; q=0.1, application/http

Ralf Handl (SAP): Mike to record outcome of discussion in ODATA-808

Ralf Handl (SAP): Mike to record outcome of discussion in ODATA-809

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Donnerstag, 18. Juni 2015 09:35
To: odata@lists.oasis-open.org
Subject: RE: [odata] Agenda for OData TC meeting on 2015-06-18

Section 5.a.iii.4. Updated link to latest JSON Format revision incorporating Mike’s comments

Section 5.b. Added section ii for issues ODATA-822 and ODATA-823

From: Handl, Ralf
Sent: Donnerstag, 18. Juni 2015 08:40
To: Handl, Ralf; odata@lists.oasis-open.org
Subject: RE: [odata] Agenda for OData TC meeting on 2015-06-18

Now with link to minutes from June 11, and section [4] for leaves of absence

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Dienstag, 16. Juni 2015 15:22
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2015-06-18

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday June 18, 2015 during 8-10am PDT (17:00-19:00 CEST). 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

1. Roll call [8:00am PT]

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

2. Approve agenda [8:05am PT]

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

a. Minutes from June 11, 2015 TC meeting: https://www.oasis-open.org/committees/download.php/55912/odata-meeting-99_on-20150611-minutes.html

4. Review Timeline [8:15am PT]

a. https://www.oasis-open.org/committees/document.php?document_id=55904&wg_abbrev=odata

5. Process issues [Issues list: https://issues.oasis-open.org/issues/?jql=project%20%3D%20ODATA] [8:30am PT]

a. Issues for V4.0_ERRATA03 in Applied state

i. Procedure

1. Review documents up-front for correct issue application

2. No live walk-through of the documents during the TC meeting

3. Discuss application of individual issues where necessary

4. Reject application of individual issues where necessary

5. Summarily move to close undisputed issues

ii. Issues

1. ODATA-479 Allow Content-ID referencing in request bodies for inserting links to newly created entities

2. ODATA-731 Explicitly state that JSON service documents may contain annotations

3. ODATA-732 Add enumeration member "Write" to "Permission" type

4. ODATA-733 Clarify handling of cycles in Extends for EntityContainers

5. ODATA-734 Unicode Facet is inadequate

6. ODATA-740 Let's update the GeoJSON reference (again)

7. ODATA-741 Mismatch between explanatory text and URL in example 96

8. ODATA-742 Usage of domain contoso.com and term name contoso in examples

9. ODATA-745 Sections 4.5.5, 7.3, and 7.4: is odata.nextLink allowed for all collections?

10. ODATA-746 12.2.3: IsComposable - clarify what is allowed even if set to false

11. ODATA-748 Section 4.5.4: odata.count needs to be allowed for all collections

12. ODATA-749 What should service return when attempting to related two entities that are already related?

13. ODATA-750 Explicitly mention the @ sign in instance annotations

14. ODATA-751 Clarification of Edm.NavigationPropertyPath and Edm.PropertyPath

15. ODATA-752 Bug in example 47

16. ODATA-753 Minor typo in references to bound function calls

17. ODATA-754 Clarify that numeric enum values are serialized as strings

18. ODATA-755 Construction rule for canonical URL is incomplete

19. ODATA-756 Clarify when odata.metadataEtag will be returned

20. ODATA-758 Example 81: wrong parameter style

21. ODATA-761 11.5.4.1 Invoking an Action: Location header for 201 Created responses

22. ODATA-762 Section 8.5: clarify that @odata.bind:null is valid for updating of 0..1 navigation properties

23. ODATA-765 Example 77 (invoking an action): show complex parameters

24. ODATA-766 8.2.4 and 8.2.5 should refer to RFC7232 (public comment c201501e00001)

25. ODATA-767 Adapt Acknowledgements

26. ODATA-768 Remove superfluous text after references

27. ODATA-769 5.2 Model Versioning: allow adding a new term to the model

28. ODATA-770 18.2: incomplete description of annotation name format

29. ODATA-771 Exponential notation for Edm.Decimal values in JSON payloads

30. ODATA-773 Qualifiers for instance annotations: JSON Format

31. ODATA-774 Qualifiers for annotations: Preference odata.include-annotations

32. ODATA-775 Should allow use of parameter aliases for key lookup

33. ODATA-776 Clarify function invocation

34. ODATA-777 Clarify multiply/divide duration by number

35. ODATA-778 Example in section 11.7.3.1, "Referencing Requests in a Change Set", should use JSON, not ATOM

36. ODATA-779 Org.OData.Core.V1 defines Term IsURL but references it as IsUrl

37. ODATA-780 indexof: what to return if the second argument does not appear in the first argument

38. ODATA-782 Example 57: choose better example

39. ODATA-783 Is it intentional that mindatetime/maxdatetime/now don't permit %-encoded parentheses in ABNF?

40. ODATA-787 Clarify how odata.Include-annotations preference affects odata.* markup

41. ODATA-788 Clarify precidence rules for odata.include-annotations preference

42. ODATA-789 Primitive type Edm.Decimal is ill-defined in regard to Precision

43. ODATA-790 Bug in example 70

44. ODATA-791 11.2.5.2 System Query Option $orderby: specify order of Edm.Boolean and Edm.Geo

45. ODATA-793 Expand * on complex type

46. ODATA-794 11.4.2.2: Create Related Entities When Creating an Entity

47. ODATA-795 Support annotations for expanded references

48. ODATA-796 Add annotation to specify whether additional properties may be returned for an entity

49. ODATA-797 Org.OData.Capabilities.V1 term property FilterRestrictions/RequiresFilter has wrong facets

50. ODATA-801 Consider supporting negative scale for decimal type

51. ODATA-803 Collection-valued property: Define default value for nullable facet

52. ODATA-806 Wrong description in capabilities vocabulary in term SearchRestrictions

53. ODATA-807 Don't need TargetId in a deleted link for a to 0..1 relationship

54. ODATA-808 ODATA-796 Minor changes to new OnlyDeclaredProperties annotation

55. ODATA-810 Part 3, 14.1.5 uses IsURI instead of IsURL

56. ODATA-815 Clarify that the values of the format parameters odata.metadata etc. are case-insensitive

iii. Documents

1. https://www.oasis-open.org/committees/download.php/55616/odata-v4.0-wd08-part1-protocol-2015-05-07.docx

2. https://www.oasis-open.org/committees/download.php/55614/odata-v4.0-wd08-part2-url-conventions-2015-05-07.docx

3. https://www.oasis-open.org/committees/download.php/55611/odata-v4.0-wd08-part3-csdl-2015-05-07.docx

4. https://www.oasis-open.org/committees/download.php/55921/odata-json-format-v4.0-wd08-2015-06-18.docx

5. https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/vocabularies/Org.OData.Core.V1.xml

6. https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/vocabularies/Org.OData.Capabilities.V1.xml

iv. Summary Motion

1. I move to close ODATA-479, ODATA-731, ODATA-732, ODATA-733, ODATA-734, ODATA-740, ODATA-741, ODATA-742, ODATA-745, ODATA-746, ODATA-748, ODATA-749, ODATA-750, ODATA-751, ODATA-752, ODATA-753, ODATA-754, ODATA-755, ODATA-756, ODATA-758, ODATA-761, ODATA-762, ODATA-765, ODATA-766, ODATA-767, ODATA-768, ODATA-769, ODATA-770, ODATA-771, ODATA-773, ODATA-774, ODATA-775, ODATA-776, ODATA-777, ODATA-778, ODATA-779, ODATA-780, ODATA-782, ODATA-783, ODATA-787, ODATA-788, ODATA-789, ODATA-790, ODATA-791, ODATA-793, ODATA-794, ODATA-795, ODATA-796, ODATA-797, ODATA-801, ODATA-803, ODATA-806, ODATA-807, ODATA-808, ODATA-810, and ODATA-815 as applied.

b. Issues for V4.0_ERRATA03 in New or Open state

i. OData CSDL

1. ODATA-821 14.2.1 Attribute Target: targeting of nested properties of structured types

2. ODATA-819 10.2.2: Clarify whether enum types allow multiple members with the same value

ii. OData Protocol

1. ODATA-822 Async Batch Request: Bug in example 80

2. ODATA-823 Header Content-Transfer-Encoding not used in HTTP

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

a. Action items due

i. Overview presentation on HTTP/2 features

7. Next meeting [9:50am PT]

a. Thursday July 09, 2015 during 8-10am PT?