[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Agenda for OData TC meeting on 2019-06-27 - chat transcript
|
[27.06.2019 17:06]
[1] Agenda
1. Roll call [8:00 am]
a. Self-registration link:
https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=47992
[27.06.2019 17:06]
2. Approve agenda [8:05 am]
[27.06.2019 17:06]
New issues: [27.06.2019 17:06]
[27.06.2019 17:07]
[27.06.2019 17:07]
If time permits:
4.5 Walk through Extension for Temporal Data [27.06.2019 17:07]
Agenda is approved [27.06.2019 17:08]
Approve minutes from previous meeting(s) [8:10 am]
i. Minutes from June 20/21, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/65520/Minutes%20of%202019-06-20%2621%20Meeting%20%23262.docx
i. Minutes from June 13, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/65506/Minutes%20of%202019-06-13%20Meeting%20%23261.docx
[27.06.2019 17:08]
Minutes are approved [27.06.2019 17:08]
No Title
3. 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:15 am]
a. Upcoming
i. #0037 Concept
for Google Protocol Buffers as a data format – Hubert Heijkers – 2019-06-27
ii. #0036 Register
the OData- headers and preferences with IANA – Mark Biamonte – 2018-07-26
[27.06.2019 17:11]
Hubert: want to do a binary format after doing Compact JSON, but most likely not based on Protocol Buffers [27.06.2019 17:13]
New action items:
[27.06.2019 17:14] Ericson, George:
For binary form: Look at
https://www.dmtf.org/sites/default/files/standards/documents/DSP0218_0.8.0a.pdf
[27.06.2019 17:15]
1. Compact JSON: Oct 31, 2019 for next draft [27.06.2019 17:15]
2. Binary format/representation: March 26, 2020 [27.06.2019 17:16]
Put them on Ling [27.06.2019 17:16] Ericson, George:
In DMTF document, see Binary Encoded JSON Clause 8. [27.06.2019 17:16]
Correction: new action items go on Hubert [27.06.2019 17:17]
4. Issues [8:20 am]
[27.06.2019 17:23]
Mike & Ralf: add a TypeDefinition Name=SchemeName Type=Edm.String to Authorization vocabulary and use it for SchemeName and within Authorization vocabulary for all properties that
actually are an authorization scheme name [27.06.2019 17:24]
<Property Name=SchemeName Type=Authorization.SchemeName ... [27.06.2019 17:28] Ericson, George:
<Property Name=Scheme Type=Auth.SchemeName ...
[27.06.2019 17:30]
ODATA-1318 is OPEN The action couldn’t be completed. Please try again later.
[27.06.2019 17:30] Mike Pizzo:
0) Define a new "SchemeName" TypeDefinition in the Auth vocabulary and use within Auth vocabulary whenever referencing a scheme. [27.06.2019 17:36]
Use "Authorization" as property name in PermissionType [27.06.2019 17:37]
Same name as in type SecurityScheme within Auth vocab
We saved this conversation. You'll see it soon in the Conversations tab in Skype for Business and in the Conversation History folder in Outlook.
[27.06.2019 17:46] Mike Pizzo:
Revised proposal: [27.06.2019 17:47] Ericson, George:
Motion to approve ODATA-1318 as proposed.
[27.06.2019 17:47] Mike Pizzo:
I second [27.06.2019 17:47]
ODATA-1318 is RESOLVED as proposed [27.06.2019 17:49]
ODATA-1316 to be reviewed together with ODATA-1319 once we have a pull request for the latter [27.06.2019 17:49]
[27.06.2019 17:49]
Section 3.3 states that payloads that format Edm.Int64 and Edm.Decimal values as strings MUST specify the IEEE754Compatible=true format parameter, however section 4.1 only mentions responses.
[27.06.2019 17:50]
Change fourth paragraph of 4.1
Header Content-Type to (new text in green)
Requests and responses
MUST include the IEEE754Compatible parameter if Edm.Int64 and Edm.Decimal numbers are represented as strings.
Note: this is a non-material change as section 3.3 already required this for all payloads, which includes request payloads.
[27.06.2019 17:50]
ODATA-1319 is OPEN [27.06.2019 17:51]
Side remark: chat bubble at 17:49 CEST should talk about ODATA-1318, not 1319 [27.06.2019 17:52] Hubert Heijkers:
I more to resolve ODATA-1319 as proposed. [27.06.2019 17:52] Ericson, George:
I Second [27.06.2019 17:52]
No Title
Requests and responses with a JSON message body MUST have a Content-Type header value of application/json.
Requests MAY add the charset parameter to the content type. Allowed values are UTF-8, UTF-16, and UTF-32. If no charset parameter is present, UTF-8 MUST be assumed.
Responses MUST include the metadata parameter
to specify the amount of metadata included in the response.
Responses MUST include the IEEE754Compatible parameter
if Edm.Int64 and Edm.Decimal numbers are represented as strings.
Requests and responses MAY add the streaming parameter with a value of true or false, see section Payload
Ordering Constraints.
[27.06.2019 17:54]
ODATA-1319 is RESOLVED as proposed [27.06.2019 17:54]
ii. ODATA-1285 Add
ReadByKeyRestrictions similar to ReadRestrictions
1. Pull request already merged, just close this issue
[27.06.2019 17:55] Mike Pizzo:
I move we close ODATA-1285 as applied. [27.06.2019 17:55] Ericson, George:
I second [27.06.2019 17:55]
ODATA-1285 is CLOSED as applie [27.06.2019 17:55]
d [27.06.2019 17:55]
iii. ODATA-1264 CRUDQ
descriptions on entity sets
1. Pull request already merged, just close this issue
[27.06.2019 17:56] Hubert Heijkers:
I move to close ODATA-1264 as applied. [27.06.2019 17:56] Ericson, George:
I second [27.06.2019 17:56]
ODATA-1264 is CLOSED as applied [27.06.2019 17:56]
iv. ODATA-1234 Allow
relative URLs in headers
1. Issue was applied and missed Fix Version V4.01_CS02, just close this issue
[27.06.2019 17:57] Hubert Heijkers:
I move to close ODATA-1234 as applied [27.06.2019 17:57] Ericson, George:
second [27.06.2019 17:57]
ODATA-1234 is CLOSED as applied [27.06.2019 17:58]
No Title
c. Data Aggregation: NEW
or OPEN
i. ODATA-1218 Transformations
for recursive hierarchy processing
[27.06.2019 17:58]
ODATA-1218 is OPEN [27.06.2019 17:58]
ii. ODATA-945 Correct
examples 53 and 54
[27.06.2019 17:59]
Postponed [27.06.2019 17:59]
d. Vocabularies: NEW
or OPEN with concrete proposal
i. ODATA-1304 Improve
descriptions on Capabilities.NavigationRestrictionsType
1. https://github.com/oasis-tcs/odata-vocabularies/pull/51/files
[27.06.2019 18:12]
Mike: Navigability on the top level is default that can be overruled by a more specific restriction on a navigation property [27.06.2019 18:13]
Saurabh, Ralf: if top level says None, don't look at navigation properties at all [27.06.2019 18:23]
Root: default navigability for all navigation properties, which can be overruled for individual navigation properties in RestrictedProperties [27.06.2019 18:28] Mike Pizzo:
Default navigability for all navigation properties on this type. Individual navigation properties can override this value via RestrictedProperties. [27.06.2019 18:31] Mike Pizzo:
Propose: [27.06.2019 18:32]
Put all text into Description, no LongDescription [27.06.2019 18:33]
Default navigability for all navigation properties of the annotation target. [27.06.2019 18:33]
ODATA-1304 [27.06.2019 18:33]
is OPEN [27.06.2019 18:34] Ericson, George:
Motion to approve OData-1304 as proposed. [27.06.2019 18:34] Mike Pizzo:
I second [27.06.2019 18:36]
ODATA-1304 is RESOLVED with the amended proposal [27.06.2019 18:36]
ii. ODATA-1300 Capabilities:
add ExpandRestrictions to type NavigationPropertyRestriction
[27.06.2019 18:47]
GET /People/$count [27.06.2019 18:47]
GET /People('john')/Friends/$count [27.06.2019 18:51]
Mike: Countable only affects the annotated entity set, all other paths need to be listed explicitly [27.06.2019 18:52] Mike Pizzo:
Note: this interpretation makes it very expensive to specify that I don't support count at all. [27.06.2019 18:55] Mike Pizzo:
We could add a "SupportsCount" bool on CountRestrictionsType as a shortcut for saying "I don't support count on anything". [27.06.2019 18:57] Mike Pizzo:
This still wouldn't allow saying "I support count on navigation collection properties but not structural collection properties" which would probably be the case for most 4.0 services. [27.06.2019 18:57]
5. Next meetings [9:50 am]
a. Thursday July 04, 2019 during 8-10 am PDT (17:00-19:00 CEST) – public holiday in the US, no meeting
b. Thursday July 11, 2019 during 8-10 am PDT (17:00-19:00 CEST)
c. Thursday July 18, 2019 during 8-10 am PDT (17:00-19:00 CEST)
The action couldn’t be completed. Please try again later.
[27.06.2019 18:59]
Mike may be on vacation on July 11 [27.06.2019 18:59]
6. AOB and wrap up [9:55 am]
[27.06.2019 18:59]
Meeting is adjourned From: odata@lists.oasis-open.org <odata@lists.oasis-open.org>
On Behalf Of Handl, Ralf Correct registration link
https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=47992 From: odata@lists.oasis-open.org <odata@lists.oasis-open.org>
On Behalf Of Handl, Ralf And we can resolve the first new issue for CS02:
ODATA-1319 From: Michael Pizzo <mikep@microsoft.com>
1.
I would like to add one (hopefully) last set of fixes for the recently added constructs to the Capabilities vocabulary:
ODATA-1318 From: odata@lists.oasis-open.org <odata@lists.oasis-open.org>
On Behalf Of Handl, Ralf If time permits: 4.5 Walk through Extension for Temporal Data 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 June 27, 2019 during 8-10 am PDT (17:00-19:00
CEST).
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] a. Self-registration link:
https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id= 2. Approve agenda [8:05 am] a. Approve minutes from previous meeting(s) [8:10 am] i.
Minutes from June 20/21, 2019 TC meeting:
https://www.oasis-open.org/committees/download.php/65520/Minutes%20of%202019-06-20%2621%20Meeting%20%23262.docx
i.
Minutes from June 13, 2019 TC meeting:
https://www.oasis-open.org/committees/download.php/65506/Minutes%20of%202019-06-13%20Meeting%20%23261.docx
3. 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:15 am] a. Upcoming i. #0037
Concept for Google Protocol Buffers as a data format – Hubert Heijkers – 2019-06-27 ii. #0036
Register the OData- headers and preferences with IANA – Mark Biamonte – 2018-07-26
4. Issues [8:20 am]
a.
APPLIED i.
ODATA-1316 Should support multiple permissions for read/write 1.
https://github.com/oasis-tcs/odata-vocabularies/pull/54 ii.
ODATA-1285 Add ReadByKeyRestrictions similar to ReadRestrictions 1. Pull request already merged, just close this issue iii.
ODATA-1264 CRUDQ descriptions on entity sets 1. Pull request already merged, just close this issue iv.
ODATA-1234 Allow relative URLs in headers 1. Issue was applied and missed Fix Version V4.01_CS02, just close this issue
b. V4.01:
NEW or OPEN i. none c. Data Aggregation:
NEW or OPEN i.
ODATA-1218 Transformations for recursive hierarchy processing ii.
ODATA-945 Correct examples 53 and 54 d.
Vocabularies:
NEW or OPEN with concrete proposal i.
ODATA-1304
Improve descriptions on Capabilities.NavigationRestrictionsType 1.
https://github.com/oasis-tcs/odata-vocabularies/pull/51/files ii.
ODATA-1300
Capabilities: add ExpandRestrictions to type NavigationPropertyRestriction 1.
https://github.com/oasis-tcs/odata-vocabularies/pull/50/files e.
Vocabularies:
NEW or OPEN that need more discussion i.
ODATA-1275
Describing and querying "JSON properties" ii.
ODATA-1214 Annotate constructor actions iii.
ODATA-1140
Add details to HttpResponse iv.
ODATA-1107
Introduce instance annotation to specify which types an instance "implements" v.
ODATA-1060
Improve specification of element response requirements vi.
ODATA-884
Allow describing possible responses to requests for a particular resource (public comment c201510e00019) 5. Next meetings [9:50 am] a. Thursday July 04, 2019 during 8-10 am PDT (17:00-19:00 CEST) – public holiday in the US, no meeting b. Thursday July 11, 2019 during 8-10 am PDT (17:00-19:00 CEST) c. Thursday July 18, 2019 during 8-10 am PDT (17:00-19:00 CEST) 6. AOB and wrap up [9:55 am] [2] References
[3] Timeline |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]