RE: [odata] Agenda for OData TC meeting on 2017-02-23

Chat Transcript

Room information was updated by: Stefan Hagen

OASIS Open Data Protocol (OData) TC OData TC Weekly Meeting (Conference Call) #163

- Thursday, 23 February 2017, 08:00am to 10:00am PT

  - i.e. 2017-02-23 17:00 to 19:00 CET (UTC+1)

  - other timezone? Try eg.:

  - https://www.timeanddate.com/worldclock/meetingdetails.html?year=2017&month=2&day=23&hour=16&min=0&sec=0&p1=47&p2=69&p3=179

Meeting Member URL:

- URL = "" href="https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43966" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43966

  - Please use starting approx. 15 minutes before the meeting for self registration. Thanks.

  - Self registration deep link (as a service):

    - https://www.oasis-open.org/apps/org/workgroup/odata/record_my_attendance.php?event_id=43966&confirmed=1

Agenda-Draft E-Mail URL:

- E-Mail Public URL = "" href="https://lists.oasis-open.org/archives/odata/201702/msg00072.html" target="_blank">https://lists.oasis-open.org/archives/odata/201702/msg00072.html

Minutes Draft Public URL (previous meeting):

- URL = "" href="https://www.oasis-open.org/committees/download.php/60069/odata-meeting-162_on-20170216-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/60069/odata-meeting-162_on-20170216-minutes.html

Online document walkthroughs or presentations:

- URL = "" href="https://sap.emea.pgiconnect.com/OData-TC/" target="_blank">https://sap.emea.pgiconnect.com/OData-TC/

Timeline:

- URL = "" href="https://www.oasis-open.org/committees/download.php/59862/TC%20Timeline-2017-01-25.docx" target="_blank">https://www.oasis-open.org/committees/download.php/59862/TC%20Timeline-2017-01-25.docx

Agenda Draft (for meeting #163):

- Roll call

- Approve agenda

- Approve minutes from previous meeting(s)

  - Minutes from February 16, 2016 TC meeting #162: https://www.oasis-open.org/committees/download.php/60069/odata-meeting-162_on-20170216-minutes.html

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

  - Action items due

  - None

- CSDL JSON

  - Document Walkthrough

  - OData CSDL JSON Representation Version 4.01 as of 2017-02-15

    - Public URL = "" href="https://www.oasis-open.org/committees/download.php/60048/odata-csdl-json-v4.01-wd01-2017-02-15.docx" target="_blank">https://www.oasis-open.org/committees/download.php/60048/odata-csdl-json-v4.01-wd01-2017-02-15.docx

- V4.01

  - Issues for V4.01_CSD02 ready for resolution

    - ODATA-1028 4.3.4 and 4.4: clarify resolution of relative URLs in system query option $id

  - Issues for V4.01_CSD02 in New or Open state without concrete proposal

    - ODATA-760 Add to depth restrictions to Capabilities Vocabulary

    - ODATA-854 Consider use of OPTIONS for discovering formats, other capabilities and features

    - ODATA-868 Describe HTTP encoding for streamed requests and responses

    - ODATA-879 Support Arrays of Arrays

    - ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)

    - ODATA-919 Specify the result type for each operation based on operator types

    - ODATA-920 Specify overflow for int data types (-INF, INF, NaN)

    - ODATA-923 $expand (or $include) for $metadata to include referenced schemas

    - ODATA-950 Clarify what requests can be delta enabled

    - ODATA-962 CORS Support

    - ODATA-994 consider replacing SchemaVersion header with $SchemaVersion query option, or root URL versioning

    - ODATA-1002 Add build in functions operating on collections of primitive (and complex?) types

    - ODATA-1003 Allow casting of entities and complex type instances to arbitrary structural type

    - ODATA-1005 Make sure we have capabilities for all new 4.01 functionality

    - ODATA-1011 Security experts at RSA suggest adding guidance on the use of OAuth and openID

    - ODATA-1018 Allow $expand and $select with modifying requests that return a collection in combination with return=representation to specify the response shape

    - ODATA-1020 Remove / in reference in instance annotation in filter and orderby _expression_

    - ODATA-1021 Are additional values needed for the reason property of a removed Annotation

    - ODATA-1032 Define comparison for numeric value exceptions

    - ODATA-1033 Interoperability issue when using escaped slash/backslash in URLs

    - ODATA-1034 Support the notion of a collection of name/value pairs where the type of the value is known

    - ODATA-1036 10.7/8: Simplify context URL for "all operations in schema"

    - ODATA-1037 Add tagging term Core.Deprecated to mark deprecated model elements

    - ODATA-1038 Clarify term "simple value"

