[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Agenda for OData TC meeting on 2019-01-31 - chat transcript
[16:41] 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 31, 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=47971
2.Approve agenda [8:05 am PT]
3.Approve minutes from previous meeting(s) [8:10 am PT]
a.Minutes from January 24, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/64630/Minutes%20of%202019-01-24%20Meeting%20%23244.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.Issues [8:20 am PT]
a.APPLIED
i.ODATA-1188 Allow using instance annotations in $select and $expand left-over
1.https://github.com/oasis-tcs/odata-abnf/pull/15
ii.ODATA-1221 Apply, as much as possible, our JSON Format to our annotations as well
1.https://github.com/oasis-tcs/odata-csdl-schemas/pull/6
2.https://github.com/oasis-tcs/odata-vocabularies/pull/34
b.V4.01: NEW or OPEN
i.ODATA-1278 Deleted Entity: @odata.removed possible in addition to @removed?
ii.ODATA-1277 null and empty paths in Annotation Path, Property Path, Navigation Property Path
iii.ODATA-1276 Explicitly allow the minus sign / dash in a search term
iv.ODATA-1263 Requirement for 204 (No Content) with 11.4.3 "Update an Entity" is not backwards compatible
v.ODATA-1260 Clarify read-write access via URLs differing from the canonical/read/edit URL
vi.ODATA-1259 Clarify @type (@odata.type) and metadata=full
vii.ODATA-1250 GeoJSON, SRID, and LineString
viii.ODATA-1243 Clarify whether $orderby and string comparison with ge, gt, le, lt is language-specific
ix.ODATA-1242 Clarify that resolved relative URIs in batch responses cannot contain content-ID references
x.ODATA-1238 Clarifications for select-list in ContextUrl
xi.ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts
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-1226 Ambiguity with Capabilities.ChangeTracking annotation
xv.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)
xvi.ODATA-1064 Add ability to annotate collections to return only count and NextLink
xvii.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-1273 Define mapping of permission scopes to resources
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.
6.Next meetings [9:50 am PT]
a.Thursday Febuary 07, 2019 during 8-10 am PST (17:00-19:00 CET)
b.Thursday Febuary 14, 2019 during 8-10 am PST (17:00-19:00 CET)
7.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] Mark Biamonte (Progress): My previous meeting is running long. I will likely be late in joining [17:02] Ralf Handl (SAP SE): Voting Members: 4 of 9 (44%) (used for quorum calculation) [17:04] Ralf Handl (SAP SE): Voting Members: 7 of 9 (77%) (used for quorum calculation) [17:04] Ralf Handl (SAP SE): 2.Approve agenda [8:05 am PT] [17:05] Ralf Handl (SAP SE): Agenda is approved without changes [17:06] Ralf Handl (SAP SE): 3.Approve minutes from previous meeting(s) [8:10 am PT] a.Minutes from January 24, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/64630/Minutes%20of%202019-01-24%20Meeting%20%23244.docx
[17:06] Ralf Handl (SAP SE): Minutes are approved [17:06] Ralf Handl (SAP SE): Thanks to George! [17:06] 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] 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
[17:07] Ralf Handl (SAP SE): Skip for today [17:07] Ralf Handl (SAP SE): 5.Issues [8:20 am PT] a.APPLIED
i.ODATA-1188 Allow using instance annotations in $select and $expand left-over
1.https://github.com/oasis-tcs/odata-abnf/pull/15
[17:12] Mike Pizzo: I second [17:12] Ralf Handl (SAP SE): I move to merge https://github.com/oasis-tcs/odata-abnf/pull/15 [17:12] Mike Pizzo: I second again [17:13] Ralf Handl (SAP SE): No objections, motion passes [17:14] Ralf Handl (SAP SE): ii.ODATA-1221 Apply, as much as possible, our JSON Format to our annotations as well 1.https://github.com/oasis-tcs/odata-csdl-schemas/pull/6
2.https://github.com/oasis-tcs/odata-vocabularies/pull/34
[17:15] George Ericson morphed into George Ericson (Dell) [17:20] Mark Biamonte (Progress): I am on the call now [17:23] George Ericson (Dell): Offline, need to research mapping from UML 2.5 EnumerationLiterals to the issues in ODATA-1221 [17:24] Ralf Handl (SAP SE): I move to merge 1.https://github.com/oasis-tcs/odata-csdl-schemas/pull/6
2.https://github.com/oasis-tcs/odata-vocabularies/pull/34
[17:24] Hubert Heijkers (IBM): I second [17:25] Ralf Handl (SAP SE): No objection, motion passes [17:25] Ralf Handl (SAP SE): b.V4.01: NEW or OPEN i.ODATA-1278 Deleted Entity: @odata.removed possible in addition to @removed?
[17:25] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1278 [17:34] Ralf Handl (SAP SE): ODATA-1278 is OPEN [17:34] Ralf Handl (SAP SE): roposal: Is control information and can be used with prefix odata.
Add subsection of 4.5 for it
Clean up use of "annotation" versus "control information" across the document
[17:39] Mike Pizzo: I move we resolved ODATA-1278 as proposed [17:39] Hubert Heijkers (IBM): I second [17:39] Ralf Handl (SAP SE): ODATA-1278 is RESOLVED as proposed [17:39] Ralf Handl (SAP SE): ii.ODATA-1277 null and empty paths in Annotation Path, Property Path, Navigation Property Path [17:39] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1277 [17:41] Ralf Handl (SAP SE): ODATA-1277 is OPEN [17:41] Ralf Handl (SAP SE): Proposal: Change text for restriction in section 14.4.1.3 Annotation Path to
A non-null path MUST resolve to an annotation.
Change text for restriction in section 14.4.1.5 Navigation Property Path to
A non-null path MUST resolve to a model element whose type is an abstract or concrete entity type, or a collection of abstract or concrete entity types, e.g. a navigation property.
Change text for restriction in section 14.4.1.6 Property Path to
A non-null path MUST resolve to a model element whose type is an abstract or concrete primitive or complex type, or a collection of abstract or concrete primitive or complex types, e.g. a structural property.
[17:41] Mike Pizzo: I move we resolved ODATA-1277 as proposed [17:42] Matt Borges (SAP): i second [17:42] Ralf Handl (SAP SE): ODATA-1277 is RESOLVED as proposed [17:42] Ralf Handl (SAP SE): iii.ODATA-1276 Explicitly allow the minus sign / dash in a search term [17:42] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1276 [17:43] Ralf Handl (SAP SE): ODATA-1276 is OPEN [17:43] Ralf Handl (SAP SE): $search=red [17:44] Ralf Handl (SAP SE): $search="red bicycle" [17:44] Ralf Handl (SAP SE): $search=-2 [17:45] Ralf Handl (SAP SE): $search=red is the same as $search="red" [17:45] Ralf Handl (SAP SE): $search=red OR bicycle [17:47] Ralf Handl (SAP SE): $search=or [17:47] Ralf Handl (SAP SE): $search="OR" [17:47] Ralf Handl (SAP SE): $search=red "OR" bicycle [17:48] Hubert Heijkers (IBM): I move to resolve ODATA-1276 as proposed [17:48] George Ericson (Dell): Second ODATA-1277 [17:49] George Ericson (Dell): Second [17:49] Ralf Handl (SAP SE): ODATA-1276 is RESOLVED as proposed [17:49] Ralf Handl (SAP SE): https://github.com/oasis-tcs/odata-abnf/pull/14 [17:50] Ralf Handl (SAP SE): I move to merge https://github.com/oasis-tcs/odata-abnf/pull/14 [17:50] George Ericson (Dell): Second [17:51] Ralf Handl (SAP SE): No objections, motion passes [17:51] Ralf Handl (SAP SE): iv.ODATA-1263 Requirement for 204 (No Content) with 11.4.3 "Update an Entity" is not backwards compatible [17:52] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1263 [17:53] Ralf Handl (SAP SE): Change text for Update an Entity (and for Update a Primitive/Complex/Collection Property) to
Upon successful completion the service responds with either 200 OK, or 204 No Content if the request included a Prefer header with a value of return=minimal.
Corresponding text for Create an Entity is
Upon successful completion the service MUST respond with either 201 Created, or 204 No Content if the request included a Prefer header with a value of return=minimal.
Corresponding text for Create a Media Entity is
Upon successful completion the service responds with either 201 Created, or 204 No Content if the request included a Prefer header with a value of return=minimal.
[17:54] Ralf Handl (SAP SE): Current (incompatible) text:
On success the service MUST respond with 204 No Content, or with 200 OK if the request included a return Prefer header with a value of return=representation.
[18:01] Ralf Handl (SAP SE): Discussion: is "minimal" always 204 No Content, or are services free to interpret "minimal"? [18:08] Mike Pizzo: Current wording in Create suggests that 204 No Content is returned unless the preference is specified: Upon successful completion the service MUST respond with either 201 Created, or 204 No Content if the request included a return Prefer header with a value of return=minimal.
[18:08] Ralf Handl (SAP SE): ODATA-1263 is OPEN [18:12] Ralf Handl (SAP SE): Intention in V3: on create return a representation, on update don't return a representation [18:27] Ralf Handl (SAP SE): Upon successful completion the service responds with either 200 OK or 204 No Content. [18:29] Mike Pizzo: If we wanted to point to prefer header: Upon successful completion the service responds with either 200 OK or 204 No Content. The client can explicitly request that the response include a body by specifying a prefer header with a value of return=representation.
[18:31] Mike Pizzo: Alternate: Upon successful completion the service responds with either 200 OK or 204 No Content. The client can express a preference that the response include a body by specifying a prefer header with a value of return=representation.
[18:32] Mike Pizzo: As per George: Upon successful completion the service responds with either 200 OK or 204 No Content. The client can express a preference that the response SHOULD include a body by specifying a prefer header with a value of return=representation.
[18:32] Ralf Handl (SAP SE): Upon successful completion the service responds with either 200 OK or 204 No Content. The client can explicitly request that the response SHOULD include a body by specifying a prefer header with a value of return=representation. [18:35] Mike Pizzo: How about: Upon successful completion the service responds with either 200 OK or 204 No Content. The client can request that the response SHOULD include a body by specifying a prefer header with a value of return=representation.
[18:37] Ralf Handl (SAP SE): Upon successful completion the service responds with either 200 OK or 204 No Content. The client may request that the response SHOULD include a body by specifying a prefer header with a value of return=representation. [18:40] Mike Pizzo: I move to resolve ODATA-1263 as proposed [18:40] Hubert Heijkers (IBM): I second [18:40] Mark Biamonte (Progress): I second [18:40] Ralf Handl (SAP SE): ODATA-1263 is RESOLVED as proposed [18:41] Ralf Handl (SAP SE): v.ODATA-1260 Clarify read-write access via URLs differing from the canonical/read/edit URL [18:41] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1260 [18:46] George Ericson (Dell): To retrieve an individual entity, the client makes a GET request to the URL that allows read of a single entity. [18:47] George Ericson (Dell): To update an individual entity, the client makes an update request to the URL that allows update of a single entity. [18:56] George Ericson (Dell): Issue is complex and needs more thought. [18:56] Ralf Handl (SAP SE): 6.Next meetings [9:50 am PT] a.Thursday Febuary 07, 2019 during 8-10 am PST (17:00-19:00 CET)
b.Thursday Febuary 14, 2019 during 8-10 am PST (17:00-19:00 CET)
[18:57] Ralf Handl (SAP SE): 7.AOB and wrap up [9:55 am PT] [18:57] 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 31, 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.
Issues [8:20 am PT]
i. ODATA-1188
Allow using instance annotations in $select and $expand – left-over
ii. ODATA-1221
Apply, as much as possible, our JSON Format to our annotations as well
i. ODATA-1278
Deleted Entity: @odata.removed possible in addition to @removed?
ii. ODATA-1277
null and empty paths in Annotation Path, Property Path, Navigation Property Path
iii. ODATA-1276
Explicitly allow the minus sign / dash in a search term
iv. ODATA-1263
Requirement for 204 (No Content) with 11.4.3 "Update an Entity" is not backwards compatible
v. ODATA-1260
Clarify read-write access via URLs differing from the canonical/read/edit URL
vi. ODATA-1259
Clarify @type (@odata.type) and metadata=full
vii. ODATA-1250
GeoJSON, SRID, and LineString
viii. ODATA-1243
Clarify whether $orderby and string comparison with ge, gt, le, lt is language-specific
ix. ODATA-1242
Clarify that resolved relative URIs in batch responses cannot contain content-ID references
x. ODATA-1238
Clarifications for select-list in ContextUrl
xi. ODATA-1168
Clarify the use of ETags for Avoiding Update Conflicts
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-1226
Ambiguity with Capabilities.ChangeTracking annotation
xv. 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)
xvi. ODATA-1064
Add ability to annotate collections to return only count and NextLink
xvii. 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-1273
Define mapping of permission scopes to resources
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.
6.
Next meetings [9:50 am PT]
7.
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]