[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Agenda for OData TC meeting 2016-04-07 - chat transcript
[16: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
[16: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
[16:49] Stefan: Info: Voting Members: 2 of 13 (15%) (used for quorum calculation) 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
[17:00] anonymous1 morphed into Mark Biamonte (Progress) [17:03] Ralf Handl (SAP): Voting Members: 7 of 13 (53%) (used for quorum calculation) [17:03] Ralf Handl (SAP): Quorum achieved [17:03] anonymous morphed into Martin Z. SAP SE [17:15] Ralf Handl (SAP): https://issues.oasis-open.org/browse/ODATA-925 [17: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.
[17:20] Ram (Microsoft): ODATA-925: Define Core term for service/schema/model version [17:20] Ram (Microsoft): Issue open, no objections [17:20] Ralf Handl (SAP): I move to resolve ODATA-925 as proposed [17:20] Martin Z. SAP SE: I second [17:23] Ram (Microsoft): No objections, motion passes, ODATA-925 [17:27] Ram (Microsoft): Side discussion on OData / Open API alignment [17: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. [17:29] Ram (Microsoft): On the OASIS open repo work relating to OData/Open API alignment, here are some work items we are contemplating: [17:32] Ralf Handl (SAP): Open Repo for OpenAPI [17:32] Ralf Handl (SAP): - XSLT transformation [17:32] Ralf Handl (SAP): - example XML files [17:33] Ralf Handl (SAP): - example openapi.json files [17:33] Ralf Handl (SAP): - preferably example files for the live odata.org services [17:34] Ralf Handl (SAP): Open Repo for Vocabularies [17:34] Ralf Handl (SAP): - read-only copies of OASIS vocabs [17:34] Ralf Handl (SAP): - Validation vocab with the intention of evolving it there [17:36] Ralf Handl (SAP): XSL transformation from XML to OpenAPI.json [17:38] Ralf Handl (SAP): https://issues.oasis-open.org/browse/ODATA-910 [17: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
[17:38] Ram (Microsoft): back to issues [17:38] Ram (Microsoft): ODATA-910: Consider format that is tailored for programmatic access (public comment c201602e00002) [17:44] Ralf Handl (SAP): Amendment to proposal: use "type" name/value pair for both entity sets and singletons [17:45] Ralf Handl (SAP): I move to resolve ODATA-910 with the amended proposal [17:45] Hubert Heijkers: I second [17:46] Ralf Handl (SAP): https://issues.oasis-open.org/browse/ODATA-906 [17:46] Ram (Microsoft): No objections to the ODATA-910 motion, motion passes. [17:47] Ram (Microsoft): ODATA-906 Consider how to specify an included namespace as a default in JSON CSDL [17: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
}
},
[17:58] Ralf Handl (SAP): I move to reopen ODATA-812 [17:58] Martin Z. SAP SE: i second [17:59] Ralf Handl (SAP): ODATA-812 is reopened [17:59] Ram (Microsoft): We will discuss ODATA-812 at the next meeting [18:00] Ralf Handl (SAP): https://issues.oasis-open.org/browse/ODATA-890 [18:01] Ram (Microsoft): ODATA-910 has been parked for discussion in light of ODATA-812. [18:01] Ram (Microsoft): ODATA-890 Specify how to get from a JSON message to a JSON schema for validating this message [18:03] Ram (Microsoft): We will discuss this later, needs more thought and consideration [18:03] Ram (Microsoft): ODATA-863 Represent Terms similar to Types [18:04] Ram (Microsoft): This depends on ODATA-618. We need to consider this more before we can resolve. [18:06] Ram (Microsoft): Preferred name for OData JSON CSDL is "ODATA CSDL JSON". No objections. [18:07] Ram (Microsoft): Editors will change the name, [18:14] Ram (Microsoft): The above discussed issues are in section 6 ODATA JSON CSDL. [18:14] Ralf Handl (SAP): Mike: can we $ref from the document with "definitions" to a separate file with "paths"? [18:15] Ram (Microsoft): Ralf to research this and report back. [18:16] Ralf Handl (SAP): Ralf to send links to Swagger UI referencing our example files [18:22] Ram (Microsoft): The minutes from the previous meeting has been approved. No corrections. No objections. [18:22] Ram (Microsoft): Action items: Both actions are still open. [18:22] Ram (Microsoft): Meeting adjourned. [18: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 Michael Pizzo As I recall from the call last week, the main topic for today was to go over Ralph's JSON CSDL issues. I don't know that we were planning on taking the full 2 hours. In any case, I am planning on calling in from my car for part of the call, but not all of it. Also, any update on requests for quotes for the ISO approval?
-Mike From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org]
On Behalf Of Ram Jeyaraman 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
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)
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
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
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
b.
Thursday April 14, 2016?
[2] References
[3] Timeline |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]