RE: [odata] Agenda for OData TC meeting on 2016-09-29 - chat transkript

["Handl, Ralf" <ralf.handl@sap.com>]

Room information was updated by: Stefan Hagen

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

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

Minutes draft of previous meeting: https://www.oasis-open.org/committees/download.php/58990/odata-meeting-145_on-20160922-minutes.html

 

Stefan Hagen: ParticipationInfo -- Voting Members: 1 of 12 (8%) (used for quorum calculation)

 

Room Information:

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

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

Minutes draft of previous meeting: https://www.oasis-open.org/committees/download.php/58990/odata-meeting-145_on-20160922-minutes.html

 

Stefan Hagen: ParticipationUpdate -- Voting Members: 1 of 12 (8%) (used for quorum calculation)  (2 registered, but on formally still on leave of absence  )

Stefan Hagen: ParticipationUpdate -- Voting Members: 3 of 12 (25%) (used for quorum calculation)

 

KenBaclawski: I am still showing up as being on Leave of Absence.  That should have ended long ago.

 

Ralf Handl (SAP): Sorry, will change that

 

anonymous morphed into Matt Borges (SAP)

 

Ralf Handl (SAP): Success - Ken Baclawski group role has been changed to Voting Member

Ralf Handl (SAP): Voting Members: 8 of 13 (61%) (used for quorum calculation)

Ralf Handl (SAP): Achieved quorum:yes

Ralf Handl (SAP): 1.Roll call [8:00 am PT]

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

2.Approve agenda [8:05 am PT]

Ralf Handl (SAP): Mike: look at ABNF and Core, Capabilities vocabulary after document-walkthrough

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

a.Minutes from September 22, 2016 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/58990/latest/odata-meeting-145_on-20160922-minutes.html

Ralf Handl (SAP): Minutes are approved

Ralf Handl (SAP): 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

 

Mark Biamonte (Progress): I am dialing in right now.

Mark Biamonte (Progress): I followed up on my email with Robin and did get a response this morning on the header registration.  He will be getting back in the next day or so with more information on how to proceed

 

Ralf Handl (SAP): Ok, thanks!

Ralf Handl (SAP): 5.V4.01 [9:20 am PT]

a.Document Walk-through

i.OData JSON Format Version 4.01  resuming with Chapter 14 Delta Response

 

Stefan Hagen: @Addition to 4.1 Action-Item #0036 - Stefan send a mail to Mark and Robin, that contains a sample filled in markdown template from the GeoJSON RFC (which will need some OData specific content replacing the GeoJSON related one)

 

Mike Pizzo: Sample Motion:

I move we accept the reviewed changes in OData 4.01 Part I: Protocol, OData 4.01 Part 2: Url Conventions and associated ABNF construction rules, OData Common Schema Definition Language XML Representation, OData 4.01 JSON format, and the OData Core and OData Capabilities vocabularies and close the following corresponding issues as applied: ODATA-961,ODATA-958,ODATA-957,ODATA-956,ODATA-953,ODATA-952,ODATA-949,ODATA-948,ODATA-942,ODATA-941,ODATA-940,ODATA-938,ODATA-937,ODATA-928,ODATA-927,ODATA-926,ODATA-925,ODATA-924,ODATA-922,ODATA-921,ODATA-920,ODATA-918,ODATA-901,ODATA-897,ODATA-895,ODATA-894,ODATA-888,ODATA-883,ODATA-881,ODATA-873,ODATA-859,ODATA-856,ODATA-846,ODATA-834,ODATA-824,ODATA-820,ODATA-818,ODATA-816,ODATA-814,ODATA-813,ODATA-812,ODATA-809,ODATA-799,ODATA-696,ODATA-666,ODATA-664,ODATA-631,ODATA-630,ODATA-617,ODATA-616,ODATA-615,ODATA-572,ODATA-563,ODATA-561,ODATA-560,ODATA-556,ODATA-541,ODATA-516,ODATA-482,ODATA-480

 

