RE: [odata] Agenda for OData TC meeting on 2015-11-19

anonymous morphed into Matt Borges (SAP)

Room information was updated by: Stefan

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

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

Ralf Handl (SAP): Achieved quorumyes

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

Ralf Handl (SAP): Agenda is approved

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

a.Minutes from November 12, 2015 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/56937/latest/odata-meeting-113_on-20151112-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.None

Ralf Handl (SAP): 5.JSON Format for CSDL [8:20am PT]

a.Document Walk-through

i.https://www.oasis-open.org/committees/download.php/56934/odata-json-csdl-v4.0-wd01-2015-11-13.docx

Ralf Handl (SAP): Ralf to prepare cleaned-up version that we may publish as a first review draft

Ralf Handl (SAP): Planning to have at least a second public review before moving it to Committee Specification

Ralf Handl (SAP): 6.V4.0 ERRATA03 [8:50am PT]

a.Issues for V4.0_ERRATA03 in New or Open state

Ralf Handl (SAP): i.OData Protocol

1.ODATA-830             Header OData-EntityId: when required

2.ODATA-837             Example 28: replace $deltaToken with a valid custom query option

3.ODATA-869             Explicitly state the location of the Content-ID header in a change set

4.ODATA-870             Round-off description for creating related entities when creating an entity

5.ODATA-882             Mismatch between 11.2.6 Requesting Related Entities and 11.2.7 Requesting Entity References

Ralf Handl (SAP): 8.3.3: change "create operation" to "create or upsert operation"

13.1.1 item 24: change "POST/PATCH" to "create or upsert operation"

Ralf Handl (SAP): ODATA-830 is OPEN

Hubert Heijkers: I move to resolve ODATA-830 as proposed.

Matt Borges (SAP): I second

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

Ralf Handl (SAP): 2.ODATA-837             Example 28: replace $deltaToken with a valid custom query option

Ralf Handl (SAP): Example 28: resource URL and corresponding context URL

http://host/service/Customers?$deltaToken=1234

http://host/service/$metadata#Customers/$delta

Ralf Handl (SAP): Proposal: treat $deltaToken as a reserved token that services can use in delta links, similar to how we have reserved $skipToken.

Ralf Handl (SAP): Proposal: treat $deltatoken as a reserved token that services can use in delta links, similar to how we have reserved $skiptoken. (lower-case t)

Mike Pizzo1: Proposal: Treat $deltatoken (all lower-case) as a reserved token that services can use in delta links, similar to how we have reserved $skiptoken.

Mike Pizzo1: I move we resolve ODATA-830 as proposed.

Hubert Heijkers: I second

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

Ralf Handl (SAP): 3.ODATA-869             Explicitly state the location of the Content-ID header in a change set

Ralf Handl (SAP): State explicitly that the Content-ID header MUST be part of the MIME-part-header section and not part of the inner OData request.

Ralf Handl (SAP): ODATA-869 is OPEN

Matt Borges (SAP): I move we resolve ODATA-869 as proposed.

Mike Pizzo2: I second

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

Ralf Handl (SAP): 4.ODATA-870             Round-off description for creating related entities when creating an entity

Ralf Handl (SAP): Don't describe any rules in 11.4.2.2, but merely refer to 11.4.2, like this:

"A request to create an entity that includes related entities, represented using the appropriate inline representation, is referred to as a deep insert. Media entities, whose binary representation cannot be represented inline, cannot be created within a deep insert.

The entity is created observing the rules described in section 11.4.2 as if it was posted against the original target URL extended with the navigation property for this related entity.

On success, the service

Ralf Handl (SAP): ODATA-870 is OPEN

Mike Pizzo2: I move we resolve ODATA-870 as proposed.

Hubert Heijkers: I second

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

Ralf Handl (SAP): 5.ODATA-882             Mismatch between 11.2.6 Requesting Related Entities and 11.2.7 Requesting Entity References

Ralf Handl (SAP): 11.2.6 defines that requests to nullable single-valued navigation properties return 204 No Content if no entity is currently related.

11.2.7 defines that all requests for references to a single entity return 404 Not Found, not distinguishing between "direct" resource paths and resource paths to related entities.

This leads to:

GET Employees('TheBigBoss')/Manager --> 204 No Content

GET Employees('TheBigBoss')/Manager/$ref --> 404 Not Found

Clarify whether this is intentional:

