RE: [odata] Agenda for OData TC meeting on 2017-03-02 - chat transcript

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

[16:49] Stefan Hagen: RegInfo{Voting Members: 1 of 11 (9%) (used for quorum calculation)}

 

[17:02] Martin Zurmuehl (SAP SE): ....Voting Members: 4 of 11 (36%) (used for quorum calculation)

 

[17:03] Ralf Handl (SAP SE): Weekly meeting of the OData TC.

Dial-in information: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/56760/latest 

Online chat room: http://webconf.soaphub.org/conf/room/odatatc

Screen sharing: https://sap.emea.pgiconnect.com/OData-TC/

 

[17:03] Stefan Hagen: RegInfo{Voting Members: 5 of 11 (45%) (used for quorum calculation) }

[17:05] Stefan Hagen: Still unchanged ...

 

[17:06] anonymous morphed into Matt Borges (SAP)

 

[17:07] Stefan Hagen: Voting Members: 6 of 11 (54%) (used for quorum calculation)

[17:07] Stefan Hagen: Quorate I guess

 

[17:07] Ralf Handl (SAP SE): No guess, fact 

 

[17:07] Stefan Hagen: It is to the chair to state so 

[17:07] Stefan Hagen: calling in ... or letting call out now

 

[17:08] Ralf Handl (SAP SE): Voting Members: 7 of 11 (63%) (used for quorum calculation)

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

[17:09] Ralf Handl (SAP SE): Additional item: update on timeline

[17:09] Ralf Handl (SAP SE): Additional issue: ODATA-1043 - Clean up context URL syntax

[17:09] Ralf Handl (SAP SE): Agenda approved with these additions

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

a.Minutes from February 23, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/60135/odata-meeting-163_on-20170223-minutes.html

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

[17:10] Ralf Handl (SAP SE): 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

[17:10] Ralf Handl (SAP SE): 4.5 Timeline

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

a.CSDL XML improved document structure: use same representation-neutral normative text as in CSDL JSON and distinguish representation-specific text with special paragraph formats

i.Walkthrough: https://www.oasis-open.org/committees/download.php/60167/odata-csdl-xml-v4.01-wd02-2017-03-01.docx

[17:36] Ralf Handl (SAP SE): ii.Decide whether to retire Part 3: CSDL as its text is now completely contained in both CSDL JSON Representation and CSDL XML Representation

 

[17:38] Stefan Hagen: I move to retire Part 3: CSDL as its text is now completely contained in both CSDL JSON Representation and CSDL XML Representation

 

[17:38] Matt Borges (SAP): I second

 

[17:38] Ralf Handl (SAP SE): Motion passes

[17:39] Ralf Handl (SAP SE): Ralf to get into contact with Chet Ensign on how to do this, especially on what happens with the stable, revision-independent URL to Part 3

[17:41] Ralf Handl (SAP SE): Make clear that we moved all content to CSDL XML Representation, and that this new document replaces and supercedes the previous Part 3, and that Core is now a two-part work product

[17:42] Ralf Handl (SAP SE): b.Issues for CSDL JSON Representation in New or Open state

i.ODATA-1042 Cast annotation _expression_ and Unicode facet

[17:42] Ralf Handl (SAP SE): Casting ASCII to Unicode always succeeds. 

Casting Unicode to ASCII only succeeds for string values with characters limited to the ASCII character set.

[17:47] Ralf Handl (SAP SE): <Annotation Term="Some.Thing">

        <Cast Type="Edm.Decimal" Scale="3">

          <Decimal>3.14</Decimal>

        </Cast>

      </Annotation>

 

[17:48] Mike Pizzo: castExpr = 'cast' OPEN BWS [ commonExpr BWS COMMA BWS ] qualifiedTypeName BWS CLOSE

cast _expression_: castExpr = 'cast' OPEN BWS [ commonExpr BWS COMMA BWS ] qualifiedTypeName BWS CLOSE

 

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

 

[17:50] Mike Pizzo: I move we approve ODATA-1042 as proposed.

 