Hubert Heijkers (IBM): I move we accept the reviewed changes in OData 4.01 Part I: Protocol, OData 4.01 Part 2: Url Conventions and associated ABNF construction rules, OData Common Schema Definition Language XML Representation, OData 4.01 JSON format, and the OData Core and OData Capabilities vocabularies and close the following corresponding issues as applied: ODATA-961,ODATA-958,ODATA-957,ODATA-956,ODATA-953,ODATA-952,ODATA-949,ODATA-948,ODATA-942,ODATA-941,ODATA-940,ODATA-938,ODATA-937,ODATA-928,ODATA-927,ODATA-926,ODATA-925,ODATA-924,ODATA-922,ODATA-921,ODATA-920,ODATA-918,ODATA-901,ODATA-897,ODATA-895,ODATA-894,ODATA-888,ODATA-883,ODATA-881,ODATA-873,ODATA-859,ODATA-856,ODATA-846,ODATA-834,ODATA-824,ODATA-820,ODATA-818,ODATA-816,ODATA-814,ODATA-813,ODATA-812,ODATA-809,ODATA-799,ODATA-696,ODATA-666,ODATA-664,ODATA-631,ODATA-630,ODATA-617,ODATA-616,ODATA-615,ODATA-572,ODATA-563,ODATA-561,ODATA-560,ODATA-556,ODATA-541,ODATA-516,ODATA-482,ODATA-480

 

Stefan Hagen: I second

 

Ralf Handl (SAP): No objections, motion passes

Ralf Handl (SAP): Mike to check in the walk-through documents into Kavi

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

i.OData Protocol

1.ODATA-965 UpdateGeoJSON Reference to RFC7946

 

Stefan Hagen: @Chair: Sorry, Stefan is boarding now - will drop off ...

 

Ralf Handl (SAP): Thanks, we'll create an action item for you 

 

Stefan Hagen: Great, thanks 

 

Ralf Handl (SAP): ODATA-965 is OPEN

Ralf Handl (SAP): We need to check whether the changes between the RFC and the preceding draft affect us

Ralf Handl (SAP): 2.ODATA-970 11.5.2: also mention advertising operations on collections

Ralf Handl (SAP): ODATA-970 is OPEN

Ralf Handl (SAP): Example 33: full representation in a collection

{

  "@odata.context": "http://host/service/$metadata#Employees",

  "#Model.RemainingVacation": {

    "title": "Remaining Vacation",

    "target": "Managers(22)/Employees/RemainingVacation"

  },

  "value": [ ... ]

}

Ralf Handl (SAP): Part 1: Protocol

11.5.2 Advertising Available Operations within a Payload

Services MAY return the available actions and/or functions bound to a particular entity as part of the entity representation within the payload.

Ralf Handl (SAP): Extension for collection-valued nav props:

  "NavProp#Model.RemainingVacation": {

    "title": "Remaining Vacation",

    "target": "Managers(22)/Employees/RemainingVacation"

  },

  "NavProp": [ ... ]

Ralf Handl (SAP): Hubert to create new issue for extending the advertisement syntax for collection-valued navigation properties

Ralf Handl (SAP): Ralf to create new issue for representing annotations on properties in single-property requests. Necessary now for the NumericValueException annotation

 

Hubert Heijkers (IBM): I move to resolve ODATA-970 as proposed

 

Mike Pizzo: I second

 

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

Ralf Handl (SAP): ii.Enumerations

1.ODATA-494 Define inheritance for enumeration types

 

Mike Pizzo: I move we close ODATA-494 with no action.

 

Hubert Heijkers (IBM): I second

 

Martin Zurmuehl (SAP): I second

 

Ralf Handl (SAP): ODATA-494 is CLOSED without action

Ralf Handl (SAP): 2.ODATA-849 Add possibility for enumeration types to "extend" another enumeration type

Ralf Handl (SAP): ODATA-849 is OPEN

 

Mike Pizzo: I move we close ODATA-849 with no action.

 

Martin Zurmuehl (SAP): I second

 

Ralf Handl (SAP): ODATA-849 is CLOSED without action

Ralf Handl (SAP): 3.ODATA-874 Allow Edm.String as underlying type for enumeration types

Ralf Handl (SAP): ODATA-874 is OPEN

Ralf Handl (SAP): I move to close ODATA-874 without action as this is covered by the AllowedValues annotation

 

Hubert Heijkers (IBM): I second

 

Ralf Handl (SAP): ODATA-874 is CLOSED without action

Ralf Handl (SAP): iii.Annotations

1.ODATA-817 Add client-side function odata.matchesRegularExpression

Ralf Handl (SAP): Add a client-side function odata.matchesRegularExpression that can be used within the Apply dynamic _expression_. 

It takes two arguments of type Edm.String and returns true if the first argument matches the regular _expression_ in the second argument, using syntax and semantics of _javascript_ regular expressions, see https://developer.mozilla.org/en-US/docs/Web/_javascript_/Guide/Regular_Expressions

Ralf Handl (SAP): ODATA-817 is OPEN

Ralf Handl (SAP): Ralf to look into regular _expression_ syntax of mainstream programming languages and cross-check with _javascript_

Ralf Handl (SAP): 2.ODATA-978 New annotation for availability/advertisement of bound actions/functions