- Next meeting

  - Thursday March 02, 2017 during 8-10 am PST? (2017-03-02 16:00 to 18:00 UTC) ?

- AOB and wrap up

UsefulPlaces:

- Chat:

  - http://webconf.soaphub.org/conf/room/odatatc   # ... this place

- ScreenShare and Voice:

  - https://sap.emea.pgiconnect.com/OData-TC/

Next Planned meeting (tentative):

- Thursday March 02, 2017 during 8-10 am PST? (2017-03-02 16:00 to 18:00 UTC) ?

  - https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43967

Stefan Hagen: RegState{Voting Members: 2 of 11 (18%) (used for quorum calculation)}

Stefan Hagen: RegState{Voting Members: 3 of 11 (27%) (used for quorum calculation)}

Room Information:

OASIS Open Data Protocol (OData) TC OData TC Weekly Meeting (Conference Call) #163

- Thursday, 23 February 2017, 08:00am to 10:00am PT

  - i.e. 2017-02-23 17:00 to 19:00 CET (UTC+1)

  - other timezone? Try eg.:

  - https://www.timeanddate.com/worldclock/meetingdetails.html?year=2017&month=2&day=23&hour=16&min=0&sec=0&p1=47&p2=69&p3=179

Meeting Member URL:

- URL = "" href="https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43966" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43966

  - Please use starting approx. 15 minutes before the meeting for self registration. Thanks.

  - Self registration deep link (as a service):

    - https://www.oasis-open.org/apps/org/workgroup/odata/record_my_attendance.php?event_id=43966&confirmed=1

Agenda-Draft E-Mail URL:

- E-Mail Public URL = "" href="https://lists.oasis-open.org/archives/odata/201702/msg00072.html" target="_blank">https://lists.oasis-open.org/archives/odata/201702/msg00072.html

Minutes Draft Public URL (previous meeting):

- URL = "" href="https://www.oasis-open.org/committees/download.php/60069/odata-meeting-162_on-20170216-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/60069/odata-meeting-162_on-20170216-minutes.html

Online document walkthroughs or presentations:

- URL = "" href="https://sap.emea.pgiconnect.com/OData-TC/" target="_blank">https://sap.emea.pgiconnect.com/OData-TC/

Timeline:

- URL = "" href="https://www.oasis-open.org/committees/download.php/59862/TC%20Timeline-2017-01-25.docx" target="_blank">https://www.oasis-open.org/committees/download.php/59862/TC%20Timeline-2017-01-25.docx

