RE: [odata] Agenda for OData TC meeting on 2015-05-21

Room information was updated by: Stefan

Please register yourself at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=39099 - thanks.

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

Ted Jones (Red Hat) morphed into Ted Jones (Redhat)

anonymous morphed into Matt Borges (SAP)

Ted Jones (Redhat) morphed into Ted Jones (Red Hat)

Please change your name from 'anonymous' using the Settings button

anonymous morphed into Ralf Handl (SAP)

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

Ralf Handl (SAP): Quorum achieved

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 May 07, 2015 TC meeting: https://www.oasis-open.org/committees/download.php/55618/odata-meeting-97_on-20150507-minutes.html

Ralf Handl (SAP): Minutes are approved

Ralf Handl (SAP): 4.Review action

Ralf Handl (SAP): None

Ralf Handl (SAP): 5.Discuss scope of TC work for the next 12-18 months

Ralf Handl (SAP): a.Topics

i.JSON for $metadata

ii.V4.1 as a compatible protocol version with version negotiation: Issues for V4.1_WD01

iii.I-REST / ... profile

b.Actions

i.Recharter the TC?

1.Current Charter

2.Process description for Rechartering

Ralf Handl (SAP): Mike: OData V4 is gaining traction

Ralf Handl (SAP): Mike: also see some resistance/push-back due to perceived complexity

Ralf Handl (SAP): Mike: make OData more appealing

Ralf Handl (SAP): Mike: tackle problems people have run into when implementing OData

Ralf Handl (SAP): Ted: it is important to focus on adoption and addressing concerns

Ralf Handl (SAP): Ted: main question: is an OData service really better than a custom REST service? Why?

Ralf Handl (SAP): Ted: seems to be general misunderstanding of OData

Ralf Handl (SAP): Ted: offer a Webinar on OData from the TC

Ralf Handl (SAP): Brent: formalize more around streaming

Ralf Handl (SAP): Brent: more about performance

Ralf Handl (SAP): Brent: zipped JSON versus BSON or other binary format

Ralf Handl (SAP): Mark: anything to get people started, get a simple service up and running quickly

Ralf Handl (SAP): Mark: then gradually leverage the power the spec gives you

Ralf Handl (SAP): Mike: common authentication model

Ralf Handl (SAP): Mike: allow clients to generically connect to services

Ralf Handl (SAP): Mike: have vocabulary describing supported authentication mechanisms

Ralf Handl (SAP): Mike: themes:

Ralf Handl (SAP): - adoption

Ralf Handl (SAP): - technical problems

Ralf Handl (SAP): - catalog of end points

Ralf Handl (SAP): - extensibility

Ralf Handl (SAP): Susan: how is the progress with ISO, and does this affect our plans?

Ralf Handl (SAP): Mike: will check with Ram on status

Ralf Handl (SAP): Mike: work we do now needs to submitted to ISO separately

Ralf Handl (SAP): Mike: OData-TC remains keeper of the spec

Ralf Handl (SAP): Mike: a lot of work not spec-related

Ralf Handl (SAP): Martin: continue work on Data Aggregation and Temporal extensions

Ralf Handl (SAP): Mike: .NET library received contribution on Data Aggregation

Ralf Handl (SAP): Ralf: check with Olingo team which steps they are taking

Ralf Handl (SAP): Mike: would be helpful to have statement of goals for next 12-18 months

Ralf Handl (SAP): 2.Process description for Rechartering

Ralf Handl (SAP): https://www.oasis-open.org/policies-guidelines/tc-process#rechartering

Ralf Handl (SAP): Martin: formulate our goals in the form of a revised charter, then check if we need to go through the process

Ralf Handl (SAP): Topics:

Ralf Handl (SAP): JSON for $metadata, XML is an inhibitor to adoption

Ralf Handl (SAP): V4.1 targeted at adoption inhibitors

Ralf Handl (SAP): Profile for simple REST services based on OData patterns

Ralf Handl (SAP): Continue work on Data Aggregation and Temporal

Ralf Handl (SAP): Whitepaper in implementing OData: continue, check which goes into V4.1 or REST profile and which into the whitepaper

