[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Agenda for OData TC meeting on 2019-01-24 - chat transcript
[16:56] anonymous morphed into George Ericson (Dell) [16:56] George Ericson (Dell): Could not get Chrome to allow soaphub... [16:57] George Ericson (Dell): Edge works OK [16:58] Room information was updated by: Ralf Handl (SAP SE) Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday January 24, 2019 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=47970
2.Approve agenda [8:05 am PT]
3.Approve minutes from previous meeting(s) [8:10 am PT]
a.Minutes from January 17, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/64553/Minutes%20of%202019-01-17%20Meeting%20%23243.docx
4.Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php?sort_field=due_closed_date] [8:15am PT]
a.Upcoming
i.#0037 Concept for Google Protocol Buffers as a data format Hubert Heijkers 2019-03-28
b.In progress
i.#0036 Register the OData- headers and preferences with IANA Mark Biamonte 2018-07-26
5.Review TC Timeline for 2019
a.https://www.oasis-open.org/committees/download.php/64563/TC%20Timeline%202019-01-23.docx
6.Issues [8:20 am PT]
a.V4.01: Triage issues:
i.List of issue NEW or OPEN
b.V4.01: NEW or OPEN
i.ODATA-1177 Embed "JSON properties" in OData JSON requests and responses
ii.ODATA-1274 Clarify that a server MUST respond with content-id annotations and MUST include nested entity IDs
iii.ODATA-1272 Highlight implications of derived complex types to their annotations
iv.ODATA-1270 14.4.11: rephrase prose text for dynamic _expression_ Null
v.ODATA-1266 Geo literals with three dimensions
vi.ODATA-1263 Requirement for 204 (No Content) with 11.4.3 "Update an Entity" is not backwards compatible
vii.ODATA-1260 Clarify read-write access via URLs differing from the canonical/read/edit URL
viii.ODATA-1250 GeoJSON, SRID, and LineString
ix.ODATA-1243 Clarify whether $orderby and string comparison with ge, gt, le, lt is language-specific
x.ODATA-1242 Clarify that resolved relative URIs in batch responses cannot contain content-ID references
xi.ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation
xii.ODATA-1165 Describe $expand and $select via prose text and examples, remove ABNF snippets
xiii.ODATA-1267 URL Conventions example in 5.1.1.5.1 has "bad" whitespace
xiv.ODATA-1262 Explicitly state structural restrictions of type Edm.Untyped
xv.ODATA-1261 Allow $pagesize system query option
xvi.ODATA-1259 Clarify @type (@odata.type) and metadata=full
xvii.ODATA-1253 Abstract type definition Core.Number as a super-type of all numeric types
xviii.ODATA-1246 Allow BaseType to be a ComplexType
xix.ODATA-1239 Define a mechanism to distinguish between inserted and updated entities in a Delta Response
xx.ODATA-1238 Clarifications for select-list in ContextUrl
xxi.ODATA-1198 ETag handling deviations from RFC7232 are avoidable if we consider two kinds of ETag (ETag in response header and ETag in response payload)
xxii.ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts
xxiii.ODATA-1135 Document use of JSON $schema
xxiv.ODATA-1064 Add ability to annotate collections to return only count and NextLink
xxv.ODATA-1005 Make sure we have capabilities for all new 4.01 functionality
c.Data Aggregation: NEW or OPEN
i.ODATA-1256 Harmonize usage of custom aggregates with structured aggregatable properties
ii.ODATA-1218 Transformations for recursive hierarchy processing
iii.ODATA-945 Correct examples 53 and 54
d.Vocabularies: NEW or OPEN with concrete proposal
i.ODATA-1176 Capabilities: add new term SelectSupport
ii.ODATA-1099 Add annotations to describe custom query options and custom headers
e.Vocabularies: NEW or OPEN that need more discussion
i.ODATA-1275 Describing and querying "JSON properties"
ii.ODATA-1269 Add QueryRestrictions to the Capabilities Vocabulary
iii.ODATA-1264 CRUD descriptions on entity sets
iv.ODATA-1214 Annotate constructor actions
v.ODATA-1140 ODATA-884 / Add details to HTTPResponseCode term
vi.ODATA-1107 Introduce instance annotation to specify which types an instance "implements"
vii.ODATA-1060 Improve specification of element response requirements
viii.ODATA-884 Enable enumerating the valid requests and responses for a particular resource.
7.Next meetings [9:50 am PT]
a.Thursday January 31, 2019 during 8-10 am PST (17:00-19:00 CET)
b.Thursday February 07, 2019 during 8-10 am PST (17:00-19:00 CET)
8.AOB and wrap up [9:55 am PT]
[2] References
Chat room: http://webconf.soaphub.org/conf/room/odatatc
Conference call & Screen sharing: https://lync.co.sap.com/meet/ralf.handl/Q4QB1098
Conference call details: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/63673/latest/TC%20meeting%20dial-in%20details.htm
[3] Timeline
https://www.oasis-open.org/committees/download.php/64563/TC%20Timeline%202019-01-23.docx
[17:00] Ralf Handl (SAP SE): Voting Members: 3 of 9 (33%) (used for quorum calculation) [17:01] Ralf Handl (SAP SE): Voting Members: 4 of 9 (44%) (used for quorum calculation) [17:05] Ralf Handl (SAP SE): Voting Members: 6 of 9 (66%) (used for quorum calculation) [17:05] Ralf Handl (SAP SE): Quorum achieved: yes [17:06] Ralf Handl (SAP SE): 2.Approve agenda [8:05 am PT] [17:09] Ralf Handl (SAP SE): 6.e.ii ODATA-1269 is already closed - remove from agenda [17:10] Ralf Handl (SAP SE): 6.b.xxii xxiii.ODATA-1135 Document use of JSON $schema [17:10] Ralf Handl (SAP SE): George to check whether this is still necessary [17:11] Ralf Handl (SAP SE): 3.Approve minutes from previous meeting(s) [8:10 am PT] a.Minutes from January 17, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/64553/Minutes%20of%202019-01-17%20Meeting%20%23243.docx
[17:12] Mike Pizzo: Thanks to Ted for doing the minutes last week! [17:12] Ralf Handl (SAP SE): Minutes are approved [17:12] Ralf Handl (SAP SE): 4.Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php?sort_field=due_closed_date] [8:15am PT] [17:12] Ralf Handl (SAP SE): Skip for today [17:12] Ralf Handl (SAP SE): 5.Review TC Timeline for 2019 a.https://www.oasis-open.org/committees/download.php/64563/TC%20Timeline%202019-01-23.docx
[17:19] Ralf Handl (SAP SE): OData Version 4.01: add progressing to Candidate OASIS Standard and finally OASIS Standard [17:21] Ralf Handl (SAP SE): George: consider announcing a "complete set" of documents, e.g. V4.01 plus Vocabs plus OpenAPI Mapping once all of these have progressed sufficiently [17:22] Ralf Handl (SAP SE): Time line is approved [17:22] Ralf Handl (SAP SE): 6.Issues [8:20 am PT] a.V4.01: Triage issues:
i.List of issue NEW or OPEN
[17:24] Ralf Handl (SAP SE): https://issues.oasis-open.org/issues/?jql=project%20%3D%20ODATA%20AND%20fixVersion%20in%20(V4.01_CS02%2C%20V4.0_ERRATA04)%20AND%20component%20in%20(%22ABNF%22%2C%20%22CSDL%20JSON%20%22%2C%20%22CSDL%20XML%22%2C%20%22JSON%20Format%22%2C%20Protocol%2C%20%22URL%20Conventions%22)%20AND%20status%20in%20(Open%2C%20New)%20%20ORDER%20BY%20labels%20ASC%2C%20key%20DESC [17:29] Mark Biamonte (Progress): Sorry I am late. I had a previous meeting that ran long [17:45] Ralf Handl (SAP SE): Triaging done, 20 issues remaining [17:46] Ralf Handl (SAP SE): b.V4.01: NEW or OPEN [17:46] Ralf Handl (SAP SE): i.ODATA-1177 Embed "JSON properties" in OData JSON requests and responses [17:48] Mike Pizzo: Could we use @mediaType instance annotation instead of Core.AcceptableMediaTypes $metadata annotation? [17:50] Mike Pizzo: (actually, existing instance annotation for a stream is @mediaContentType) [17:56] Ralf Handl (SAP SE): {"thisCanBeAnyJSON":{"":"empty key","non-odata key":true}} [18:04] Mike Pizzo: Proposed revision to proposal: "JSON properties" are represented in metadata as properties of type {{Edm.Stream}}, which may be annotated with the existing annotation {{Core.AcceptableMediaTypes}}, listing {{application/json}} to specify that the stream property contains JSON.
Streams that are annotated as the {{application/json}} media type (or one of its subtypes, optionally with format parameters) through @mediaContentType instance annotation are represented as native JSON in JSON requests and responses, they are NOT represented as a base64url-encoded string values. (Note: this is similar to what we do in the [JSON Batch format|http://docs.oasis-open.org/odata/odata-json-format/v4.01/cs01/odata-json-format-v4.01-cs01.html#sec_BatchRequestsandResponses] for JSON request and response bodies.)
"JSON properties" can additionally be annotated with the existing annotation {{Core.AutoExpand}} to indicate that the property will be implicitly expanded by the service if it is contained in a JSON response. The term {{Core.AutoExpand}} is extended to also apply to (stream) properties. Auto-expanded "JSON properties" MAY be part of the default selection, i.e. represented inline if no {{$select}} query option is specified.
[18:11] Ralf Handl (SAP SE): {"thisCanBeAnyJSON":{"":"empty key","non-odata key":true}} [18:13] Ralf Handl (SAP SE): {"thisCanBeAnyJSON":"...","thisCanBeAnyJSON@odata.mediaContentType":"application/json"}} [18:20] Mike Pizzo: Slightly revised: "JSON properties" are represented in metadata as properties of type Edm.Stream, which may be annotated with the existing annotation Core.AcceptableMediaTypes, listing application/json to specify that the stream property contains JSON.
Streams that are annotated as the application/json media type (or one of its subtypes, optionally with format parameters) through @mediaContentType instance annotation are represented as native JSON in JSON requests and responses, they are NOT represented as a base64url-encoded string values. (Note: this is similar to what we do in the JSON Batch format for JSON request and response bodies.)
The term Core.AutoExpand is extended to also apply to (stream) properties, enabling "JSON properties" to be implicitly expanded by the service if it is contained in a JSON response. Auto-expanded "JSON properties" MAY be part of the default selection, i.e. represented inline if no $select query option is specified.
[18:29] Ralf Handl (SAP SE): I move to resolve ODATA-1177 with the amended proposal [18:29] Hubert Heijkers (IBM): I second [18:30] Ralf Handl (SAP SE): ODATA-1177 is resolved with the amended proposal [18:31] Ralf Handl (SAP SE): ii.ODATA-1274 Clarify that a server MUST respond with content-id annotations and MUST include nested entity IDs [18:31] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1274 [18:37] Matt Borges (SAP): Clarify that the server MUST return content-ids in deep insert/deep update responses if it says it supports it. Clarify that the response must include the entity ID (or all key properties if conventional IDs are used) for all entities returned in the response for a create or update.
[18:42] Matt Borges (SAP): <ComplexType Name="DeepInsertSupportType"> <Property Name="Supported" Type="Edm.Boolean" Nullable="false" DefaultValue="true">
<Annotation Term="Core.Description" String="Annotation target supports deep inserts" />
</Property>
<Property Name="ContentIDSupported" Type="Edm.Boolean" Nullable="false" DefaultValue="true">
<Annotation Term="Core.Description"
String="Annotation target supports accepting and returning nested entities annotated with the `Core.ContentID` instance annotation." />
</Property>
</ComplexType>
[18:45] Ralf Handl (SAP SE): ODATA-1274 is OPEN [18:46] Mike Pizzo: How about wording such as: "Clients MAY associate an id with individual nested entities in the request by using the Core.ContentID term defined in [OData-VocCore]. Services that respond with 201 Created SHOULD annotate the entities in the response using the same Core.ContentID value as specified in the request. Services SHOULD advertise support for deep inserts through the Capabilities.DeepInsertSupport term, defined in [OData-VocCap]; services that advertise support through Capabilities.DeepInsertSupport MUST return the Core.ContentID for the inserted or updated entities."
[18:47] Matt Borges (SAP): Clarify that the response must include the entity ID (or all key properties if conventional IDs are used) for all entities returned in the response for a create or update. [18:48] Matt Borges (SAP): I move to resolve OData-1274 with the amended proposal [18:48] Hubert Heijkers (IBM): I second [18:48] Ralf Handl (SAP SE): ODATA-1274 is RESOLVED with the above proposal [18:49] Ralf Handl (SAP SE): iii.ODATA-1272 Highlight implications of derived complex types to their annotations [18:49] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1272 [18:50] Mike Pizzo: I move we resolved ODATA_1272 as proposed. [18:50] Ralf Handl (SAP SE): ODATA-1272 is OPEN [18:50] Hubert Heijkers (IBM): I second [18:50] Ralf Handl (SAP SE): ODATA-1272 is RESOLVED as proposed [18:51] Mike Pizzo: I lost connection; trying to reconnect. [18:51] Ralf Handl (SAP SE): iv.ODATA-1270 14.4.11: rephrase prose text for dynamic _expression_ Null [18:52] Ralf Handl (SAP SE): ODATA-1270 is OPEN [18:52] Hubert Heijkers (IBM): I move to resolve ODATA-1270 as proposed. [18:53] Mark Biamonte (Progress): I second [18:53] Ramesh Reddy (RedHat)2: I second [18:53] Ralf Handl (SAP SE): ODATA-1270 is RESOLVED as proposed [18:53] Ralf Handl (SAP SE): v.ODATA-1266 Geo literals with three dimensions [18:56] Ralf Handl (SAP SE): ODATA-1266 is OPEN [18:56] Hubert Heijkers (IBM): I move to resolve ODATA-1266 as proposed! [18:56] Mark Biamonte (Progress): i second [18:57] Ralf Handl (SAP SE): ODATA-1266 is RESOLVED as proposed [18:57] Ralf Handl (SAP SE): 7.Next meetings [9:50 am PT] a.Thursday January 31, 2019 during 8-10 am PST (17:00-19:00 CET)
b.Thursday February 07, 2019 during 8-10 am PST (17:00-19:00 CET)
[18:58] Ralf Handl (SAP SE): 8.AOB and wrap up [9:55 am PT] [18:58] Ralf Handl (SAP SE): Meeting is adjourned From: odata@lists.oasis-open.org <odata@lists.oasis-open.org>
On Behalf Of Handl, Ralf Here [1] is a draft agenda for the OData TC (Technical Committee) meeting
scheduled on
Thursday January 24, 2019 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]
2.
Approve agenda [8:05 am PT]
3.
Approve minutes from previous meeting(s) [8:10 am PT]
4.
Review action items [Action item list:
https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php?sort_field=due_closed_date] [8:15am PT]
i. #0037
Concept for Google Protocol Buffers as a data format – Hubert Heijkers – 2019-03-28
i. #0036
Register the OData- headers and preferences with IANA – Mark Biamonte – 2018-07-26
5.
Review TC Timeline for 2019
6.
Issues [8:20 am PT]
i. List of issue
NEW or OPEN
i. ODATA-1177
Embed "JSON properties" in OData JSON requests and responses
ii. ODATA-1274
Clarify that a server MUST respond with content-id annotations and MUST include nested entity IDs
iii. ODATA-1272
Highlight implications of derived complex types to their annotations
iv. ODATA-1270
14.4.11: rephrase prose text for dynamic _expression_ Null
v. ODATA-1266
Geo literals with three dimensions
vi. ODATA-1263
Requirement for 204 (No Content) with 11.4.3 "Update an Entity" is not backwards compatible
vii. ODATA-1260
Clarify read-write access via URLs differing from the canonical/read/edit URL
viii. ODATA-1250
GeoJSON, SRID, and LineString
ix. ODATA-1243
Clarify whether $orderby and string comparison with ge, gt, le, lt is language-specific
x. ODATA-1242
Clarify that resolved relative URIs in batch responses cannot contain content-ID references
xi. ODATA-1226
Ambiguity with Capabilities.ChangeTracking annotation
xii. ODATA-1165
Describe $expand and $select via prose text and examples, remove ABNF snippets
xiii. ODATA-1267
URL Conventions example in 5.1.1.5.1 has "bad" whitespace
xiv. ODATA-1262
Explicitly state structural restrictions of type Edm.Untyped
xv. ODATA-1261
Allow $pagesize system query option
xvi. ODATA-1259
Clarify @type (@odata.type) and metadata=full
xvii. ODATA-1253
Abstract type definition Core.Number as a super-type of all numeric types
xviii. ODATA-1246
Allow BaseType to be a ComplexType
xix. ODATA-1239
Define a mechanism to distinguish between inserted and updated entities in a Delta Response
xx. ODATA-1238
Clarifications for select-list in ContextUrl
xxi. ODATA-1198
ETag handling deviations from RFC7232 are avoidable if we consider two kinds of ETag (ETag in response header and ETag in response payload)
xxii. ODATA-1168
Clarify the use of ETags for Avoiding Update Conflicts
xxiii. ODATA-1135
Document use of JSON $schema
xxiv. ODATA-1064
Add ability to annotate collections to return only count and NextLink
xxv. ODATA-1005
Make sure we have capabilities for all new 4.01 functionality
i. ODATA-1256
Harmonize usage of custom aggregates with structured aggregatable properties
ii. ODATA-1218
Transformations for recursive hierarchy processing
iii. ODATA-945
Correct examples 53 and 54
i. ODATA-1176
Capabilities: add new term SelectSupport
ii. ODATA-1099
Add annotations to describe custom query options and custom headers
i. ODATA-1275
Describing and querying "JSON properties"
ii. ODATA-1269
Add QueryRestrictions to the Capabilities Vocabulary
iii. ODATA-1264
CRUD descriptions on entity sets
iv. ODATA-1214
Annotate constructor actions
v. ODATA-1140
ODATA-884 / Add details to HTTPResponseCode term
vi. ODATA-1107
Introduce instance annotation to specify which types an instance "implements"
vii. ODATA-1060
Improve specification of element response requirements
viii. ODATA-884
Enable enumerating the valid requests and responses for a particular resource.
7.
Next meetings [9:50 am PT]
8.
AOB and wrap up [9:55 am PT] [2]
References
[3]
Timeline |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]