[17:50] Ramesh Reddy (Red Hat): I second

 

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

[17:51] Ralf Handl (SAP SE): 6.V4.01 [9:20 am PT]

a.Issues for V4.01_CSD02 ready for resolution

i.ODATA-1039 Relax constraints on namespace names

[17:52] Ralf Handl (SAP SE): Currently a namespace has to consist of several dot-separated segments, and each segment has to be a SimpleIdentifier (essentially a JavaScipt/Java/Swift/C# variable name). 

We could relax this and allow - at least for the second, third, ... segment, additional characters, most prominently the dash (-), and allow to have purely numeric segments, e.g. Some.Namespace.3.1.4 to allow for semantic versioning of namespaces.

[17:52] Ralf Handl (SAP SE): - Allow purely numeric segments after the first segment. First segment still needs to start with with a letter 

- Allow dash in all segments (except as first character in first segment)

[17:55] Ralf Handl (SAP SE): ODATA-1039 is OPEN

[17:55] Ralf Handl (SAP SE): Investigate programming language rules and client implementations

[17:56] Ralf Handl (SAP SE): - Mike: C# and Microsoft clients

[17:56] Ralf Handl (SAP SE): - Ramesh: Java and Olingo

[17:56] Ralf Handl (SAP SE): - Matt: C++

[17:56] Ralf Handl (SAP SE): - Matt: Swift

[17:57] Ralf Handl (SAP SE): ODATA-1043 - Clean up context URL syntax

[17:57] Ralf Handl (SAP SE): 1) Chapter 10 states: The context URL describes the content of the payload. It consists of the canonical metadata document URL and a fragment *identifying the relevant portion of the metadata document.* 

This is somewhat violated by context urls using the template variable {entity} whose value is the canonical URL of an entity, including its key values - the key values aren't needed to identify the relevant portion of the metadata document, for this purpose the type is sufficient. 

2) Chapter 10 states: Request payloads generally do not require context URLs as the type of the payload can generally be determined from the request URL. 

Can we have the same for response payloads? Most responses for requests to entity sets or singletons using canonical URLs would not need a context URL, same for navigation paths with a navigation property binding. Instances with a type derived from the declared type carry the @odata.type annotation, so even those don't need a context URL. Same for responses to actions/functions with an EntitySetPath, or action/function imports with a an EntitySet.

[17:59] Ralf Handl (SAP SE): Mike: Context URL is also used as base for relative URLs, requiring the key values to keep the relative URLs short

[17:59] Ralf Handl (SAP SE): Mainly for Containment

[18:02] Ralf Handl (SAP SE): For non-containment helpful to keep navigation URLs short - but only if the entity uses canonical URL, and the navigation property segment is non-canonical

[18:04] Ralf Handl (SAP SE): Mike: this would be a 4.01 feature only

[18:04] Ralf Handl (SAP SE): Mike: look into client libraries

[18:06] Ralf Handl (SAP SE): ODATA-1043 is OPEN

[18:07] Ralf Handl (SAP SE): Mike: .NET libraries

[18:08] Ralf Handl (SAP SE): Ramesh: Olingo Client

[18:08] Ralf Handl (SAP SE): Matt: talk to Evan about XScript library

[18:09] Ralf Handl (SAP SE): b.Issues for V4.01_CSD02 in New or Open state without concrete proposal

[18:12] Ralf Handl (SAP SE): Stefan: move ODATA-1011 (Security) and ODATA-962 (CORS) to "Securing OData" committee note

[18:18] Ralf Handl (SAP SE): ODATA-760: Vocabularies have own publication cycle

 

[18:20] Mike Pizzo: I move we defer ODATA-854 to 4.02.

 

[18:20] Martin Zurmuehl (SAP SE): i second

 

[18:20] Ralf Handl (SAP SE): ODATA-854 has been defered to V4.02

 

[18:26] Mike Pizzo: I move we assign ODATA-962 as a committee note and change the milestone to CN1.

 

[18:26] Martin Zurmuehl (SAP SE): I second

 

