RE: [odata] Agenda for OData TC meeting on 2016-11-10

[12:57] Room information was updated by: Stefan Hagen

Register: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41488  (please do so as usual, thanks).

Agenda draft: https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201611/msg00055.html

Minutes draft of previous meeting: https://www.oasis-open.org/committees/download.php/59288/odata-meeting-151_on-20161103-minutes.html

Room Information:

Register: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41488  (please do so as usual, thanks).

Agenda draft: https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201611/msg00055.html

Minutes draft of previous meeting: https://www.oasis-open.org/committees/download.php/59288/odata-meeting-151_on-20161103-minutes.html

[15:34] Stefan Hagen: Info: Voting Members: 8 of 13 (61%) (used for quorum calculation)

[15:36] Ralf Handl (SAP SE): Voting Members: 9 of 13 (69%) (used for quorum calculation)

[15:36] Ralf Handl (SAP SE): Achieved quorum: yes

[15:37] Ralf Handl (SAP SE): 2.Approve agenda [6:35 am PT]

[15:37] Ralf Handl (SAP SE): ODATA-996 Added/deleted links: "relationship" should be navigation property path

ODATA-997 Define modulo operator for non-integral numeric values

ODATA-998 Specify comparable types for comparison operators

[15:47] Ralf Handl (SAP SE): ODATA-999 introduce aliases for e.g. property names

[15:53] Ralf Handl (SAP SE): Github repositories for Vocabularies and OpenAPI mapping under TC license

[15:53] Ralf Handl (SAP SE): As a replacement/alternative to Subversion

[15:54] Ralf Handl (SAP SE): Not to be confused with the "Open Repos" that we intended earlier, which would have used different licensing and required Individual Contributors License Agreements

[15:55] Mike Pizzo: I move we create two new GitHub repos; one for vocabularies and one for open api alignment, and that we use those repos instead of subversion for ongoing work in those two areas.

[15:55] Hubert Heijkers: I second

[15:56] Ralf Handl (SAP SE): No objections, motion passes

[15:56] Ralf Handl (SAP SE): Example repo: https://github.com/oasis-tcs/water-new-metrics

[15:57] anonymous morphed into Kenneth Baclawski

[15:57] Ralf Handl (SAP SE): Repo name proposals

- odata-vocabularies

- odata-openapi

[15:58] Ralf Handl (SAP SE): existing repos:

dita

OASIS DITA TC: Official repository for the source files for the written DITA specification

Updated 21 hours ago

xliff-omos-jliff

OASIS XLIFF OMOS TC: JSON serialization of the XLIFF Abstract Object Model

 2 Updated 2 days ago

xliff-omos-om

OASIS XLIFF OMOS TC: Object Model for XLIFF Versions 2.0 and higher

[16:01] Ralf Handl (SAP SE): Naming proposals are accepted:

- odata-vocabularies

- odata-openapi

[16:02] Ralf Handl (SAP SE): No further additions to the agenda

[16:02] Ralf Handl (SAP SE): 3.Approve minutes from previous meeting(s) [6:40 am PT]

a.Minutes from November 03, 2016 TC meeting: https://www.oasis-open.org/committees/download.php/59288/odata-meeting-151_on-20161103-minutes.html

[16:05] Ralf Handl (SAP SE): No remarks, minutes are approved

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

a.Action items due

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

[16:06] Ralf Handl (SAP SE): Registration documents checked into Kavi

[16:07] Ralf Handl (SAP SE): 12345678901234567890123456789012345678901234567890123456789012345678901234567890

Open Data (OData) Protocol IANA Header registration request

------------------------------------------------------------

This documentation contains the information needed for Perminanent

Registration of the OData specific request headers with IANA as called out in

RFC 3864 - Registration Procedures for Message Header Fields.  The OData

headers to be registered are

OData-Version

OData-Isolation

OData-MaxVersion

OData-EntityId

The details as required by RFC 3864 for these headers are listed below

####

Header field name:

OData-Version

Applicable protocol:

OASIS Open Data Protocol (OData)

Status:

Standard

Author/Change controller:

OASIS

Specification document(s):

OData Version 4.0 Part 1: Protocol Plus Errata 03 -

   http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752225

Related information:

<none>

####

Header field name:

OData-Isolation

Applicable protocol:

OASIS Open Data Protocol (OData)

Status:

Standard

Author/Change controller:

OASIS

Specification document(s):

OData Version 4.0 Part 1: Protocol Plus Errata 03 -

   http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752232

Related information:

<none>

####

Header field name:

OData-MaxVersion