A) Of course, the related Manager is empty, so the reference does not exist, or

B) Ooops, of course both requests should return the same response code because /$ref is just a briefer representation of the non-existing related entity

Also clarify what happens if other path segments are added, e.g. properties or navigation properties:

GET Employees('TheBigBoss')/Manager/Name --> ???

GET Employees('TheBigBoss')/Manager/Department --> ???

Ralf Handl (SAP): ODATA-882 is OPEN

Ralf Handl (SAP): If the property is single-valued and has the null value, the service responds with 204 No Content.

If the property is not available, for example due to permissions, the service responds with 404 Not Found.

Ralf Handl (SAP): A $value request for a property that is null results in a 204 No Content response.

If the property is not available, for example due to permissions, the service responds with 404 Not Found.

Ralf Handl (SAP): Mike: look at other implementations and find out what they do

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

a.Thursday December 03, 2015 during 8-10am PT?

Ralf Handl (SAP): Agreed

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

Ralf Handl (SAP): Ram: Ballots for OData ISO have started, will end in January

Ralf Handl (SAP): Ram to give more insight in the next meeting!

Ralf Handl (SAP): Put Face-to-face on next agenda

Ralf Handl (SAP): Make formal motion for F2F date#

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Dienstag, 17. November 2015 10:22
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2015-11-19

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

2. Approve agenda [8:05am PT]

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

a. Minutes from November 12, 2015 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/56937/latest/odata-meeting-113_on-20151112-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. JSON Format for CSDL [8:20am PT]

a. Document Walk-through

i. https://www.oasis-open.org/committees/download.php/56934/odata-json-csdl-v4.0-wd01-2015-11-13.docx

b. Issues for JSON Format for CSDL in Applied state

6. V4.0 ERRATA03 [8:50am PT]

a. Issues for V4.0_ERRATA03 in New or Open state

i. OData Protocol

1. ODATA-830 Header OData-EntityId: when required

2. ODATA-837 Example 28: replace $deltaToken with a valid custom query option

3. ODATA-869 Explicitly state the location of the Content-ID header in a change set

4. ODATA-870 Round-off description for creating related entities when creating an entity

5. ODATA-882 Mismatch between 11.2.6 Requesting Related Entities and 11.2.7 Requesting Entity References

ii. OData URL Conventions

1. ODATA-784 Need to specify the behaviour of arithmetic operators on Decimal type

2. ODATA-785 Numeric promotion (on overflow) across "number type families" is undesirable.

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

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

i. Adoption Blocker

1. ODATA-881 Add support for Edm.Untyped

2. ODATA-876 Allow services to return contained entities inline for delta responses

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

4. ODATA-613 Allow POST to entity sets using the delta-response format

ii. Simplified Syntax

1. ODATA-664 Consider supporting parameterless function imports with no parens

2. ODATA-812 Allow omitting namespaces for unambiguous functions/actions

3. ODATA-763 Allowing implicit aliasing of parameters (public comment c201412e00001)

4. ODATA-799 Define Key-As-Segment URL convention for resource paths

5. ODATA-834 Make type prefix optional for enumeration literals in URLs

iii. Enum Types

1. Proposal by Ken Baclawski: https://www.oasis-open.org/committees/download.php/56805/DerivationForEnumerations_KenBaclawski.html

2. ODATA-494 Define inheritance for enumeration types

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

iv. Set Operations

1. ODATA-666 Define Deep Update and Deep Upsert operations

2. ODATA-836 Allow applying actions to a filtered collection of entities

3. ODATA-613 Allow POST to entity sets using the delta-response format

4. ODATA-615 Allow PATCH and DELETE with $filter on collections to modify or delete all (and only) the matching entities

5. ODATA-616 Allow POST to collections of complex and primitive types, and DELETE with $filter

6. ODATA-820 Allow indexing into collections

v. Simplified Payload

1. ODATA-561 odata.type shouldn't require "#" for primitive types

2. ODATA-630 Consider making odata the default namespace for annotations

3. ODATA-813 Allow no metadata for non-OData clients

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

5. ODATA-818 Omit properties whose value is null or the $metadata-defined default value

6. ODATA-809 Define non-message format for final response of async request

8. Next meeting [9:50am PT]

a. Thursday December 03, 2015 during 8-10am PT?

9. AOB and wrap up [9:55am 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

odata message