Agenda Draft (for meeting #163):

- Roll call

- Approve agenda

- Approve minutes from previous meeting(s)

  - Minutes from February 16, 2016 TC meeting #162: https://www.oasis-open.org/committees/download.php/60069/odata-meeting-162_on-20170216-minutes.html

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

  - Action items due

  - None

- CSDL JSON

  - Document Walkthrough

  - OData CSDL JSON Representation Version 4.01 as of 2017-02-15

    - Public URL = "" href="https://www.oasis-open.org/committees/download.php/60048/odata-csdl-json-v4.01-wd01-2017-02-15.docx" target="_blank">https://www.oasis-open.org/committees/download.php/60048/odata-csdl-json-v4.01-wd01-2017-02-15.docx

- V4.01

  - Issues for V4.01_CSD02 ready for resolution

    - ODATA-1028 4.3.4 and 4.4: clarify resolution of relative URLs in system query option $id

  - Issues for V4.01_CSD02 in New or Open state without concrete proposal

    - ODATA-760 Add to depth restrictions to Capabilities Vocabulary

    - ODATA-854 Consider use of OPTIONS for discovering formats, other capabilities and features

    - ODATA-868 Describe HTTP encoding for streamed requests and responses

    - ODATA-879 Support Arrays of Arrays

    - ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)

    - ODATA-919 Specify the result type for each operation based on operator types

    - ODATA-920 Specify overflow for int data types (-INF, INF, NaN)

    - ODATA-923 $expand (or $include) for $metadata to include referenced schemas

    - ODATA-950 Clarify what requests can be delta enabled

    - ODATA-962 CORS Support

    - ODATA-994 consider replacing SchemaVersion header with $SchemaVersion query option, or root URL versioning

    - ODATA-1002 Add build in functions operating on collections of primitive (and complex?) types

    - ODATA-1003 Allow casting of entities and complex type instances to arbitrary structural type

    - ODATA-1005 Make sure we have capabilities for all new 4.01 functionality

    - ODATA-1011 Security experts at RSA suggest adding guidance on the use of OAuth and openID

    - ODATA-1018 Allow $expand and $select with modifying requests that return a collection in combination with return=representation to specify the response shape

    - ODATA-1020 Remove / in reference in instance annotation in filter and orderby _expression_

    - ODATA-1021 Are additional values needed for the reason property of a removed Annotation

    - ODATA-1032 Define comparison for numeric value exceptions

    - ODATA-1033 Interoperability issue when using escaped slash/backslash in URLs

    - ODATA-1034 Support the notion of a collection of name/value pairs where the type of the value is known

    - ODATA-1036 10.7/8: Simplify context URL for "all operations in schema"

    - ODATA-1037 Add tagging term Core.Deprecated to mark deprecated model elements

    - ODATA-1038 Clarify term "simple value"

- Next meeting

  - Thursday March 02, 2017 during 8-10 am PST? (2017-03-02 16:00 to 18:00 UTC) ?

- AOB and wrap up

UsefulPlaces:

- Chat:

  - http://webconf.soaphub.org/conf/room/odatatc   # ... this place

- ScreenShare and Voice:

  - https://sap.emea.pgiconnect.com/OData-TC/

Next Planned meeting (tentative):

- Thursday March 02, 2017 during 8-10 am PST? (2017-03-02 16:00 to 18:00 UTC) ?

  - https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43967

Ralf Handl (SAP SE): Voting Members: 8 of 11 (72%) (used for quorum calculation)

Ralf Handl (SAP SE): Quorum achieved: yes

Ralf Handl (SAP SE): Let's wait for everyone to join the telco

Ralf Handl (SAP SE): 2.Approve agenda [8:05 am PT]

Ralf Handl (SAP SE): Addition to 6.2:

ii. ODATA-1036 10.7/8: Simplify context URL for "all operations in schema"

iii: ODATA-1037 Add tagging term Core.Deprecated to mark deprecated model elements

Ralf Handl (SAP SE): Agenda is approved

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

a.Minutes from February 16, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/60069/odata-meeting-162_on-20170216-minutes.html

Ralf Handl (SAP SE): No remarks, minutes are approved

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

a.Action items due

i.None

Ralf Handl (SAP SE): 5.CSDL JSON  [8:20 am PT]

a.Improved document structure: combine representation-neutral normative text from Part 3: CSDL and representation-specific text into a full specification

i.Walkthrough: https://www.oasis-open.org/committees/download.php/60088/odata-csdl-json-v4.01-wd01-2017-02-21-full.docx

Ralf Handl (SAP SE): Mark is concerned that authors need to be careful when applying changes to keep the documents in sync

Ralf Handl (SAP SE): Mark wondered whether the two vertical bars for the normative representation-specific text would collide with change-tracking.

Ralf Handl (SAP SE): Experiments convinced him that it is not a problem

Ralf Handl (SAP SE)2: Mark likes the combined format

Ralf Handl (SAP SE)2: Side-track: Ralf lost the content of the chat transcript window, Mark will send chat transcript around after the meeting

Ralf Handl (SAP SE)2: ii.Decide whether to use full-specification approach for CSDL JSON

Mark Biamonte (Progress): I move that we proceed with using the combined Part 3 and JSON format for the JSON CSDL

Matt Borges (SAP): i second

Ralf Handl (SAP SE)2: No objection, motion passes