Applicable protocol:

OASIS Open Data Protocol (OData)

Status:

Standard

Author/Change controller:

OASIS

Specification document(s):

OData Version 4.0 Part 1: Protocol Plus Errata 03 -

   http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752233

Related information:

<none>

####

Header field name:

OData-EntityId

Applicable protocol:

OASIS Open Data Protocol (OData)

Status:

Standard

Author/Change controller:

OASIS

Specification document(s):

http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752238

Related information:

<none>

[16:12] Ralf Handl (SAP SE): OData-Isolation and OData-EntityId: mention upcoming short form Isolation resp. EntityId in "Related information"

[16:13] Ralf Handl (SAP SE): Open Data (OData) Protocol IANA Prefer Header Preference registration request

------------------------------------------------------------------------------

This documentation contains the information needed for Registration of the

OData specific Prefer Header Preferences headers with IANA as called out in

RFC 7240 - Prefer Header for HTTP.  The OData Prefer Header Preferences to be

registered are

allow-entityreferences

callback

continue-on-error

include-annotations

maxpagesize

track-changes

The details as required by RFC 7240 for registering these preferences are listed below

{ Open Questions}

{ 1 - Should the odata. prefix to the preference as defined in the 4.0 spec be included in the registration?}

####

Preference:

allow-entityreferences

Value:

<none>

Optional Parameters:

<none>

Description:

As defined in section 8.2.8.1 of the OData Version 4.0 Part 1: Protocol Plus Errata 03 document referenced below.

Reference:

OData Version 4.0 Part 1: Protocol Plus Errata 03 -

   http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752234

Notes: [optional]

<none>

####

Preference:

callback

Value:

<none>

Optional Parameters:

url - The URL of a callback endpoint to be invoked by the OData service when data is available

Description:

As defined in section 8.2.8.2 of the OData Version 4.0 Part 1: Protocol Plus Errata 03 document referenced below.

Reference:

OData Version 4.0 Part 1: Protocol Plus Errata 03 -

   http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752234

Notes: [optional]

The url parameter specified under optional parameters is required when using the callback preference with OData

####

Preference:

continue-on-error

Value:

<none>

Optional Parameters:

<none>

Description:

As defined in section 8.2.8.3 of the OData Version 4.0 Part 1: Protocol Plus Errata 03 document referenced below.

Reference:

OData Version 4.0 Part 1: Protocol Plus Errata 03 -

   http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752234

Notes: [optional]

<none>

####

Preference:

include-annotations

Value:

comma-separated list of namespaces or namespace qualified term names to include or exclude, with "*" representing all

Optional Parameters:

<none>

Description:

As defined in section 8.2.8.4 of the OData Version 4.0 Part 1: Protocol Plus Errata 03 document referenced below.

Reference:

OData Version 4.0 Part 1: Protocol Plus Errata 03 -

   http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752234

Notes: [optional]

<none>

####

Preference:

maxpagesize

Value:

a positive integer that represents the maximum number of items each collection in a response may contain

Optional Parameters:

<none>

Description:

As defined in section 8.2.8.5 of the OData Version 4.0 Part 1: Protocol Plus Errata 03 document referenced below.

Reference:

OData Version 4.0 Part 1: Protocol Plus Errata 03 -

   http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752234

Notes: [optional]

<none>

####

Preference:

track-changes

Value:

<none>

Optional Parameters:

<none>

Description:

As defined in section 8.2.8.6 of the OData Version 4.0 Part 1: Protocol Plus Errata 03 document referenced below.

Reference:

OData Version 4.0 Part 1: Protocol Plus Errata 03 -

   http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752234

Notes: [optional]

<none>

[16:28] Ralf Handl (SAP SE): 5.JSON Format for CSDL [6:50 am PT]

a.Proposals for an OData-specific, lossless JSON format for Metadata

i.OpenUI5 OData V4 Metadata JSON Format: https://openui5.hana.ondemand.com/#docs/guide/87aac894a40640f89920d7b2a414499b.html

[17:30] Ralf Handl (SAP SE): Walking through https://openui5.hana.ondemand.com/#docs/guide/87aac894a40640f89920d7b2a414499b.html

[17:34] Ralf Handl (SAP SE): Points to consider:

- $kind or $Kind etc. to be consistently UpperCamelCase

- "MaxLength":"max"

- Collections of collections

[17:36] Ralf Handl (SAP SE): Next steps:

- check in examples and XSLT

- start filling CSDL JSON V4.01 document

- open issues for things to discuss/change/extend

