RE: [odata] Agenda for OData TC meeting on 2017-01-26

[10:29] Room information was updated by: Stefan Hagen

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

- Thursday, 26 January 2017, 08:00am to 10:00am PT

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

  - other timezone? Try eg.:

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

Meeting Member URL:

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

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

    - Self registration link (as a service):

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

Agenda-Draft E-Mail URL:

- E-Mail Public URL = "">https://lists.oasis-open.org/archives/odata/201701/msg00100.html

Minutes Draft Public URL (previous meeting):

- URL = "">https://www.oasis-open.org/committees/download.php/59840/odata-meeting-158_on-20170119-minutes.html

Online document walkthroughs or presentations:

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

Timeline:

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

New Contribution fromSAP SE (submitted by Ralf):

- Title: Streamlined Metadata JSON

  - URL = "">https://www.oasis-open.org/committees/download.php/59875/Streamlined%20Metadata%20JSON.docx

  - Abstract:

    - This document describes a streamlined JSON format for OData V4 metadata intended to simplify client-side processing. |

      It is different from the $metadata service's JSON format (see OData JSON Format Version 4.0) |

      and the OData JSON Format for Common Schema Definition Language (CSDL) Version 4.0 (see corresponding specification).

Agenda Draft (for meeting #159):

- Roll call

- Approve agenda

- Approve minutes from previous meeting(s)

  - Minutes from January 19, 2016 TC meeting #158: https://www.oasis-open.org/committees/download.php/59840/odata-meeting-158_on-20170119-minutes.html

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

  - Action items due

    - #0036 Register the OData- headers and preferences with IANA

      - IANA Prefer Header Preference Registration Request uploaded to kavi:

        - https://www.oasis-open.org/committees/download.php/59874/IANA_Preference_Registration.docx

- Approve Timeline

  - New version (e.g. now including "Securing OData Version 4.0"):

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

- V4.01

  - Issues for V4.01_CSD02 ready for resolution

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

    - ODATA-1013 Selected nav props in a defining query should specify interest in added/deleted links

    - ODATA-1019 Add term Core.DynamicDefaultValue

    - ODATA-1027 Support instance annotations in $orderby

    - ODATA-1028 4.3.4: clarify relative URLs when a type-cast segment is present

    - ODATA-1029 5.1.1.10.2: clarify that all() is always true if applied to an empty collection

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

    - ODATA-674 Specify navigation property binding combined with containment

    - 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-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-1019 Add term Core.OptionallyComputed or Core.ComputedDefault

    - 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

- Next meeting

  - Thursday February 02, 2017 during 8-10 am PST? (2017-02-02 17:00 to 19:00 UTC) ?

- AOB and wrap up

Further item suggested after "Timeline approval section" and before "Issue processing" (Stefan suggested):

- E-Mail Public URL = "">https://lists.oasis-open.org/archives/odata/201701/msg00107.html

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

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

Next Planned meeting (tentative):

- Thursday February 02, 2017 during 8-10 am PST? (2017-02-02 17:00 to 19:00 UTC) ?

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

[16:45] Stefan Hagen: PartInfo[Voting Members: 1 of 11 (9%) (used for quorum calculation)]

[16:55] Stefan Hagen: PartInfo[Voting Members: 2 of 11 (18%) (used for quorum calculation)]

[16:57] anonymous morphed into Matt Borges (SAP)

[16:58] Stefan Hagen: PartInfo[Voting Members: 3 of 11 (27%) (used for quorum calculation)]

Room Information:

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

- Thursday, 26 January 2017, 08:00am to 10:00am PT

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

  - other timezone? Try eg.:

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

Meeting Member URL:

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

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

    - Self registration link (as a service):

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

Agenda-Draft E-Mail URL:

- E-Mail Public URL = "">https://lists.oasis-open.org/archives/odata/201701/msg00100.html

Minutes Draft Public URL (previous meeting):

- URL = "">https://www.oasis-open.org/committees/download.php/59840/odata-meeting-158_on-20170119-minutes.html

Online document walkthroughs or presentations:

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

Timeline:

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

New Contribution fromSAP SE (submitted by Ralf):

- Title: Streamlined Metadata JSON

  - URL = "">https://www.oasis-open.org/committees/download.php/59875/Streamlined%20Metadata%20JSON.docx

  - Abstract:

    - This document describes a streamlined JSON format for OData V4 metadata intended to simplify client-side processing. |

      It is different from the $metadata service's JSON format (see OData JSON Format Version 4.0) |

      and the OData JSON Format for Common Schema Definition Language (CSDL) Version 4.0 (see corresponding specification).

Agenda Draft (for meeting #159):

- Roll call

- Approve agenda

- Approve minutes from previous meeting(s)

  - Minutes from January 19, 2016 TC meeting #158: https://www.oasis-open.org/committees/download.php/59840/odata-meeting-158_on-20170119-minutes.html

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

  - Action items due

    - #0036 Register the OData- headers and preferences with IANA

      - IANA Prefer Header Preference Registration Request uploaded to kavi:

        - https://www.oasis-open.org/committees/download.php/59874/IANA_Preference_Registration.docx

- Approve Timeline

  - New version (e.g. now including "Securing OData Version 4.0"):

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

- V4.01

  - Issues for V4.01_CSD02 ready for resolution

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

    - ODATA-1013 Selected nav props in a defining query should specify interest in added/deleted links

    - ODATA-1019 Add term Core.DynamicDefaultValue

    - ODATA-1027 Support instance annotations in $orderby

    - ODATA-1028 4.3.4: clarify relative URLs when a type-cast segment is present

    - ODATA-1029 5.1.1.10.2: clarify that all() is always true if applied to an empty collection

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

    - ODATA-674 Specify navigation property binding combined with containment

    - 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-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-1019 Add term Core.OptionallyComputed or Core.ComputedDefault

    - 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

- Next meeting

  - Thursday February 02, 2017 during 8-10 am PST? (2017-02-02 17:00 to 19:00 UTC) ?

- AOB and wrap up

Further item suggested after "Timeline approval section" and before "Issue processing" (Stefan suggested):

- E-Mail Public URL = "">https://lists.oasis-open.org/archives/odata/201701/msg00107.html

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

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

Next Planned meeting (tentative):

- Thursday February 02, 2017 during 8-10 am PST? (2017-02-02 17:00 to 19:00 UTC) ?

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

[17:03] anonymous morphed into Martin Zurmuehl (SAP SE)

[17:04] Ralf Handl (SAP SE): Voting Members: 9 of 11 (81%) (used for quorum calculation)

[17:04] Ralf Handl (SAP SE): Achieved quorum: yes

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

[17:06] Ralf Handl (SAP SE): Stefan Hagen: , I hereby suggest to add a short presentation / discussion of the contribution after "approval of timeline" and before "issue processing".

Context:

New Contribution fromSAP SE (submitted by Ralf):

- Title: Streamlined Metadata JSON

  - URL = "">https://www.oasis-open.org/committees/download.php/59875/Streamlined%20Metadata%20JSON.docx

  - Abstract:

    - This document describes a streamlined JSON format for OData V4 metadata intended to simplify client-side processing. |

      It is different from the $metadata service's JSON format (see OData JSON Format Version 4.0) |

      and the OData JSON Format for Common Schema Definition Language (CSDL) Version 4.0 (see corresponding specification).

[17:07] Ralf Handl (SAP SE): New issues:

[17:07] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1030

[17:08] Ralf Handl (SAP SE): Discuss this right after ODATA-674

[17:09] Ralf Handl (SAP SE): Move ODATA-674 to "ready for resolution" as new agenda  item 6.a.vii

[17:09] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1031

[17:10] Ralf Handl (SAP SE): Discuss this right before ODATA-674

[17:10] Ralf Handl (SAP SE): The agenda is approved with these modifications

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

a.Minutes from January 18, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/59840/odata-meeting-158_on-20170119-minutes.html

[17:10] Ralf Handl (SAP SE): Minutes are approved

[17:11] 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.#0036 Register the OData- headers and preferences with IANA

[17:11] Ralf Handl (SAP SE): https://www.oasis-open.org/apps/org/workgroup/odata/download.php/59874/latest/IANA_Preference_Registration.docx

[17:11] Ralf Handl (SAP SE): https://www.oasis-open.org/apps/org/workgroup/odata/download.php/59873/latest/IANA_Header_Registration.docx

[17:12] Ralf Handl (SAP SE): Mark will walk us through the documents

[17:23] Ralf Handl (SAP SE): Example 2: using a HTTP callback endpoint to receive notification

Prefer: callback; url="">http://myserver/notfication/token/12345"

[17:32] Ralf Handl (SAP SE): Thanks to Mark!

[17:33] Ralf Handl (SAP SE): Documents will be submitted to IANA once V4.01 CS01 is published

[17:33] Ralf Handl (SAP SE): 5.Approve Timeline

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

[17:37] Ralf Handl (SAP SE): 5.1 CSDL JSON Representation V4.01

[17:39] Mike Pizzo: I move we accept the contribution "Streamlined Metadata in JSON" from SAP made by Ralf Handl.

[17:39] Mark Biamonte (Progress): I second

[17:39] Ralf Handl (SAP SE): No objections, motion passes.

[17:42] Ralf Handl (SAP SE): Mike: push for earlier public review of CSDL JSON Representation?

[17:42] Ralf Handl (SAP SE): Mike: take next week's meeting to walk through the document and see when we want to publish CSD01

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

a.Issues for V4.01_CSD02 ready for resolution

[17:43] Ralf Handl (SAP SE): i.ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)

[17:44] Ralf Handl (SAP SE): <Annotation Term="Core.ErrorCodes">

  <Collection>

    <Record>

      <PropertyValue Property="HttpMethod" String="GET" />

      <PropertyValue Property="HttpStatusCode" String="400" />

      <PropertyValue Property="ODataErrorCode" String="QueryFilterFunctionNotSupported" />

      <PropertyValue Property="Description"

        String="This error indicates that a request was made with a filter function that isnt supported on this entity set. Please refer to the Capabilities.FilterFunctions annotation on this entity set for a list of supported functions, and the exact error message for which function usage triggered this error." />

    </Record>

  </Collection>

</Annotation>

[17:44] Ralf Handl (SAP SE): Definition

<Term Name="ErrorCodes" Type="Collection(Core.ErrorCodeType)" AppliesTo="EntitySet Singleton ActionImport FunctionImport Action Function">

  <Annotation Term="Core.Description" String="Describes possible error codes in OData responses" />

  <Annotation Term="Core.LongDescription" String="The list need not be complete. It may be used to generate API documentation, so restricting it to the most common and most important errors may increase readability." /></Term>

<ComplexType Name="ErrorCodeType">

  <Property Name="HttpMethod" Type="Edm.String">

    <Annotation Term="Core.Description" String="Request verb of the HTTP request, e.g. GET, POST, PATCH, DELETE" />

  </Property>

  <Property Name="HttpStatusCode" Type="Edm.String">

    <Annotation Term="Core.Description" String="HTTP status code of the response, e.g. 400, 403, 501" />

  </Property>

  <Property Name="ODataErrorCode" Type="Edm.String">

    <Annotation Term="Core.Description" String="Language-independent, machine-readable OData error code" />

  </Property>

  <Property Name="Description" Type="Edm.String">

    <Annotation Term="Core.Description" String="Human-readable description of the error situation" />

  </Property>

</ComplexType>

[17:49] Ralf Handl (SAP SE): Mike: would it make sense to pre-group the error codes by HTTP method and then HTTP status code

[17:50] Ralf Handl (SAP SE): Ralf to prepare examples for XML and JSON showing more than one error code

[17:50] Ralf Handl (SAP SE): ii.ODATA-1013 Selected nav props in a defining query should specify interest in added/deleted links

[17:50] Ralf Handl (SAP SE): Proposal:

Nav properties specified in the select list of a defining query are not used to define the scope or contents of the items being tracked. Clients can specify /$ref in $expand in order to specify interest in the set of related entities without interest in changes to the content of those related entities.

Delta responses contain AddedLinks and DeletedLinks entries (or, for nested collections, (at least) entity references representing the current membership) for navigation properties expanded with $ref in the defining request.

[17:56] Mike Pizzo: I move we approve ODATA-1013 as proposed to define semantics around /$ref in the expand of a defining query.

[17:57] Ralf Handl (SAP SE): Hubert seconds via phone

[17:57] Ralf Handl (SAP SE): ODATA-1013 is resolved as proposed

[17:57] Ralf Handl (SAP SE): iii.ODATA-1019 Add term Core.DynamicDefaultValue

[17:58] Ralf Handl (SAP SE): Term definition

<Term Name="DynamicDefaultValue" Type="Core.Tag" DefaultValue="true" AppliesTo="Property">

  <Annotation Term="Core.Description" String="A value for this property is can be provided on insert and update. If no value is provided on insert, a non-static default value is generated" />

</Term>

[18:05] Ralf Handl (SAP SE): Mike: ComputedDefaultValue would be more in line with Core.Computed for read-only properties with computed values

[18:05] Ralf Handl (SAP SE): Mike: Clarify how this combines with preference omit-defaults

[18:06] Ralf Handl (SAP SE): Computed default values cannot be omitted because the client can't know it

[18:07] Ralf Handl (SAP SE): Mark: ComputedDefaultValue works

[18:07] Ralf Handl (SAP SE): Hubert: +1

[18:07] Ralf Handl (SAP SE): Matt: +1

[18:09] Ralf Handl (SAP SE): Mike: -1

[18:10] Ralf Handl (SAP SE): ComputedDefaultValue is accepted

[18:10] Ralf Handl (SAP SE): ODATA-1019 is OPEN

[18:11] Ralf Handl (SAP SE): I move to resolve ODATA-1019 with the updated proposal

[18:11] Matt Borges (SAP): I second

[18:11] Ralf Handl (SAP SE): ODATA-1019 is RESOLVED

[18:11] Ralf Handl (SAP SE): iv.ODATA-1027 Support instance annotations in $orderby

[18:13] Mike Pizzo: I move we resolve ODATA-1027 as proposed.

[18:14] Ramesh Reddy (Red Hat): I second

[18:14] Ralf Handl (SAP SE) asked for a victim, I choose... Mark Biamonte (Progress)

[18:14] Ralf Handl (SAP SE): ODATA-1027 is RESOLVED as proposed

[18:14] Ralf Handl (SAP SE): v.ODATA-1028 4.3.4: clarify relative URLs when a type-cast segment is present

[18:15] Ralf Handl (SAP SE): Description:

4.3.4 Resolving an Entity-Id states that

The entity-id may be expressed as an absolute IRI or relative to the service root URL.

Example 23: request the entity representation for an entity-id

http://host/service/$entity?$id=Products(0)

This was correct until we introduced type-cast segments after $entity with ODATA-528.

Now relative URLs should rather be relative to the request URL, as in all other places.

[18:16] Ralf Handl (SAP SE): Relative URLs passed with query option $id are relative to the request, as explicitly stated for other uses of $id.

Add example for a relative URL with and without type-cast segments, showing the need for ../ to dive down beyond the type-cast segment.

[18:17] Ralf Handl (SAP SE): Mike: we also have $root as a symbolic segment

[18:20] Ralf Handl (SAP SE): So URLs relative to the service root can be expressed by prepending $root/

[18:25] Ralf Handl (SAP SE): According to JSON Format the entity id is relative to the context URL, which is (typically) the metadata URL, i.e. relative to the service root

[18:25] Ralf Handl (SAP SE): Mike: $id should also be relative to the service root, so clients can just take the id provided in the JSON response

[18:30] Ralf Handl (SAP SE): GET $entity/self.Car?$id=People(42)

[18:33] Ralf Handl (SAP SE): Alternative proposal: stick to the current text: $id is always relative to service root, even if there's a type-cast segment appended to $entity

[18:33] Ralf Handl (SAP SE): ODATA-1028 is OPEN

[18:36] Mike Pizzo: I move we resolve ODATA-1028 as per the alternate proposal; that the $id is always relative to the service root.

[18:36] Martin Zurmuehl (SAP SE): i second

[18:37] Ralf Handl (SAP SE): ODATA-1028 is RESOLVED with the alternative proposal

[18:37] Ralf Handl (SAP SE): vi.ODATA-1029 5.1.1.10.2: clarify that all() is always true if applied to an empty collection

[18:37] Ralf Handl (SAP SE): ODATA-1029 is OPEN

[18:41] Ralf Handl (SAP SE): Mike: clarify that for all() and any()

[18:41] Ralf Handl (SAP SE): any(expr) is false on the empty set

[18:41] Mike Pizzo: Proposal: all() applied to an empty collection always returns true.

any() applied to an empty collection always returns false.

[18:42] Hubert Heijkers (IBM): I move to resolve ODATA-1029 as per the amended proposal

[18:42] Stefan Hagen: I second

[18:42] Ralf Handl (SAP SE): ODATA-1029 is RESOLVED with the extended proposal

[18:43] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1031

[18:43] Ralf Handl (SAP SE): Define term for links to related information

[18:43] Ralf Handl (SAP SE): Example:

      <Annotation Term="Core.Link">

        <Record>

          <PropertyValue Property="rel" String="latest-version" />

          <PropertyValue Property="href"

            String="https://oasis-tcs.github.io/odata-vocabularies/vocabularies/Org.OData.Core.V1.xml" />

        </Record>

      </Annotation>

[18:44] Ralf Handl (SAP SE): Define new Core term:

      <Term Name="Link" Type="Core.LinkType">

        <Annotation Term="Core.Description" String="Link to related information" />

        <Annotation Term="Core.LongDescription"

          String="The Link term is inspired by the `atom:Link` element, see [RFC4287](https://tools.ietf.org/html/rfc4287#section-4.2.7) and the `Link` HTTP header, see [RFC5988](https://tools.ietf.org/html/rfc5988)" />

      </Term>

      <ComplexType Name="LinkType">

        <Property Name="rel" Type="Edm.String" Nullable="false">

          <Annotation Term="Core.Description"

            String="Link relation type, see [IANA Link Relations](http://www.iana.org/assignments/link-relations/link-relations.xhtml)" />

        </Property>

        <Property Name="href" Type="Edm.String" Nullable="false">

          <Annotation Term="Core.IsURL" />

          <Annotation Term="Core.Description" String="URL of related information" />

        </Property>

      </ComplexType>

[18:45] Ralf Handl (SAP SE): Mike: only for metadata annotations or also for instance annotations?

[18:45] Ralf Handl (SAP SE): In the Atom format we could have used this out-of-the-box

[18:47] Ralf Handl (SAP SE): Atom format used atom:link for @odata.editLink, @odata.id, ...

[18:48] Ralf Handl (SAP SE): Mike: would need to define what happens if both the @odata link and the @Core.Link are present

[18:48] Ralf Handl (SAP SE): Mike: would also need to consider this when reviving the Atom format

[18:49] Ralf Handl (SAP SE): Mike: explicitly state that this annotation is (a) useful as an instance annotation (b) @odata annotations take precedence

[18:50] Ralf Handl (SAP SE): Mike: make this a collection?

[18:51] Ralf Handl (SAP SE): Mike: or use the qualifier for the rel and make it just a string?

[18:52] Ralf Handl (SAP SE): Mike: want to have multiple links, dummy qualifiers seem awkward

[18:53] Ralf Handl (SAP SE): ODATA-1031 is OPEN

[18:53] Stefan Hagen: I move to resolve ODATA-1031 as proposed making this a collection.

[18:54] Martin Zurmuehl (SAP SE): i second

[18:54] Ralf Handl (SAP SE): ODATA-1031 is RESOLVED with the amendment

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

a.Thursday February 02, 2017 during 8-10 am PST?

[18:57] Ralf Handl (SAP SE): Topic next week: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/59388/odata-csdl-json-v4.01-wd01-2016-11-16.docx

[18:59] Stefan Hagen: All with spare cycles please take a look at that URL/document

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

[18:59] Ralf Handl (SAP SE): Mark: example quotes for ISO publication?

[18:59] Ralf Handl (SAP SE): Mike will put together sample quotes

[19:00] Ralf Handl (SAP SE): Meeting is adjourned

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Mittwoch, 25. Januar 2017 15:57
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2017-01-26

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday January 26, 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=43962

2. Approve agenda [8:05 am PT]

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

a. Minutes from January 18, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/59840/odata-meeting-158_on-20170119-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. #0036 Register the OData- headers and preferences with IANA

5. Approve Timeline

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

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

a. Issues for V4.01_CSD02 ready for resolution

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

ii. ODATA-1013 Selected nav props in a defining query should specify interest in added/deleted links

iii. ODATA-1019 Add term Core.DynamicDefaultValue

iv. ODATA-1027 Support instance annotations in $orderby

v. ODATA-1028 4.3.4: clarify relative URLs when a type-cast segment is present

vi. ODATA-1029 5.1.1.10.2: clarify that all() is always true if applied to an empty collection

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

i. ODATA-674 Specify navigation property binding combined with containment

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

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

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

v. ODATA-879 Support Arrays of Arrays

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

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

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

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

x. ODATA-962 CORS Support

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

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

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

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

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

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

xvii. ODATA-1019 Add term Core.OptionallyComputed or Core.ComputedDefault

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

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

7. Next meeting [9:50 am PT]

a. Thursday February 02, 2017 during 8-10 am PST?

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