Ralf Handl (SAP SE)2: iii.Decide whether to apply same approach to CSDL XML

Matt Borges (SAP): I move we also use the full-specification approach for CSDL XML

Mark Biamonte (Progress): I second

Ralf Handl (SAP SE)2: No objection, motion passes

Ralf Handl (SAP SE)2: 6.V4.01 [9:20 am PT]

a.Issues for V4.01_CSD02 ready for resolution

i.ODATA-1035 10.13: Simplify context URL for Property Value

Ralf Handl (SAP SE)2: The context URL for a property value contains the keys of the entity.

This seems overly specific as the context URL is a pointer to structural metadata, so why should it vary from entity to structurally identical entity?

Note that the context URL for an entity does not contain the key, nor is it required that the key properties are always present in the response.

Ralf Handl (SAP SE)2: Example: http://host/service/$metadata#Customers(1)/Addresses

Ralf Handl (SAP SE)2: Allow the context URL pattern

    {context-url}#{type-name}{select-list}

also for property values.

If something more specific is desired, the pattern could be

    {context-url}#{entity-set}/{property-path}{select-list}

Ralf Handl (SAP SE)2: Example: http://host/service/$metadata#Customers/Addresses

Ralf Handl (SAP SE)2: Example: http://host/service/$metadata#Customers/Addresses(Street,Zip)

Ralf Handl (SAP SE)2: Example for operation: http://host/service/$metadata#Collection(self.Address)

Ralf Handl (SAP SE)2: Mark tried it out with his implementation: it is already using the key-less pattern

Mark Biamonte (Progress): "@odata.context": "http://localhost:8080/api/odata4/sforce_odata/$metadata#USERS/USERNAME"

Ralf Handl (SAP SE)2: ODATA-1035 is OPEN

Ralf Handl (SAP SE)2: Martin: should the pattern with key still be allowed?

Ralf Handl (SAP SE)2: Ralf: the ISO version of OData V4 allows this, so disallowing it is problematic

Ramesh Reddy (Red Hat): I move ODATA-1035 resolved as proposed

Martin Zurmuehl (SAP SE): I second

Ralf Handl (SAP SE)2: ODATA-1035 is RESOLVED as proposed

Ralf Handl (SAP SE)2: ii. ODATA-1036 10.7/8: Simplify context URL for "all operations in schema"

Ralf Handl (SAP SE)2: Background: $select=self.*

Ralf Handl (SAP SE)2: Context URL: #WorkflowItems(self.Approve,self.Reject,self.Forward)

Ralf Handl (SAP SE)2: Proposal: Context URL: #WorkflowItems(self.*)

Ralf Handl (SAP SE)2: Precedence - structural properties: $select=Name,Date

Ralf Handl (SAP SE)2: Context URL: #WorkflowItems(Name,Date)

Ralf Handl (SAP SE)2: Precedence - structural properties: $select=*

Ralf Handl (SAP SE)2: Context URL: #WorkflowItems(*)

Ralf Handl (SAP SE)2: ODATA-1036 is OPEN

Ralf Handl (SAP SE)2: Matt likes it

Mark Biamonte (Progress): I move that ODATA-1036 be accepted as proposed

Matt Borges (SAP): I second

Ralf Handl (SAP SE)2: ODATA-1036 is RESOLVED as proposed

Ralf Handl (SAP SE)2: iii. ODATA-1037 Add tagging term Core.Deprecated to mark deprecated model elements

Ralf Handl (SAP SE)2: Our model versioning rules only allow adding optional model elements, they don't allow removing model elements.

One way to deal with this is to leave outdated model elements in a service and just mark them as "deprecated".

Ralf Handl (SAP SE)2: Add new Core term

      <Term Name="Deprecated" Type="Core.Tag" DefaultValue="true">

        <Annotation Term="Core.Description" String="Model elements annotated with this term are deprecated and should no longer be used. They may be removed in a future version of the service." />

      </Term>

Ralf Handl (SAP SE)2: Mark: seems to make sense as a general concept

Ralf Handl (SAP SE)2: Ramesh agrees

Ralf Handl (SAP SE)2: ODATA-1037 is OPEN