Ralf Handl (SAP): Martin: HTTP/2 is standardized, used by first browsers - investigate how that affects OData

Ralf Handl (SAP): Martin: can we leverage e.g. server push

Ralf Handl (SAP): Mike: seems very interesting

Ralf Handl (SAP): Martin: Chrome and FireFox already use it, Google will discontinue SPDY and move to HTTP/2

Ralf Handl (SAP): Martin will give presentation -> Action Item

Matt Borges (SAP): Yes I definitely agree

Ralf Handl (SAP): Mike will summarize this discussion into a "Goals" description

Ralf Handl (SAP): Martin: decide on format for "REST profile"

Ralf Handl (SAP): Mike: Could be (part of) V4.1 specification

Ralf Handl (SAP): Use Label mechanism of Jira to categorize issues

Ralf Handl (SAP): Possible labels:

Ralf Handl (SAP): -AdoptionBlocker

Ralf Handl (SAP): -- recurring issue, not just nice to have

Ralf Handl (SAP): - GoodIdea

Ralf Handl (SAP): -- not yet reported as an issue by (potential) adopters

Ralf Handl (SAP): - RatherNot

Ralf Handl (SAP): -- adds too much complexity

Ralf Handl (SAP): - Clarification

Ralf Handl (SAP): -- things that need defining but don't qualify for an Errata

Ralf Handl (SAP): Rename "RatherNot" to "NeedsFurtherJustification"

Ralf Handl (SAP): ODATA-813 Allow no metadata for non-OData clients

Ralf Handl (SAP): ODATA-812 Allow omitting namespaces for unambiguous functions/actions

Ralf Handl (SAP): ODATA-811 Define propagation and (partial) overriding of annotations

Ralf Handl (SAP): ODATA-809 Define non-message format for final response of async request

Ralf Handl (SAP): ODATA-799 Define Key-As-Segment URL convention for resource paths

Ralf Handl (SAP): ODATA-798 Semantic Key or Alternate Key for entity types

Ralf Handl (SAP): New category: Extension - something that the V4 spec allows but doesn't describe

Ralf Handl (SAP): ODATA-786 Extend definition of edmath _expression_

Ralf Handl (SAP): New tag - Usability (from the client developer's perspective)

Ralf Handl (SAP): ODATA-763 Allowing implicit aliasing of parameters (public comment c201412e00001)

Ralf Handl (SAP): GET http://serviceroot/Add(a=@a,b=@b)?@a=1&@b=1.

Ralf Handl (SAP): http://serviceroot/Add()?@a=1&@b=1.

Ralf Handl (SAP): http://serviceroot/Add()?a=1&b=1.

Ralf Handl (SAP): Action item for all: go over remaining issues and attach labels. Just add, don't remove, we'll resolve that in a future meeting

Ralf Handl (SAP): 6.Process issues

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

i.OData JSON Format

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

Ralf Handl (SAP): ODATA-807 is OPEN

Ralf Handl (SAP): Mike: add comment to Errata03 that clients should not rely on the target to be present in this case

Mike Pizzo: Revised proposal for 807: Provide guidance to clients that they should not require targetid for deleted link for a to 0..1 relationship.

Martin Zurmuehl: I move to resolve ODATA 807 as proposed (revised proposal)

Mike Pizzo: I second

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

Ralf Handl (SAP): ii.OData Vocabularies

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

Ralf Handl (SAP): ODATA-808 is OPEN

Mike Pizzo: I move we resolve ODATA-808 as proposed.

Martin Zurmuehl: i second

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

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

a.Thursday June 05, 2015 during 8-10am PT?

Ralf Handl (SAP): b. Thursday June 11, 2015 during 8-10am PT?

Ralf Handl (SAP): Next meeting: Thursday June 11, 2015 during 8-10am PT

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

Ralf Handl (SAP): Meeting is adjourned

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Mittwoch, 20. Mai 2015 16:19
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2015-05-21

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

2. Approve agenda [8:05am PT]

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

a. Minutes from May 07, 2015 TC meeting: https://www.oasis-open.org/committees/download.php/55618/odata-meeting-97_on-20150507-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. Discuss scope of TC work for the next 12-18 months

a. Topics