RE: Agenda for OData TC meeting 2016-04-07

[Ram Jeyaraman <Ram.Jeyaraman@microsoft.com>]

[7:47] Room information was updated by: Stefan

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

You may find agenda draft sent via email by Ram at ttps://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201604/msg00010.html

[7:48] Room information was updated by: Stefan

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

You may find agenda draft sent via email by Ram at https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201604/msg00010.html

 

[7:49] Stefan: Info: Voting Members: 2 of 13 (15%) (used for quorum calculation)

 

[8:00] anonymous1 morphed into Mark Biamonte (Progress)

 

[8:03] Ralf Handl (SAP): Voting Members: 7 of 13 (53%) (used for quorum calculation)

[8:03] Ralf Handl (SAP): Quorum achieved

 

[8:03] anonymous morphed into Martin Z. SAP SE

 

[8:15] Ralf Handl (SAP): https://issues.oasis-open.org/browse/ODATA-925

[8:16] Ralf Handl (SAP): Add a Core term for a service/schema/model version. 

    <Term Name="SchemaVersion" Type="String" AppliesTo="Schema"> 

        <Annotation Term="Core.Description" String="Version of the schema (not to be confused with the protocol version)" /> 

    </Term> 

Clarify relationship between version and metadataEtag: first is semantic, second could be technically derived (timestamp of development artifacts), so the latter may change without the former changing, but if the former changes, the latter SHOULD/MUST change.

 

[8:20] Ram (Microsoft): ODATA-925: Define Core term for service/schema/model version

[8:20] Ram (Microsoft): Issue open, no objections

 

[8:20] Ralf Handl (SAP): I move to resolve ODATA-925 as proposed

 

[8:20] Martin Z. SAP SE: I second

 

[8:23] Ram (Microsoft): No objections, motion passes, ODATA-925

[8:27] Ram (Microsoft): Side discussion on OData / Open API alignment

[8:28] Ram (Microsoft): The plan is to advance OData JSON CSDL to CSD02 (align with Swagger 2.0 spec) and then to CSD03 (align with Swagger/Open API 3.0), and then Committee Specification.

[8:29] Ram (Microsoft): On the OASIS open repo work relating to OData/Open API alignment, here are some work items we are contemplating:

 

[8:32] Ralf Handl (SAP): Open Repo for OpenAPI

[8:32] Ralf Handl (SAP): - XSLT transformation

[8:32] Ralf Handl (SAP): - example XML files

[8:33] Ralf Handl (SAP): - example openapi.json files

[8:33] Ralf Handl (SAP): - preferably example files for the live odata.org services

[8:34] Ralf Handl (SAP): Open Repo for Vocabularies

[8:34] Ralf Handl (SAP): - read-only copies of OASIS vocabs

[8:34] Ralf Handl (SAP): - Validation vocab with the intention of evolving it there

[8:36] Ralf Handl (SAP): XSL transformation from XML to OpenAPI.json

[8:38] Ralf Handl (SAP): https://issues.oasis-open.org/browse/ODATA-910

[8:38] Ralf Handl (SAP): Inheritance: add "x-baseType" extension keyword in addition to "allOf" keyword. 

4.1.3 Enumeration Types: OpenAPI specification doesn't support "anyOf" keyword, so enumeration types are represented just as string enums without the ambiguous "pattern".

4.3 Entity Container: use "resources" name/value pair whose value is an object with one name/value pair per entity container child. Add name/value pair "kind" to the object describing the container child 

EntitySet/@EntityType and Singleton/@Type: since we introduce keyless entity types for singletons we won't use complex types for singletons, so the JSON format can use the same keyword "entityType" for both resource kinds

 

[8:38] Ram (Microsoft): back to issues

[8:38] Ram (Microsoft): ODATA-910: Consider format that is tailored for programmatic access (public comment c201602e00002)

 

[8:44] Ralf Handl (SAP): Amendment to proposal: use "type" name/value pair for both entity sets and singletons

[8:45] Ralf Handl (SAP): I move to resolve ODATA-910 with the amended proposal

 

[8:45] Hubert Heijkers: I second

 

[8:46] Ralf Handl (SAP): https://issues.oasis-open.org/browse/ODATA-906

 

[8:46] Ram (Microsoft): No objections to the ODATA-910 motion, motion passes.

[8:47] Ram (Microsoft): ODATA-906 Consider how to specify an included namespace as a default in JSON CSDL

 

[8:47] Ralf Handl (SAP): Both document-defined and included namespaces are represented as properties of the /x-schemas object. The Core.DefaultNamespace annotation will in both cases be represented as a name/value pair within the object describing the namespace, e.g. 

    "x-schemas": { 

        "Org.OData.Core.V1": { 

            "uri": "http://localhost/examples/Org.OData.Core.V1.openapi.json", 

            "@Core.DefaultNamespace": true 

        }, 

        "Core": { 

            "aliasFor": "Org.OData.Core.V1" 

        }, 

        "Org.OData.Measures.V1": { 

            "uri": "http://localhost/examples/Org.OData.Measures.V1.openapi.json" 

        }, 

        "UoM": { 

            "aliasFor": "Org.OData.Measures.V1" 

        }, 

        "ODataDemo": { 

            "@Core.DefaultNamespace": true 

        } 

    },