Ramesh Reddy (Red Hat): I propose to resolve ODATA-1037 as proposed

Martin Zurmuehl (SAP SE): i second

Ralf Handl (SAP SE)2: ODATA-1037 is RESOLVED as proposed

Ralf Handl (SAP SE)2: xx.ODATA-1034 Support the notion of a collection of name/value pairs where the type of the value is known

7.Next meeting [9:50 am PT]

a.Thursday March 02, 2017 during 8-10 am PST  already agreed

Ralf Handl (SAP SE)2: Mark and Hubert will be on vacation next week

Ralf Handl (SAP SE)2: b.Thursday March 09, 2017 during 8-10 am PST

Ralf Handl (SAP SE)2: works for Mark

Ralf Handl (SAP SE)2: No objections, both dates are set

Ralf Handl (SAP SE)2: 8.AOB and wrap up [9:55 am PT]

Ralf Handl (SAP SE)2: Meeting is adjourned

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Thursday, February 23, 2017 3:10 AM
To: odata@lists.oasis-open.org
Subject: RE: [odata] Agenda for OData TC meeting on 2017-02-23

Addition to 6.2:

ii. ODATA-1036 10.7/8: Simplify context URL for "all operations in schema"

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Mittwoch, 22. Februar 2017 09:43
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2017-02-23

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday February 23, 2017 during 8-10 am PST (17:00-19:00 CET). 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:00 am PT]

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

2. Approve agenda [8:05 am PT]

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

a. Minutes from February 16, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/60069/odata-meeting-162_on-20170216-minutes.html

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

a. Action items due

i. None

5. CSDL JSON [8:20 am PT]

a. Improved document structure: combine representation-neutral normative text from Part 3: CSDL and representation-specific text into a full specification

i. Walkthrough: https://www.oasis-open.org/committees/download.php/60088/odata-csdl-json-v4.01-wd01-2017-02-21-full.docx

ii. Decide whether to use full-specification approach for CSDL JSON

iii. Decide whether to apply same approach to CSDL XML

6. V4.01 [9:20 am PT]

a. Issues for V4.01_CSD02 ready for resolution

i. ODATA-1035 10.13: Simplify context URL for Property Value

b. Issues for V4.01_CSD02 in New or Open state without concrete proposal

i. ODATA-760 Add to depth restrictions to Capabilities Vocabulary

ii. ODATA-854 Consider use of OPTIONS for discovering formats, other capabilities and features

iii. ODATA-868 Describe HTTP encoding for streamed requests and responses

iv. ODATA-879 Support Arrays of Arrays

v. ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)

vi. ODATA-919 Specify the result type for each operation based on operator types

vii. ODATA-923 $expand (or $include) for $metadata to include referenced schemas

viii. ODATA-950 Clarify what requests can be delta enabled

ix. ODATA-962 CORS Support

x. ODATA-994 consider replacing SchemaVersion header with $SchemaVersion query option, or root URL versioning

xi. ODATA-1002 Add build in functions operating on collections of primitive (and complex?) types

xii. ODATA-1003 Allow casting of entities and complex type instances to arbitrary structural type

xiii. ODATA-1005 Make sure we have capabilities for all new 4.01 functionality

xiv. ODATA-1011 Security experts at RSA suggest adding guidance on the use of OAuth and openID

xv. ODATA-1018 Allow $expand and $select with modifying requests that return a collection in combination with return=representation to specify the response shape

xvi. ODATA-1020 Remove / in reference in instance annotation in filter and orderby _expression_

xvii. ODATA-1021 Are additional values needed for the reason property of a removed Annotation

xviii. ODATA-1032 Define comparison for numeric value exceptions

xix. ODATA-1033 Interoperability issue when using escaped slash/backslash in URLs

xx. ODATA-1034 Support the notion of a collection of name/value pairs where the type of the value is known

7. Next meeting [9:50 am PT]

a. Thursday March 02, 2017 during 8-10 am PST – already agreed

8. AOB and wrap up [9:55 am PT]

[2] References

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

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

[3] Timeline

· https://www.oasis-open.org/committees/download.php/59862/TC%20Timeline-2017-01-25.docx

odata message