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

Room information was updated by: Stefan Hagen

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

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

Minutes draft of previous meeting: https://www.oasis-open.org/committees/download.php/59035/odata-meeting-146_on-20160929-minutes.html

Stefan Hagen: From Registration Site(Voting Members: 3 of 12 (25%) (used for quorum calculation) )

Stefan Hagen: One missing "Voting Members: 6 of 12 (50%) (used for quorum calculation) "

Ralf Handl (SAP): Voting Members: 7 of 12 (58%) (used for quorum calculation)

Ralf Handl (SAP): Achieved quorum: yes

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

Susan Malaika: hubert is on

Ralf Handl (SAP): https://issues.oasis-open.org/browse/ODATA-984 - Make $-prefix optional for system query options

Ralf Handl (SAP): https://issues.oasis-open.org/browse/ODATA-985 - The HTTP Specification document referenced in the OData Protocol Spec has been obsoleted

Ralf Handl (SAP): Add these to 5.a.i

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

a.Minutes from September 29, 2016 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/59035/latest/odata-meeting-146_on-20160929-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

anonymous morphed into Ted Jones (Red Hat)

Ralf Handl (SAP): Mark in contact with Robin Cover from OASIS, provided with templates

Ralf Handl (SAP): Mark sent samples to Robin for cross-checking

Ralf Handl (SAP): Waiting for feedback

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

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

i.OData Protocol

Ralf Handl (SAP): 1.ODATA-965 UpdateGeoJSON Reference to RFC7946

Ralf Handl (SAP): @Stefan: are you in the call?

Ralf Handl (SAP): Postpone ODATA-965

Ralf Handl (SAP): 2.ODATA-981 ETag Header: Clarify meaning of "individual resource".

Ralf Handl (SAP): ODATA-981 is OPEN

Stefan Hagen: @Ralf I follow the trace of the chat and will join the voice line after completion of MQTT call.

Ralf Handl (SAP): @Stefan: thanks!

Mike Pizzo: I think proposal is: Clarify that etags MAY be on collections.  If present on the collection, the service MUST support if-match on get/post; client MUST specify if-match (and can use if-match=* to force operation).

Mike Pizzo: revised:

Mike Pizzo: Clarify that etags MAY be on collections.  If present on the collection, the service MUST support if-match/if-not-match on get, if-match on post; client MUST specify if-match (and can use if-match=* to force operation).

Mike Pizzo: slightly better wording

Mike Pizzo: Clarify that etags MAY be on collections.  If present on the collection, the service MUST support if-match/if-not-match on get, if-match on post; client MUST specify if-match when posting to the collection (i.e., action) (and can use if-match=* to force operation).

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

Martin Zurmuehl (SAP): I second.

Ralf Handl (SAP): ODATA-981 is resolved with the modified proposal

Ralf Handl (SAP): ODATA-984 - Make $-prefix optional for system query options

Mike Pizzo: revised: Make the "$" optional in 4.01.  A 4.01 compliant service MUST support query options both with and without the "$" prefix. Clients that want to work with 4.0 services MUST specify the "$" prefix.

Ralf Handl (SAP): ODATA-984 is OPEN

Martin Zurmuehl (SAP): I move we resolve ODATA-984 as proposed (revised proposal)

Hubert Heijkers: I second

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

Ralf Handl (SAP): ODATA-985 - The HTTP Specification document referenced in the OData

Ralf Handl (SAP): Errata03: reference to RFC2616 already changed, reference to RFC2617 still present, needs to be updated

Martin Zurmuehl (SAP): http://docs.oasis-open.org/odata/odata/v4.0/errata03/odata-v4.0-errata03-part1-protocol-complete.html

Martin Zurmuehl (SAP): http://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part1-protocol.html

Ralf Handl (SAP): References on TC Public Page are outdated, still linking to OS version instead of Errata03

Ralf Handl (SAP): Action Item for Ralf

Ralf Handl (SAP): ODATA-985 is OPEN

Martin Zurmuehl (SAP): Hand signal

Ralf Handl (SAP): Martin volunteers to check RFC7235 for significant changes versus RFC2617

Ralf Handl (SAP): ii.OData CSDL

1.ODATA-879 Support Arrays of Arrays

Ralf Handl (SAP): Alternative:

- similar to TypeDefinition for primitive types add a CollectionTypeDefinition element with an UnderlyingType attribute and a Nullable facet that allows defining a reusable collection type. The underlying type can be any type in scope, including another CollectionTypeDefinition, as long as that doesn't introduce a cycle. If the UnderlyingType is a primitive type, other type-specific facets can be specified.

- JSON representation of a CollectionTypeDefinition instance is an array whose items are representations of instances of the UnderlyingType

- Consider using the shorter name of CollectionType which was used with similar semantics and different syntax in OData V3, https://msdn.microsoft.com/en-us/library/ee781155.aspx

- Consider using the TypeDefinition element for defining both faceted primitive types and collection types

Ralf Handl (SAP): ODATA-879 is OPEN

Ralf Handl (SAP): Mike and Hubert to prepare a proposal

Ralf Handl (SAP): 2.ODATA-929 Nullable facet should default to false for collection types, rather than being unspecified

