[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Agenda for OData TC meeting on 2019-02-14 - chat transcript
[17:01] 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 February 14, 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=47973
2.Approve agenda [8:05 am PT]
3.Approve minutes from previous meeting(s) [8:10 am PT]
a.Minutes from February 07, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/64690/Minutes%20of%202019-02-07%20Meeting%20%23246.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.V4.01: NEW or OPEN
i.ODATA-1281 Clarify: interpretation of omitted optional parameters
ii.ODATA-1267 URL Conventions example in 5.1.1.5.1 has "bad" whitespace
iii.ODATA-1165 Describe $expand and $select via prose text and examples, remove ABNF snippets
iv.ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation
v.ODATA-1282 How to set the mediaReadLink and mediaEditLink of a stream property
vi.ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts
vii.ODATA-1176 Capabilities: add new term SelectSupport
viii.ODATA-1283 $search: ABNF comment is more restrictive than prose text
ix.ODATA-1260 Clarify read-write access via URLs differing from the canonical/read/edit URL
x.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)
xi.ODATA-1064 Add ability to annotate collections to return only count and NextLink
xii.ODATA-1005 Make sure we have capabilities for all new 4.01 functionality
b.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
c.Vocabularies: NEW or OPEN with concrete proposal
i.ODATA-1099 Add annotations to describe custom query options and custom headers
d.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 February 21, 2019 during 8-10 am PST (17:00-19:00 CET)
b.Thursday February 28, 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:02] anonymous morphed into Mark Biamonte (Progress) [17:02] Ralf Handl (SAP SE): Voting Members: 4 of 9 (44%) (used for quorum calculation) [17:02] Ralf Handl (SAP SE): Voting Members: 5 of 9 (55%) (used for quorum calculation) [17:04] Ralf Handl (SAP SE): Voting Members: 8 of 9 (88%) (used for quorum calculation) [17:04] Ralf Handl (SAP SE): Achieved quorum:yes [17:05] Ralf Handl (SAP SE): 2.Approve agenda [8:05 am PT] [17:06] Ralf Handl (SAP SE): Saurabh to join later: discuss Vocabularies once he joins [17:06] Ralf Handl (SAP SE): Agenda is approved with this change [17:06] Ralf Handl (SAP SE): 3.Approve minutes from previous meeting(s) [8:10 am PT] a.Minutes from February 07, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/64690/Minutes%20of%202019-02-07%20Meeting%20%23246.docx
[17:07] Ralf Handl (SAP SE): Minutes are approved [17:07] 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:09] Ralf Handl (SAP SE): Mike in communication with Mark Nottingham [17:09] Ralf Handl (SAP SE): 5.Issues [8:20 am PT] a.V4.01: NEW or OPEN
i.ODATA-1281 Clarify: interpretation of omitted optional parameters
[17:10] Ralf Handl (SAP SE): Description With https://issues.oasis-open.org/browse/ODATA-1066 we added the possibility to mark parameters as optional.
We also added text to Part 1: Protocol describing how function overload resolution works in combination with optional parameters.
Two aspects of optional parameters just came up during implementation that I cant find in the document or the issue:
Are services free to interpret the absence of a parameter as best suits the purpose of the function?
Can actions also have optional parameters?
[17:11] Ralf Handl (SAP SE): Proposal: Omitting an optional function parameter means that the parameter has the default value specified in the annotation Core.OptionalParameter. If no explicit DefaultValue is specified, the default value is null, as per standard interpretation of annotation records.
Nullable non-binding action parameters can already be omitted from the request body, and omitting them means that they have the value null. Allowing to annotate them with Core.OptionalParameter and a DefaultValue would be incompatible with V4.
[17:12] Ralf Handl (SAP SE): ODATA-1281 is OPEN [17:13] Ralf Handl (SAP SE): Mike: assumed omitting an optional function parameter leaves it to the implementation to interpret that [17:14] Ralf Handl (SAP SE): Need to call that out in the term definition [17:15] Ralf Handl (SAP SE): Any parameter values not specified in the JSON object are assumed to have the null valu [17:17] Ralf Handl (SAP SE): Mike: unannotated action parameters work as in V4: omission means null [17:19] Mike Pizzo: For part 1: Omitting an optional function parameter means that the parameter has the default value specified in the annotation Core.OptionalParameter. Call out that the absence of an explicit DefaultValue means that the parameter has no default; it is up to the implementation of the function to interpret absence of a parameter value. [17:22] Ralf Handl (SAP SE): Mike: desired behavior for action: OptionalParameter with DefaultValue alters omission to mean "default value" instead of null [17:22] Ralf Handl (SAP SE): Mike: adding OptionalParameter annotation is a breaking change [17:25] Ralf Handl (SAP SE): Mike: can also annotate non-nullable action parameters with OptionalParameter and then it can be omitted [17:26] Ralf Handl (SAP SE): Mike: changing a DefaultValue also is a breaking change [17:28] Ralf Handl (SAP SE): Mike: omitted action parameter is equivalent to an action parameter annotated as OptionalParameter with DefaultValue null [17:33] Ralf Handl (SAP SE): Omitting an optional function parameter means that the parameter has the default value specified in the annotation Core.OptionalParameter. If no explicit DefaultValue is specified, the service is free on how to interpret this. Call this out in term definition.
Nullable non-binding action parameters can already be omitted from the request body, and omitting them means that they have the value null.
Allow annotating action parameters with Core.OptionalParameter. This allows to omit them, whether they are nullable or not.
Omitted action parameter with a DefaultValue means that default value
Omitted action parameter without DefaultValue can be freely interpreted by the service
[17:35] Mike Pizzo: I would add: A nullable non-binding action parameter is equivalent to being annotated with optionalParameter = true and a default value as null. [17:37] Mike Pizzo: I move we approve ODATA-1281 with the revised proposal [17:37] George Ericson (Dell): Second [17:38] Ralf Handl (SAP SE): ODATA-1281 is RESOLVED with the amended proposal [17:39] Ralf Handl (SAP SE): ii.ODATA-1267 URL Conventions example in 5.1.1.5.1 has "bad" whitespace [17:39] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1267 [17:39] Ralf Handl (SAP SE): ODATA-1267 is OPEN [17:40] Mike Pizzo: I move we resolved OData-1267 as proposed [17:40] Mark Biamonte (Progress): I second [17:41] Ralf Handl (SAP SE): ODATA-1267 is RESOLVED as proposed [17:41] Ralf Handl (SAP SE): iii.ODATA-1165 Describe $expand and $select via prose text and examples, remove ABNF snippets [17:41] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1165 [17:44] George Ericson (Dell): Move to resolve OData-1165 as proposed [17:46] Mike Pizzo: I second [17:46] Ralf Handl (SAP SE): ODATA-1165 is RESOLVED as proposed [17:46] Ralf Handl (SAP SE): iv.ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation [17:46] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1226 [17:48] Ralf Handl (SAP SE): For collection-valued properties the absence of a property value _expression_ is equivalent to specifying an empty collection as its value. [17:56] Ralf Handl (SAP SE): ODATA-1226 is OPEN [17:57] Ralf Handl (SAP SE): If no properties are specified, the clients cannot assume support for filtering on/expanding any properties. [17:59] Ralf Handl (SAP SE): If no properties are specified or Filterable/ExpandableProperties is omitted, the clients cannot assume support for filtering on/expanding any properties. [18:00] George Ericson (Dell): Move to resolve OData-1226 as proposed. [18:00] Mark Biamonte (Progress): I second [18:01] Ralf Handl (SAP SE): ODATA-1226 is RESOLVED with the amended proposal [18:01] Ralf Handl (SAP SE): v.ODATA-1282 How to set the mediaReadLink and mediaEditLink of a stream property [18:01] Mark Biamonte (Progress): I need to drop off of the call now. Talk to you all next week [18:07] Ralf Handl (SAP SE): Mike: need to make sure this new semantics does not conflict with existing semantics [18:07] Ralf Handl (SAP SE): Mike: need capabilities to advertise support for this [18:08] Ralf Handl (SAP SE): ODATA-1282 is OPEN [18:09] Ralf Handl (SAP SE): Ralf to amend proposal with a corresponding Capability term that can be applied to the stream property, e.g. UserSettableLocation [18:11] Ralf Handl (SAP SE): d.ii.ODATA-1273 Define mapping of permission scopes to resources [18:11] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1273 [18:20] Mike Pizzo: restrictedproperties is a comma-separated list of included properties, properties prepended with minus (in which case they are omitted), or * (meaning all properties are supported). Absence of the "RestrictedProperties" means all properties are included. [18:22] Mike Pizzo: Rewording for clarification: restrictedproperties is a comma-separated list of accessible properties, properties prepended with minus (in which case they are not accessible given the specified scope), or * (meaning all properties are accessible given the specified scope). Absence of the "RestrictedProperties" means all properties are accessible with the given scope. [18:44] Saurabh Madan (Microsoft): OData 1273 - https://github.com/oasis-tcs/odata-vocabularies/pull/35/files?utf8=%E2%9C%93&diff=split [18:52] Mike Pizzo: Retrieve is more consistent with our current language, Read seems simpler. [18:53] Ralf Handl (SAP SE): Decision: name it ReadRestrictions, use "Retrieve single or collection" in description [18:54] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1099 [18:54] George Ericson (Dell): Move to resolve 1099 as proposed with change to use Read restrictions. [18:55] Mike Pizzo: I second [18:55] Ralf Handl (SAP SE): ODATA-1099 is RESOLVED with the amended proposal [18:56] Ralf Handl (SAP SE): ODATA-1273 is OPEN [18:56] Mike Pizzo: I move to resolve ODATA-1273 as proposed. [18:56] George Ericson (Dell): Second [18:56] Ralf Handl (SAP SE): ODATA-1273 is RESOLVED as propsed [18:56] Ralf Handl (SAP SE): 6.Next meetings [9:50 am PT] a.Thursday February 21, 2019 during 8-10 am PST (17:00-19:00 CET)
b.Thursday February 28, 2019 during 8-10 am PST (17:00-19:00 CET)
[18:57] Ralf Handl (SAP SE): Mike cannot attend next week [18:58] Ralf Handl (SAP SE): Do not discuss ODATA-1064 next week [18:58] Ralf Handl (SAP SE): 7.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 February 14, 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-1281
Clarify: interpretation of omitted optional parameters
ii. ODATA-1267
URL Conventions example in 5.1.1.5.1 has "bad" whitespace
iii. ODATA-1165
Describe $expand and $select via prose text and examples, remove ABNF snippets
iv. ODATA-1226
Ambiguity with Capabilities.ChangeTracking annotation
v. ODATA-1282
How to set the mediaReadLink and mediaEditLink of a stream property
vi. ODATA-1168
Clarify the use of ETags for Avoiding Update Conflicts
vii. ODATA-1176
Capabilities: add new term SelectSupport
viii. ODATA-1283
$search: ABNF comment is more restrictive than prose text
ix. ODATA-1260
Clarify read-write access via URLs differing from the canonical/read/edit URL
x. 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)
xi. ODATA-1064
Add ability to annotate collections to return only count and NextLink
xii. 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-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]