[17:36] Ralf Handl (SAP SE): 6.V4.01 [7:50 am PT]

a.Issues for V4.01_WD01 in New or Open state

i.Waiting for refined proposal

[17:36] Ralf Handl (SAP SE): i.Waiting for refined proposal

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

2.ODATA-879 Support Arrays of Arrays

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

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

5.ODATA-965 UpdateGeoJSON Reference to RFC7946

6.ODATA-966 13.4 Add example for navigation property bindings for containment navigation property

7.ODATA-974 Flesh out recommendations around OAuth support in OData

8.ODATA-995 Resolve inconsistencies in JSON streaming property ordering

[17:37] Ralf Handl (SAP SE): 9. ODATA-996 Added/deleted links: "relationship" should be navigation property path

10. ODATA-997 Define modulo operator for non-integral numeric values

11. ODATA-998 Specify comparable types for comparison operatorsODATA-999 introduce aliases for e.g. property names

[17:38] Ralf Handl (SAP SE): ODATA-965

[17:38] Mike Pizzo: I move we resolve ODATA-965 as proposed.

[17:38] Hubert Heijkers: I second

[17:39] Ralf Handl (SAP SE): ODATA-965 is RESOLVED as proposed

[17:39] Ralf Handl (SAP SE): ODATA-996 Added/deleted links: "relationship" should be navigation property path

[17:40] Ralf Handl (SAP SE): {

      "@odata.context":"#Customers/$link",

      "source":"Customers('BOTTM')",

      "relationship":"Orders",

      "target":"Orders(10645)"

},

[17:40] Ralf Handl (SAP SE): {

      "@odata.context":"#Customers/$link",

      "source":"Customers('BOTTM')",

      "relationship":"Some/Thing/Complex/Orders",

      "target":"Orders(10645)"

},

[17:46] Ralf Handl (SAP SE): Alternative: use nested content representation with an entity reference value for the navigation property

[17:47] Ralf Handl (SAP SE): Nested content with entity references is safe way to go for collection-valued complex properties

[17:49] Ralf Handl (SAP SE): ODATA-996 is OPEN

[17:49] Mike Pizzo: I like the syntax for nav properties on individual complex types. we could default to nested collections syntax for collections of complex types.

[17:50] Ralf Handl (SAP SE): Amended proposal: path for single-valued complex properties, nested content with entity references for collection-valued complex properties

[17:54] Hubert Heijkers: I move to resolve ODATA-996 as per the amended proposal

[17:54] Martin Zurmuehl (SAP): I second

[17:55] Ralf Handl (SAP SE): ODATA-996 is resolved with the amended proposal

[17:55] Ralf Handl (SAP SE): ODATA-997 Define modulo operator for non-integral numeric values

[17:56] Ralf Handl (SAP SE): 10 mod 4.8 -> 0.4

[17:58] Ralf Handl (SAP SE): Programming language 10 div 4.8 -> 2

[17:58] Ralf Handl (SAP SE): Programming language 10 / 4.8 -> 2.something

[18:00] Ralf Handl (SAP SE): Martin's extension:

10 div 4 -> 2

10 divby 4 -> 2.5

[18:01] Ralf Handl (SAP SE): ODATA-996 is OPEN

[18:03] Ralf Handl (SAP SE): ODATA-997 is OPEN

[18:05] Ralf Handl (SAP SE): a mod b eq a sub b mul floor(a div b)

[18:06] Mike Pizzo: I move we resolve ODATA-997 as proposed.

[18:06] Hubert Heijkers: I second

[18:07] Ralf Handl (SAP SE): ODATA-997 is resolved as proposed, pending check of definition formula for negative operands

[18:08] Ralf Handl (SAP SE): ODATA-998 Specify comparable types for comparison operators

[18:08] Ralf Handl (SAP SE): Specify which types can be compared with eq, ne, le, lt, ge, gt

a) values of same primitive type can be compared (except Edm.Binary, Edm.Stream, and the Edm.Geo types. Edm.Binary, Edm.Stream, and the Edm.Geo)

b) Int* can be compared to Int*

c) Single to Double

[18:11] Ralf Handl (SAP SE): d) Int* can be compared to Decimal by casting Int* to the same Decimal flavor

[18:12] Matt Borges (SAP): 5.1.1.8.1

[18:12] Matt Borges (SAP): In URL conventions

[18:13] Matt Borges (SAP): 5.1.1.15 in URL conventions

[18:16] Ralf Handl (SAP SE): ODATA-998 is OPEN

[18:17] Ralf Handl (SAP SE): Specify which types can be compared with eq, ne, le, lt, ge, gt