Ralf Handl (SAP): ODATA-929 is OPEN

Ralf Handl (SAP): Mike and Ralf: even though "false" is the better default for collections, it is odd to have the default dependent on the type

Ralf Handl (SAP): Option 1: leave it as it is in V4

Ralf Handl (SAP): Option 2: recommend that services specify Nullable for collection-valued properties

Ralf Handl (SAP): Option 3: require that services MUST specify Nullable for collection-valued properties

Ralf Handl (SAP): Mike: most people new to OData looking at a collection-valued property interpret Nullable as describing the property, not the items in the collection

Mike Pizzo: alternate proposal: To be compliant, 4.01 Services MUST specify Nullable for collections.  Since this is a new 4.01 requirement, clients SHOULD be prepared for collections that do not specify the value.

Hubert Heijkers: I move to resolve ODATA-929 as per the amended proposal by Mike.

Mark Biamonte (Progress): I second

Ralf Handl (SAP): ODATA-929 is RESOLVED as proposed

Ralf Handl (SAP): 3.ODATA-935 Allow singletons to be members of an entity set

Ralf Handl (SAP): ~/Contoso

Ralf Handl (SAP): Contoso is member of companies

Ralf Handl (SAP): ~/SpecialCompanies/Contoso

Ralf Handl (SAP): This is already legal with V4

Ralf Handl (SAP): ~/Companies/Contoso

Ralf Handl (SAP): ~/ActiveUser as member of Users - illegal in V4

Ralf Handl (SAP): ~/V4/ActiveUser as member of Users - legal in V4

Ralf Handl (SAP): ~/Me/User

Ralf Handl (SAP): ~/Me/Emails

Ralf Handl (SAP): ~/Me/Company

Ralf Handl (SAP): Mike: is used often in existing services and doesn't seem to break anything

Ralf Handl (SAP): Mike: just relax wording on membership and don't extend nav prop binding syntax

Ralf Handl (SAP): Reduce ODATA-935 to membership wording, delegate nav prop binding to ODATA-674

Ralf Handl (SAP): I move to resolve ODATA-935, reduced to the membership wording

Hubert Heijkers: I second

Ralf Handl (SAP): ODATA-935 is RESOLVED

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

Ralf Handl (SAP): 5.ODATA-966 13.4 Add example for navigation property bindings for containment navigation property

Ralf Handl (SAP): ODATA-966 is OPEN

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

Stefan Hagen: skipped ODATA-959 as reported by Hubert, who just left the meeting ...

Ralf Handl (SAP): ODATA-973 is OPEN

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

Stefan Hagen: I second

Ralf Handl (SAP): ODATA-973 is RESOLVED as proposed

Ralf Handl (SAP): iii.OData JSON Format

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

Ralf Handl (SAP): Allow exponential notation for Edm.Decimal literals.

Add new symbolic value Scale="floating" for DECFLOAT values. The Precision attribute will specify the number of digits in the mantissa.

Stefan Hagen: Stefan proposes to update lira ODATA-965 UpdateGeoJSON Reference to RFC7946 after scanning changes vs. document references to indicate readiness.

Ralf Handl (SAP): ODATA-557 is OPEN

Ralf Handl (SAP): Exponential notation in JSON Format:

The ExponentialDecimals=true format parameter indicates that the service MAY serialize Edm.Decimal numbers (including the odata.count, if requested) in exponential notation (e.g. 1e-6 instead of 0.000001).

The sender of a request MUST specify ExponentialDecimals=true in the Content-Type header if the request body contains Edm.Decimal values in exponential notation.

If not specified, or specified as ExponentialDecimals=false, all Edm.Decimal values MUST be serialized in long notation, using only an optional sign, digits, and an optional decimal point followed by digits.

Ralf Handl (SAP): Mike: how about making ExponentialDecimals=true the default?

Ralf Handl (SAP): Mike: need some research into JSON tools how they deal with numbers and exponential notation

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

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

Ralf Handl (SAP): 7.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: Mittwoch, 5. Oktober 2016 14:19
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2016-10-06

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

2. Approve agenda [8:05 am PT]

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

a. Minutes from September 29, 2016 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/59035/latest/odata-meeting-146_on-20160929-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 [8:20 am PT]

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

i. OData Protocol

1. ODATA-965 UpdateGeoJSON Reference to RFC7946

2. ODATA-981 ETag Header: Clarify meaning of "individual resource".

ii. 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)

iii. OData JSON Format

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

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

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

4. ODATA-982 Chapter 11: Annotations on properties in single-property messages

5. ODATA-983 Chapter 15/16: advertise actions on collection-valued properties

iv. Interfaces

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

v. 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-817 Add client-side function odata.matchesRegularExpression

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

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

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

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

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

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

13. ODATA-964 Need to clarify nested delta representation

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

15. ODATA-976 Support partial keys

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

17. ODATA-979 Recursive containment navigation properties and Partner attribute

18. ODATA-980 SchemaVersion header, $SchemaVersion query option, or root URL versioning

6. Next meeting [9:50 am PT]

a. Thursday October 13, 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

odata message