RE: Agenda for OData TC meeting on 2019-01-17

[16:53] Mike Pizzo: [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=47969

2.Approve agenda [8:05 am PT]

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

a.Minutes from January 10, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/64507/Minutes%20of%202019-01-10%20Meeting%20%23242.docx

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

a.Upcoming

i.#0037 Concept for Google Protocol Buffers as a data format  Hubert Heijkers  2019-03-28

b.In progress

i.#0036 Register the OData- headers and preferences with IANA  Mark Biamonte  2018-07-26

1.Mike Pizzo: follow-up on the benefit of registering these headers and preferences

5.Issues [8:20 am PT]

a.Triage V4.01 issues

i.Issue authors:

1.Move nice-to-have issues to V4.02_WD01

2.Label must have issues with current_version

3.Do this before the TC meeting on Thursday January 24

b.Urgent

i.ODATA-1265 Clarify property paths used in a lambda predicate _expression_

ii.ODATA-1244 Add a function to determine aggregated values within common expressions

iii.ODATA-1207 Clarify need for @odata.id in nested response structures

iv.ODATA-1271 Define a validation term for terms applicable in a given context

v.ODATA-1269 Add QueryRestrictions to the Capabilities Vocabulary

vi.ODATA-1273 Define mapping of permission scopes to resources

c.V4.01: NEW or OPEN

i.ODATA-1272 Highlight implications of derived complex types to their annotations

ii.ODATA-1270 14.4.11: rephrase prose text for dynamic _expression_ Null

iii.ODATA-1263 Requirement for 204 (No Content) with 11.4.3 "Update an Entity" is not backwards compatible

iv.ODATA-1262 Explicitly state structural restrictions of type Edm.Untyped

v.ODATA-1261 Allow $pagesize system query option

vi.ODATA-1260 Clarify read-write access via URLs differing from the canonical/read/edit URL

vii.ODATA-1259 Clarify @type (@odata.type) and metadata=full

viii.ODATA-1266 Geo literals with three dimensions

ix.ODATA-1250 GeoJSON, SRID, and LineString

x.ODATA-1243 Clarify whether $orderby and string comparison with ge, gt, le, lt is language-specific

xi.ODATA-1242 Clarify that resolved relative URIs in batch responses cannot contain content-ID references

xii.ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation

xiii.ODATA-1177 Add "JSON properties" to OData

xiv.ODATA-1165 Describe $expand and $select via prose text and examples, remove ABNF snippets

xv.ODATA-1267 URL Conventions example in 5.1.1.5.1 has "bad" whitespace

xvi.ODATA-1253 Abstract type definition Core.Number as a super-type of all numeric types

xvii.ODATA-1246 Allow BaseType to be a ComplexType

xviii.ODATA-1239 Define a mechanism to distinguish between inserted and updated entities in a Delta Response

xix.ODATA-1238 Clarifications for select-list in ContextUrl

xx.ODATA-1198 ETag handling deviations from RFC7232 are avoidable if we consider two kinds of ETag (ETag in response header and ETag in response payload)

xxi.ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts

xxii.ODATA-1135 Document use of JSON $schema

xxiii.ODATA-1064 Add ability to annotate collections to return only count and NextLink

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

d.Data Aggregation: NEW or OPEN

i.ODATA-1256 Harmonize usage of custom aggregates with structured aggregatable properties

ii.ODATA-1218 Transformations for recursive hierarchy processing

iii.ODATA-945 Correct examples 53 and 54

e.Vocabularies: NEW or OPEN with concrete proposal

i.ODATA-1176 Capabilities: add new term SelectSupport

ii.ODATA-1099 Add annotations to describe custom query options and custom headers

f.Vocabularies: NEW or OPEN that need more discussion

i.ODATA-1264 CRUD descriptions on entity sets

ii.ODATA-1214 Annotate constructor actions

iii.ODATA-1140 ODATA-884 / Add details to HTTPResponseCode term

iv.ODATA-1107 Introduce instance annotation to specify which types an instance "implements"

v.ODATA-1060 Improve specification of element response requirements

vi.ODATA-884 Enable enumerating the valid requests and responses for a particular resource.

6.Next meetings [9:50 am PT]

a.Thursday January 22, 2019 during 8-10 am PST (17:00-19:00 CET)

b.Thursday January 29, 2019 during 8-10 am PST (17:00-19:00 CET)

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

[2] References

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

Conference call & Screen sharing: https://lync.co.sap.com/meet/ralf.handl/Q4QB1098

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

[3] Timeline

https://www.oasis-open.org/committees/download.php/62637/TC%20Timeline-2018-03-02.docx

[17:01] Ralf Handl (SAP SE): Voting Members: 3 of 9 (33%) (used for quorum calculation)

[17:02] Ralf Handl (SAP SE): Voting Members: 4 of 9 (44%) (used for quorum calculation)

[17:03] Hubert Heijkers (IBM): Count me in, be there in 2 mins...

[17:03] Ralf Handl (SAP SE): Voting Members: 6 of 9 (66%) (used for quorum calculation)

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

[17:05] Ralf Handl (SAP SE): Ted will keep today's minutes

[17:05] Ralf Handl (SAP SE): Thanks!

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

[17:05] Ralf Handl (SAP SE): Agenda is approved

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

a.Minutes from January 10, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/64507/Minutes%20of%202019-01-10%20Meeting%20%23242.docx

[17:06] Ralf Handl (SAP SE): Minutes look great, thanks to George!

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

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

a.Upcoming

i.#0037 Concept for Google Protocol Buffers as a data format  Hubert Heijkers  2019-03-28

b.In progress

i.#0036 Register the OData- headers and preferences with IANA  Mark Biamonte  2018-07-26

1.Mike Pizzo: follow-up on the benefit of registering these headers and preferences

[17:08] Ralf Handl (SAP SE): Mike will reply to Chet's questions on registration

[17:08] Ralf Handl (SAP SE): 5.Issues [8:20 am PT]

a.Triage V4.01 issues

i.Issue authors:

1.Move nice-to-have issues to V4.02_WD01

2.Label must have issues with current_version

3.Do this before the TC meeting on Thursday January 24

[17:11] Mike Pizzo: Action item for all: go through existing 4.01 active issues and label any that you believe must be in 4.01 with "current_version"

[17:11] Ralf Handl (SAP SE): b.Urgent

i.ODATA-1265 Clarify property paths used in a lambda predicate _expression_

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

[17:25] Mike Pizzo: Example 93 could be:

http://host/service/Products?$filter=OrderItems/any(od:od/UnitPrice ne UnitPrice)

[17:26] Mike Pizzo: (sorry; that would be example 92)

[17:26] Gerald Krause (SAP): is actually ex 92; describe its identical with having $it in the path

[17:28] Mike Pizzo: I move we resolve ODATA-1265 as proposed, with the recommended clarification

[17:28] Gerald Krause (SAP): I second.

[17:29] Ralf Handl (SAP SE): ODATA-1265 is RESOLVED with the recommended clarification

[17:29] Ralf Handl (SAP SE): ii.ODATA-1244 Add a function to determine aggregated values within common expressions

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

[17:34] Mike Pizzo: Hubert: can still assign an alias using $compute

[17:45] Hubert Heijkers (IBM): I move to resolve ODATA-1244 as proposed.

[17:45] Mike Pizzo: I second

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

[17:45] Ralf Handl (SAP SE): i.ODATA-1207 Clarify need for @odata.id in nested response structures

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

[17:50] Ralf Handl (SAP SE): ODATA-1207 is OPEN

[17:57] Mike Pizzo: In 4.01, we could say that an entity representation may omit both the id and the key fields, in which case it must be treated as a transient entity.

[17:58] Mike Pizzo: We want aggregation to have same behavior as common rules.

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

Examples in the document should comply with the rules stated in the JSON format specification. Since the examples throughout the document return transient aggregated entities, all examples having responses with nested projections of related entities need to include an "@odata.id":null annotation for each of those in OData V4.0. For V4.01, clients must be prepared to receive entities having neither @odata.id nor key fields to indicate that it is a transient entity. Proposal is to update all examples in the document and remove all @odata.id:null.

Mention that all examples are based on OData V4.01.

[18:05] Mike Pizzo: Examples in the document should comply with the rules stated in the JSON format specification. Since the current examples throughout the document that return transient aggregated entities based on 4.0, all examples having responses with nested projections of related entities should have included an "@odata.id":null annotation.

Proposal is to make a blanket statement for V4.01 that clients must be prepared to receive entities having neither @odata.id nor key fields and, in the absence of any additional information, must treat such entities as transient.

We will update the examples in the aggregation specification to be 4.01 and thus all @odata.id:null (as well as other 4.01 simplifications).

Mention in Aggregation that all examples are based on OData V4.01, and call out what would be different across examples for V4.0.

[18:06] Mike Pizzo: I move to resolve ODATA-1207 as proposed

[18:07] Hubert Heijkers (IBM): I second

[18:07] Ralf Handl (SAP SE): ODATA-1207 RESOLVED as proposed

[18:07] Ralf Handl (SAP SE): iv.ODATA-1271 Define a validation term for terms applicable in a given context

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

[18:23] Ralf Handl (SAP SE): ODATA-1271 is OPEN

[18:24] Mike Pizzo: Need to be clear that this is not a restriction, it is a hint as to what may be applicable in a particular context.

[18:26] Mark Biamonte (Progress): I have had something come up that I need to drop off of the call.

[18:26] Ralf Handl (SAP SE): @Mark: ok, and thanks for attending!

[18:31] Mike Pizzo: proposed wording: Names of specific terms that are applicable and may be applied in the current context. This annotation does not restrict the use of other terms.

[18:32] Mike Pizzo: I move to resolve ODATA-1271 as proposed, with the revised wording.

[18:32] Gerald Krause (SAP): I second.

[18:33] Ralf Handl (SAP SE): ODATA-1271 is RESOLVED with the revised proposal

[18:33] Ralf Handl (SAP SE): v.ODATA-1269 Add QueryRestrictions to the Capabilities Vocabulary

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

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

We have cases where we want to have an entity set which is only accessible by navigation from another entity but it is not a containment relationship.  We currently have InsertRestrictions and UpdateRestrictions in the capabilities vocabulary but no corresponding QueryRestrictions.  We should add QueryRestrictions to the capabilities vocabulary.

[18:34] Matt Borges (SAP): <Term Name="QueryRestrictions" Type="Capabilities.QueryRestrictionsType" AppliesTo="EntitySet">

    <Annotation Term="Core.Description" String="Restrictions on queries" />

</Term>

<ComplexType Name="QueryRestrictionsType">

    <Property Name="DirectlyAccessible" Type="Edm.Boolean" Nullable="false" DefaultValue="true">

        <Annotation Term="Core.Description" String="Whether entities in this entity set can be accessed directly or must be accessed through a navigation property." />

    </Property>

</ComplexType>

[18:35] Ralf Handl (SAP SE): GET Addresses --> forbidden

[18:35] Ralf Handl (SAP SE): GET Employees(123)/MainAddress --> allowed

[18:35] Ralf Handl (SAP SE): GET Addresses('ABC') --> ???

[18:39] Ralf Handl (SAP SE): Mike: just don't have an entity set

[18:44] Ralf Handl (SAP SE): Write-only entity sets can be annotated with Core.Permissions=Read

[18:47] Matt Borges (SAP): I'm fine closing 1269 with no action.

[18:49] Ralf Handl (SAP SE): vi.ODATA-1273 Define mapping of permission scopes to resources

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

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

Our Authorizations vocabulary describes multiple different authentication flows and the scopes that can be requested for each flow.

What is missing is a way of documenting which resources/properties are available given a particular scope.

This would allow documentation to be generated that tells the client/app which scopes they need to request in order to access certain resources.

OData-884 and OData-1145 attempt to align with OpenAPI by describing operations supported, and necessary headers, parameters, and permissions required to invoke those operations.  However, we have moved away from OData-884, which uses a more operation-centric approach, to something that aligns with our capabilities.  In doing so, we need a way to specify what permissions are required to access a particular resource (or properties within a resource).

[18:53] Ralf Handl (SAP SE): Hubert: has larger services, access rights are tied to the authenticated user and don't depend on the authentication flow

[18:57] Ralf Handl (SAP SE): 6.Next meetings [9:50 am PT]

a.Thursday January 22, 2019 during 8-10 am PST (17:00-19:00 CET)

b.Thursday January 29, 2019 during 8-10 am PST (17:00-19:00 CET)

[18:57] Ralf Handl (SAP SE): Reminder: tag your favorite issues until next Thursday so we can triage

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

[18:59] Ralf Handl (SAP SE): Meeting is adjoured

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf
Sent: Mittwoch, 16. Januar 2019 18:48
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2019-01-17

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

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

2. Approve agenda [8:05 am PT]

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

Minutes from January 10, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/64507/Minutes%20of%202019-01-10%20Meeting%20%23242.docx

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

Upcoming

i. #0037 Concept for Google Protocol Buffers as a data format – Hubert Heijkers – 2019-03-28

In progress

i. #0036 Register the OData- headers and preferences with IANA – Mark Biamonte – 2018-07-26

Mike Pizzo: follow-up on the benefit of registering these headers and preferences

5. Issues [8:20 am PT]

Triage V4.01 issues

i. Issue authors:

Move nice-to-have issues to V4.02_WD01
Label “must have” issues with “current_version”
Do this before the TC meeting on Thursday January 24

Urgent

i. ODATA-1265 Clarify property paths used in a lambda predicate _expression_

ii. ODATA-1244 Add a function to determine aggregated values within common expressions

iii. ODATA-1207 Clarify need for @odata.id in nested response structures

iv. ODATA-1271 Define a validation term for terms applicable in a given context

v. ODATA-1269 Add QueryRestrictions to the Capabilities Vocabulary

vi. ODATA-1273 Define mapping of permission scopes to resources

V4.01: NEW or OPEN

i. ODATA-1272 Highlight implications of derived complex types to their annotations

ii. ODATA-1270 14.4.11: rephrase prose text for dynamic _expression_ Null

iii. ODATA-1263 Requirement for 204 (No Content) with 11.4.3 "Update an Entity" is not backwards compatible

iv. ODATA-1262 Explicitly state structural restrictions of type Edm.Untyped

v. ODATA-1261 Allow $pagesize system query option

vi. ODATA-1260 Clarify read-write access via URLs differing from the canonical/read/edit URL

vii. ODATA-1259 Clarify @type (@odata.type) and metadata=full

viii. ODATA-1266 Geo literals with three dimensions

ix. ODATA-1250 GeoJSON, SRID, and LineString

x. ODATA-1243 Clarify whether $orderby and string comparison with ge, gt, le, lt is language-specific

xi. ODATA-1242 Clarify that resolved relative URIs in batch responses cannot contain content-ID references

xii. ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation

xiii. ODATA-1177 Add "JSON properties" to OData

xiv. ODATA-1165 Describe $expand and $select via prose text and examples, remove ABNF snippets

xv. ODATA-1267 URL Conventions example in 5.1.1.5.1 has "bad" whitespace

xvi. ODATA-1253 Abstract type definition Core.Number as a super-type of all numeric types

xvii. ODATA-1246 Allow BaseType to be a ComplexType

xviii. ODATA-1239 Define a mechanism to distinguish between inserted and updated entities in a Delta Response

xix. ODATA-1238 Clarifications for select-list in ContextUrl

xx. ODATA-1198 ETag handling deviations from RFC7232 are avoidable if we consider two kinds of ETag (ETag in response header and ETag in response payload)

xxi. ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts

xxii. ODATA-1135 Document use of JSON $schema

xxiii. ODATA-1064 Add ability to annotate collections to return only count and NextLink

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

Data Aggregation: NEW or OPEN

i. ODATA-1256 Harmonize usage of custom aggregates with structured aggregatable properties

ii. ODATA-1218 Transformations for recursive hierarchy processing

iii. ODATA-945 Correct examples 53 and 54

Vocabularies: NEW or OPEN with concrete proposal

i. ODATA-1176 Capabilities: add new term SelectSupport

ii. ODATA-1099 Add annotations to describe custom query options and custom headers

Vocabularies: NEW or OPEN that need more discussion

i. ODATA-1264 CRUD descriptions on entity sets

ii. ODATA-1214 Annotate constructor actions

iii. ODATA-1140 ODATA-884 / Add details to HTTPResponseCode term

iv. ODATA-1107 Introduce instance annotation to specify which types an instance "implements"

v. ODATA-1060 Improve specification of element response requirements

vi. ODATA-884 Enable enumerating the valid requests and responses for a particular resource.

6. Next meetings [9:50 am PT]

Thursday January 22, 2019 during 8-10 am PST (17:00-19:00 CET)
Thursday January 29, 2019 during 8-10 am PST (17:00-19:00 CET)

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

[2] References

Chat room: http://webconf.soaphub.org/conf/room/odatatc
Conference call & Screen sharing: https://lync.co.sap.com/meet/ralf.handl/Q4QB1098
Conference call details: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/63673/latest/TC%20meeting%20dial-in%20details.htm

[3] Timeline

https://www.oasis-open.org/committees/download.php/62637/TC%20Timeline-2018-03-02.docx

odata message