[18:26] Ralf Handl (SAP SE): No objections, motion passes

 

[18:32] Stefan Hagen: I move to assign the ODATA-1011 to the Securing OData Committee Note

 

[18:33] Mike Pizzo: I second

 

[18:33] Ralf Handl (SAP SE): No objections, motion passes

 

[18:42] Mike Pizzo: I propose we resolve ODATA-1032 with the updated proposal: Accept the IEEE754 rules for INF, -INF, as described below, as well as the IEEE754 rules for NaaN (unordered and not equal to anything)

 

[18:42] Ralf Handl (SAP SE): ODATA-1032 is OPEN

 

[18:42] Martin Zurmuehl (SAP SE): I second

 

[18:42] Ralf Handl (SAP SE): ODATA-1032 is RESOLVED as proposed

[18:45] Ralf Handl (SAP SE): ODATA-1033

[18:45] Ralf Handl (SAP SE): We allow parameter aliases for key values, so these values can be deferred to the query part of the URL

[18:45] Ralf Handl (SAP SE): keyValuePair     = ( primitiveKeyProperty / keyPropertyAlias  ) EQ ( parameterAlias / keyPropertyValue )

[18:46] Ralf Handl (SAP SE): ODATA-1033 is OPEN

[18:48] Ralf Handl (SAP SE): ODATA-1034 is OPEN

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

a.Thursday March 09, 2017 during 8-10 am PST

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

[18:51] Ralf Handl (SAP SE): No other business, meeting is adjourned

 

 

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Mittwoch, 1. März 2017 14:19
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2017-03-02

 

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

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

 

2.        Approve agenda [8:05 am PT]

 

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

a.     Minutes from February 23, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/60135/odata-meeting-163_on-20170223-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.        CSDL [8:20 am PT]

a.     CSDL XML improved document structure: use same representation-neutral normative text as in CSDL JSON and distinguish representation-specific text with special paragraph formats

                                  i.    Walkthrough: https://www.oasis-open.org/committees/download.php/60167/odata-csdl-xml-v4.01-wd02-2017-03-01.docx

                                 ii.    Decide whether to retire Part 3: CSDL as its text is now completely contained in both CSDL JSON Representation and CSDL XML Representation

b.     Issues for CSDL JSON Representation in New or Open state

                                  i.    ODATA-1042 Cast annotation _expression_ and Unicode facet

 

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

a.     Issues for V4.01_CSD02 ready for resolution

                                  i.    ODATA-1039 Relax constraints on namespace names

                                 ii.    ODATA-1042 Cast annotation _expression_ and Unicode facet

b.    Issues for V4.01_CSD02 in New or Open state without concrete proposal

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

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

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

                                iv.    ODATA-879 Support Arrays of Arrays

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

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

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

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

                                ix.    ODATA-962 CORS Support

                                 x.    ODATA-994 consider replacing SchemaVersion header with $SchemaVersion query option, or root URL versioning

                                xi.    ODATA-1002 Add build in functions operating on collections of primitive (and complex?) types

                               xii.    ODATA-1003 Allow casting of entities and complex type instances to arbitrary structural type

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

                              xiv.    ODATA-1011 Security experts at RSA suggest adding guidance on the use of OAuth and openID

                               xv.    ODATA-1018 Allow $expand and $select with modifying requests that return a collection in combination with return=representation to specify the response shape

                              xvi.    ODATA-1020 Remove / in reference in instance annotation in filter and orderby _expression_

                             xvii.    ODATA-1021 Are additional values needed for the reason property of a removed Annotation

                            xviii.    ODATA-1032 Define comparison for numeric value exceptions

                              xix.    ODATA-1033 Interoperability issue when using escaped slash/backslash in URLs

                               xx.    ODATA-1034 Support the notion of a collection of name/value pairs where the type of the value is known

 

7.        Next meeting [9:50 am PT]

a.     Thursday March 09, 2017 during 8-10 am PST

 

8.        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/download.php/59862/TC%20Timeline-2017-01-25.docx