a) values of same primitive type can be compared (except Edm.Binary, Edm.Stream, and the Edm.Geo types)

b) Int* can be compared to Int*

c) Single to Double

d) Int* can be compared to Decimal by casting Int* to the same Decimal flavor

[18:19] Ralf Handl (SAP SE): Amended proposal:

a) values of same primitive type can be compared (except Edm.Binary, Edm.Stream, and the Edm.Geo types)

b) numbers compared with each other using casting rules

[18:23] Hubert Heijkers: I move to resolve ODATA-998 as per the new amended proposal

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

[18:23] Stefan Hagen: I second

[18:23] Ralf Handl (SAP SE): ODATA-998 is resolved with the amended proposal

[18:23] Ralf Handl (SAP SE): ODATA-999 Consider adding support for 'aliases' on Entity sets, Singletons and Properties

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

The idea behind allowing aliases is primarily driven by having shorter names for various entity sets, singletons and properties of complex and entity types. Ideally these aliases could be used in request as well as be returned by the server in response payloads.

[18:25] Ralf Handl (SAP SE): 8.ODATA-995 Resolve inconsistencies in JSON streaming property ordering

[18:25] Ralf Handl (SAP SE): Proposal:

Update 18.2 to state that annotations must come before the property

After making sure existing streaming clients don't rely on this ordering, update 4.4 to remove constraint that navigation annotations must come after structural properties.

[18:29] Mike Pizzo: revised proposal:

Update 18.2 to state that annotations must come before the property

Update 4.4 to say that 4.0 services MUST return nav annotations after structural properties, 4.01 clients MUST NOT assume this ordering.

[18:30] Ralf Handl (SAP SE): ODATA-995 is OPEN

[18:30] Hubert Heijkers: I move to resolve ODATA-995 as per the revised proposal

[18:30] Mike Pizzo: I second.

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

[18:31] Ralf Handl (SAP SE): 6.ODATA-966 13.4 Add example for navigation property bindings for containment navigation property

[18:31] Ralf Handl (SAP SE): Example: Orders contained OrderDetails:

<EntitySet Name="Orders" Type="Sales.Order">

   <NavigationPropertyBinding Path="OrderDetails/Product" Target="Products"/>

</EntitySet>

[18:36] Mike Pizzo: I move we resolve ODATA-966 as proposed.

[18:36] Hubert Heijkers: I second

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

[18:37] Ralf Handl (SAP SE): 7.ODATA-974 Flesh out recommendations around OAuth support in OData

[18:39] Ralf Handl (SAP SE): Example of usage:

<Annotation Term="Auth.AuthorizationOptions">

  <Collection>

    <Record Type="Auth.Http"/>

    <Record Type="Auth.OpenIDConnect">

      <PropertyValue Name="IssuerUrl" String="https://example.com/issuer1"/>

    </Record>

    <Record Type="Auth.OAuth2AuthCode">

      <PropertyValue Name="AuthorizationUrl" String="http://myauth/authorize"/>

      <PropertyValue Name="TokenUrl" String="http://myauth/token"/>

      <PropertyValue Name="Scopes">

        <Record>

          <PropertyValue Name="writeets" String="modify pets"/>

        </Record>

      </PropertyValue>

    </Record>

  </Collection>

</Annotation>

[18:47] Mike Pizzo: Definition of OpenIDConnect:

[18:48] Mike Pizzo: <ComplexType Name="OpenIDConnect" BaseType="Auth.Authorization">

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

<Annotation Term="Core.Description" String="Issuer location for the OpenID Provider. Configuration information can be obtained by appending /.well-known/openid-configuration to this Url."/>

</Property>

</ComplexType>

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

a.Thursday November 17, 2016 during 8-10 am PST?

[18:52] Ralf Handl (SAP SE): a. is accepted.

No meeting on November 24, 2016

[18:53] Ralf Handl (SAP SE): Decide next week whether to make December 1 a long meeting

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

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Freitag, 4. November 2016 13:52
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2016-11-10

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday November 10, 2016 during 6:30-10:00 am PST (15:30-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 [6:30 am PT]

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

2. Approve agenda [6:35 am PT]

3. Approve minutes from previous meeting(s) [6:40 am PT]

a. Minutes from November 03, 2016 TC meeting: https://www.oasis-open.org/committees/download.php/59288/odata-meeting-151_on-20161103-minutes.html

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

a. Action items due

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

5. JSON Format for CSDL [6:50 am PT]

a. Proposals for an OData-specific, lossless JSON format for Metadata