[8:58] Ralf Handl (SAP): I move to reopen ODATA-812

 

[8:58] Martin Z. SAP SE: i second

 

[8:59] Ralf Handl (SAP): ODATA-812 is reopened

 

[8:59] Ram (Microsoft): We will discuss ODATA-812 at the next meeting

 

[9:00] Ralf Handl (SAP): https://issues.oasis-open.org/browse/ODATA-890

 

[9:01] Ram (Microsoft): ODATA-910 has been parked for discussion in light of ODATA-812.

[9:01] Ram (Microsoft): ODATA-890 Specify how to get from a JSON message to a JSON schema for validating this message

[9:03] Ram (Microsoft): We will discuss this later, needs more thought and consideration

[9:03] Ram (Microsoft): ODATA-863 Represent Terms similar to Types

[9:04] Ram (Microsoft): This depends on ODATA-618. We need to consider this more before we can resolve.

[9:06] Ram (Microsoft): Preferred name for OData JSON CSDL is "ODATA CSDL JSON". No objections.

[9:07] Ram (Microsoft): Editors will change the name,

[9:14] Ram (Microsoft): The above discussed issues are in section 6 ODATA JSON CSDL.

 

[9:14] Ralf Handl (SAP): Mike: can we $ref from the document with "definitions" to a separate file with "paths"?

 

[9:15] Ram (Microsoft): Ralf to research this and report back.

 

[9:16] Ralf Handl (SAP): Ralf to send links to Swagger UI referencing our example files

 

[9:22] Ram (Microsoft): The minutes from the previous meeting has been approved. No corrections. No objections.

[9:22] Ram (Microsoft): Action items: Both actions are still open.

[9:22] Ram (Microsoft): Meeting adjourned.

 

Room Information:

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

You may find agenda draft sent via email by Ram at https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201604/msg00010.html

 

[9:25] Ram (Microsoft)1: Next meeting: Next week same time

 

 

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Ram Jeyaraman
Sent: April 6, 2016 4:00 PM
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting 2016-04-07

 

Here [1] is the agenda for the OData TC (Technical Committee) meeting scheduled on Thursday April 7, 2016 during 8-10am Pacific Time. 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]
   1. Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41457  

 

2. Approve agenda [8:05am]

 

3. Approve minutes from previous meeting(s) [8:10am]
   1. Minutes from March 31, 2016 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57850/odata-meeting-126_on-20160331-minutes.html  

 

4. Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am]
   1. Action items due

                                                    i.     #0032: Overview presentation on HTTP/2 features (due May 19, 2016)

                                                   ii.     #0035: Identify the right open source license for the OASIS Open Source repositories for vocabularies and libraries (due March 31, 2016)

 

5. V4.01 issues [8:20am]

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

                                                     i.          OData protocol

1.      ODATA-920 Specify overflow for int data types

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

3.      ODATA-918 Add operator "divideby" that always results in a decimal.

4.      ODATA-921: Specify operations for keyless nav props

5.      ODATA-928: Allow client to use OData-SchemaVersion header to indicate the metadata version it is using

                                                   ii.           Simplified Payload

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

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

3.      ODATA-747Allow IEEE 754 constants [-]INF and NaN also for Edm.Decimal and integer types

                                                  iii.           New Query Capabilities

1.      ODATA-614 Allow $expand, $select, ... with POST/PATCH/PUT in combination with return=representation to specify the response shape

2.      ODATA-827 introduce $compute query option

                                                  iv.           Enumerations

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

2.      ODATA-494 Define inheritance for enumeration types

3.      ODATA-874 Allow Edm.String as underlying type for enumeration types

                                                   v.          OData CSDL

1.      ODATA-923: $expand for $metadata to include referenced schemas

6.      OData JSON CSDL [9:20am]

a.      New issues

                                                    i.     ODATA-925: Define Core term for service/schema/model version

b.      Parked issues

                                                    i.     ODATA-910: Consider format that is tailored for programmatic access (public comment c201602e00002)

                                                   ii.     ODATA-906 Consider how to specify an included namespace as a default in JSON CSDL

                                                  iii.     ODATA-890 Specify how to get from a JSON message to a JSON schema for validating this message

                                                  iv.     ODATA-863 Represent Terms similar to Types

c.      Next steps

                                                    i.     Discuss next steps for alignment with Swagger JSON schema

7. Data aggregation [9:30am]

a.      Hierarchy discussion

b.      Issues

                                               i.          ODATA-905 Example 67: result row for USA, Sugar missing, Example 68: last total should be 7

                                              ii.          ODATA-904 Example 55: clarify groupby in combination with relationships of instance cardinality zero

                                             iii.          ODATA-909 ABNF for pathPrefix should also allow qualified ComplexTypeName

8. Next meeting [9:50am]

b.      Thursday April 14, 2016?

 

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

 

[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