Ralf Handl (SAP): New Core or Capabilities annotation on actions/functions: AvailableOnAllInstances: 

      <Term Name="AvailableOnAllInstances" Type="Core.Tag" DefaultValue="true" AppliesTo="Action Function"> 

        <Annotation Term="Core.Description" String="Bound action/function is available on all instances of the binding parameter type" /> 

        <Annotation Term="Core.LongDescription" String="If annotated with value of 'false', clients should check instance representations for action/function advertisements" /> 

      </Term> 

Alternative proposal: 

      <Term Name="AdvertisedOnInstances" Type="Core.Tag" DefaultValue="true" AppliesTo="Action Function"> 

        <Annotation Term="Core.Description" String="Instance representations of the binding parameter type will contain advertisement if action/function is available on that instance" /> 

      </Term>

Ralf Handl (SAP): ODATA-978 is OPEN

Ralf Handl (SAP): Mike: alternatively advertise non-applicability in payload

Ralf Handl (SAP): "#Model.RemainingVacation": null

Ralf Handl (SAP): "#Model.RemainingVacation": {

    "title": "Remaining Vacation",

    "target": "Managers(22)/Employees/RemainingVacation"

  },

Ralf Handl (SAP): Mike and Ralf to come up with proposal

Ralf Handl (SAP): iv.OData CSDL

1.ODATA-879 Support Arrays of Arrays

Ralf Handl (SAP): Proposal:

Don't add a formal notion of arrays of arrays to the data model (it breaks too many rules). 

Instead, use "Edm.Untyped" (see ODATA-881) or "Collection(Edm.Untyped)" (see ODATA-973) as a way to allow payloads that contain such structure.

Ralf Handl (SAP): Hubert: introduction of @Core.NumericValueException poses a problem in arrays of numeric values, some of which are the exceptional values

Ralf Handl (SAP): Mike: split this issue into

- allow annotating an item in an ordered collection

- allow collections of collections

Ralf Handl (SAP): Consensus: reconsider NumericValueException, e.g. make it a preference

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

a.Thursday October 06, 2016 during 8-10 am PT?

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

Ralf Handl (SAP): Meeting is adjourned

 

 

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Dienstag, 27. September 2016 11:58
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2016-09-29

 

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

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

 

2.        Approve agenda [8:05 am PT]

 

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

a.     Minutes from September 22, 2016 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/58990/latest/odata-meeting-145_on-20160922-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.        V4.01 [9:20 am PT]

a.     Document Walk-through

                                  i.    OData JSON Format Version 4.01 – resuming with Chapter 14 Delta Response

 

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

                                  i.    OData Protocol

1.     ODATA-965 UpdateGeoJSON Reference to RFC7946

2.     ODATA-970 11.5.2: also mention advertising operations on collections

                                 ii.    Enumerations

1.     ODATA-494 Define inheritance for enumeration types

2.     ODATA-849 Add possibility for enumeration types to "extend" another enumeration type

3.     ODATA-874 Allow Edm.String as underlying type for enumeration types

                                iii.    Annotations

1.     ODATA-817 Add client-side function odata.matchesRegularExpression

2.     ODATA-978 New annotation for availability/advertisement of bound actions/functions

                                iv.    OData CSDL

1.     ODATA-879 Support Arrays of Arrays

2.     ODATA-929 Nullable facet should default to false for collection types, rather than being unspecified

3.     ODATA-935 Allow singletons to be members of an entity set

4.     ODATA-959 Allow path in an edm:key to also use a primitive property of a non null-able navigation property (recursively) of the entity type.

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

6.     ODATA-973 Should we relax prohibiting Collection(Edm.ComplexType) and Collection(Edm.Untyped)

                                 v.    OData JSON Format

1.     ODATA-557 Allow exponential notation for Edm.Decimal

2.     ODATA-969 Chapter 15, Example 32: syntax of "target" URL

                                vi.    Interfaces

1.     ODATA-619 Attach action and function signatures to terms, i.e. make a term definition an interface definition

                               vii.    Waiting for refined proposal

1.     ODATA-618 Allow using term names in positions that allow type names

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

3.     ODATA-735 Enhance the CSDL for instance annotations

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

5.     ODATA-811 Define propagation and (partial) overriding of annotations

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

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

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

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

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

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

12.  ODATA-964 Need to clarify nested delta representation

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

14.  ODATA-976 Support partial keys

 

6.        Next meeting [9:50 am PT]

a.     Thursday October 06, 2016 during 8-10 am PT?

 

7.        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/document.php?document_id=56024&wg_abbrev=odata