[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Agenda for OData TC meeting on 2019-02-07 - chat transcript
[17:03] 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 07, 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=47972
2.Approve agenda [8:05 am PT]
3.Approve minutes from previous meeting(s) [8:10 am PT]
a.Minutes from January 31, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/64640/Minutes%20of%202019-01-31%20Meeting%20%23245.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-1266 Geo literals with three dimensions
1.https://github.com/oasis-tcs/odata-abnf/pull/16
b.V4.01: NEW or OPEN
i.ODATA-1280 Clarify insert entity defined only by key properties of related entities
ii.ODATA-1259 Clarify @type (@odata.type) and metadata=full
iii.ODATA-1250 GeoJSON, SRID, and LineString
iv.ODATA-1243 Clarify whether $orderby and string comparison with ge, gt, le, lt is language-specific
v.ODATA-1242 Clarify that resolved relative URIs in batch responses cannot contain content-ID references
vi.ODATA-1238 Clarifications for select-list in ContextUrl
vii.ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts
viii.ODATA-1165 Describe $expand and $select via prose text and examples, remove ABNF snippets
ix.ODATA-1267 URL Conventions example in 5.1.1.5.1 has "bad" whitespace
x.ODATA-1260 Clarify read-write access via URLs differing from the canonical/read/edit URL
xi.ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation
xii.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)
xiii.ODATA-1064 Add ability to annotate collections to return only count and NextLink
xiv.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 February 14, 2019 during 8-10 am PST (17:00-19:00 CET)
b.Thursday February 21, 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:03] Ralf Handl (SAP SE): Voting Members: 5 of 9 (55%) (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): Achieved quorum: yes [17:07] Ralf Handl (SAP SE): Voting Members: 7 of 9 (77%) (used for quorum calculation) [17:09] Ralf Handl (SAP SE): Voting Members: 8 of 9 (88%) (used for quorum calculation) [17:09] Ralf Handl (SAP SE): Voting Members: 9 of 9 (100%) (used for quorum calculation) [17:10] Ralf Handl (SAP SE): 2.Approve agenda [8:05 am PT] [17:10] Ralf Handl (SAP SE): Agenda is approved [17:10] Ralf Handl (SAP SE): 3.Approve minutes from previous meeting(s) [8:10 am PT] a.Minutes from January 31, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/64640/Minutes%20of%202019-01-31%20Meeting%20%23245.docx
[17:10] Ralf Handl (SAP SE): Minutes are approved [17:10] Ralf Handl (SAP SE): Thanks to George! [17:10] 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:12] Ralf Handl (SAP SE): Mike asked Mark Nottingham on guidance for using/supporting headers without registration [17:13] Ralf Handl (SAP SE): 5.Issues [8:20 am PT] a.APPLIED
i.ODATA-1266 Geo literals with three dimensions
1.https://github.com/oasis-tcs/odata-abnf/pull/16
[17:18] Mike Pizzo: I move that we approve the application of ODATA-1266 and close as applied. [17:18] Mark Biamonte (Progress): I second [17:18] Ralf Handl (SAP SE): No objection, motion passes [17:18] Ralf Handl (SAP SE): b.V4.01: NEW or OPEN i.ODATA-1280 Clarify insert entity defined only by key properties of related entities
[17:18] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1280 [17:25] Ralf Handl (SAP SE): A key property MUST be a non-nullable primitive property of the entity type itself or a non-nullable primitive property of a single-valued, non-nullable complex or navigation property (recursively) of the entity type. Navigation properties MAY only be used in OData 4.01 responses. [17:34] Ralf Handl (SAP SE): Specification text is overly generous, original intent was to avoid "duplicate" foreign-key properties in the source entity [17:37] Ralf Handl (SAP SE): Mike: add restriction that all key properties of the related entity have to be part of the "source" key [17:38] Ralf Handl (SAP SE): Ralf: restrict to at most one navigation segment that then must be second-to-last [17:40] Ralf Handl (SAP SE): all key properties of a "directly related" entity if the relationship is to-one and not nullable [17:43] Ralf Handl (SAP SE): <EntityType Name="Edge"> <Key>
<PropertyRef Name="From/ID" Alias="FromID" />
<PropertyRef Name="To/ID" Alias="ToID" />
</Key>
<NavigationProperty Name="From" Type="this.Node" Nullable="false" />
<NavigationProperty Name="To" Type="this.Node" Nullable="false" />
</EntityType>
[17:51] Ralf Handl (SAP SE): ODATA-1280 is OPEN [17:51] Hubert Heijkers (IBM): I move to resolve ODATA-1280 as per the new proposal [17:51] George Ericson: second [17:51] Ralf Handl (SAP SE): ODATA-1280 is RESOLVED with the modified proposal [17:52] Ralf Handl (SAP SE): ii.ODATA-1259 Clarify @type (@odata.type) and metadata=full [17:52] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1259 [17:53] Ralf Handl (SAP SE): ODATA-1259 is OPEN [17:53] Mike Pizzo: I move we resolve ODATA-1259 as proposed [17:54] George Ericson: second [17:54] Ralf Handl (SAP SE): ODATA-1259 is RESOLVED as proposed [17:54] Ralf Handl (SAP SE): iii.ODATA-1250 GeoJSON, SRID, and LineString [17:54] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1250 [17:56] Ralf Handl (SAP SE): ODATA-1250 is OPEN [17:57] Ralf Handl (SAP SE): Mike: we should discourage the use of CRS as this is no longer present in the current GeoJSON RFC 7946 [18:00] Ralf Handl (SAP SE): Proposal: 1) Add GeoJSON-2008 as a non-normative reference and point to it (especially to http://geojson.org/geojson-spec.html#named-crs) in the bullet point mentioning the CRS object. Discourage use of CRS object as it is not part of the final GeoJSON specification.
(Note: we already reference RFC 7946 as a normative reference, which in turn references GeoJSON-2008, but without a hyperlink. So whole point of the non-normative reference is providing the link).
2) Remove extension to zero/one position for LineString by removing the second bullet point in the current text (see Description).
[18:00] George Ericson: move to resolve odata 1250 as modified [18:01] Mike Pizzo: I second [18:01] Ralf Handl (SAP SE): ODATA-1250 is RESOLVED with the amended proposal [18:01] Ralf Handl (SAP SE): iv.ODATA-1243 Clarify whether $orderby and string comparison with ge, gt, le, lt is language-specific [18:01] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1243 [18:03] Ralf Handl (SAP SE): Mark: add a $language query option? [18:04] Ralf Handl (SAP SE): s/Mark/George/ [18:05] Ralf Handl (SAP SE): Proposal: Explicitly leave the choice to the service implementation, mention that sort order and comparison MAY depend e.g. on the content-language of the response.
[18:06] Ralf Handl (SAP SE): George: make it SHALL [18:06] Ralf Handl (SAP SE): Mike: make it SHOULD because SHALL would be a breaking change [18:11] Ralf Handl (SAP SE): ODATA-1243 is OPEN [18:12] Ralf Handl (SAP SE): Mike: should we mention that data stores may have different collations / sort orders per property/column? [18:18] Ralf Handl (SAP SE): Proposal: Services SHOULD compare and sort language-dependent properties according to the content-language of the response.
[18:18] Hubert Heijkers (IBM): I move to resolve ODATA-1243 as per the updated proposal [18:19] Mike Pizzo1: I second [18:19] Ralf Handl (SAP SE): ODATA-1243 is RESOLVED as proposed [18:19] Ralf Handl (SAP SE): v.ODATA-1242 Clarify that resolved relative URIs in batch responses cannot contain content-ID references [18:19] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1242 [18:20] Ralf Handl (SAP SE): Description With ODATA-1234 we allow services to return URLs relative to the request URL in headers. We need to clarify that in a batch response, the service is responsible for producing URLs that don't contain content-id references.
[18:20] Ralf Handl (SAP SE): Proposal: Clarify that if the service returns URLs relative to the request URL in a batch response the service is responsible for ensuring the resolved URLs do not contain a content-ID reference.
[18:21] Ralf Handl (SAP SE): ODATA-1242 is OPEN [18:26] Matt Borges (SAP): I move to resolve ODATA-1242 as per the updated proposal [18:26] George Ericson: second [18:26] Ralf Handl (SAP SE): ODATA-1242 is RESOLVED with the amended proposal [18:26] Ralf Handl (SAP SE): vi.ODATA-1238 Clarifications for select-list in ContextUrl [18:26] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1238 [18:27] Ralf Handl (SAP SE): Proposal: Make sure the following are clear in the documentation:
1) If the contextUrl includes only expanded navigation properties (i.e., only navigation properties suffixed with parens), then all structural properties are implicitly selected (same as if there were no properties listed in the select-list)
2) In section 10.8, Projected Entity, change:
"Note that expanded properties are implicitly selected." to "Note that expanded properties are implicitly included in the response."
3) Regardless of how contained structural properties are represented in the request URL (as paths or as select options) they are represented in the contextUrl using path syntax, as defined in 4.0. Similarly, expands nested within $select are represented the same as expands outside of $select.
4) Operations in the ContextUrl should always be represented using the fully qualified name, so if it has a dot it is an operation. Functions suffixed with parens represent a specific overload, while functions without parens represent all overloads of the function.
5) Navigation properties with expanded references are not represented in the ContextUrl. i.e., the contextUrl for Customers?$expand=Orders/$ref would just be $metadata#Customers.
[18:40] Ralf Handl (SAP SE): #4: "fully qualified" means "namespace- or alias-qualified" [18:40] Ralf Handl (SAP SE): TODO: adjust protocol spec and always explicitly use "namespace- or alias-qualified" [18:41] Ralf Handl (SAP SE): TODO: adjust ABNF and rename rule "namespace" to "namespaceOrAlias" [18:48] Mike Pizzo: I move we resolve ODATA-1238 as proposed. [18:49] Hubert Heijkers (IBM): I second [18:49] Ralf Handl (SAP SE): ODATA-1238 is RESOLVED as proposed [18:49] Ralf Handl (SAP SE): vii.ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts [18:50] Ralf Handl (SAP SE): Description http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Data_Modification states:
11.4.1.1 Use of ETags for Avoiding Update Conflicts
If an ETag value is specified in an If-Match or If-None-Match header of a Data Modification Request or Action Request, the operation MUST only be invoked if the if-match or if-none-match condition is satisfied.
The ETag value specified in the if-match or if-none-match request header may be obtained from an ETag header of a response for an individual entity, or may be included for an individual entity in a format-specific manner.
Issue requiring clarification: we carefully need to distinguish between ODatas meaning of entity = an instance of an entity type" and HTTPs meaning of entity = the thing whose representation is transferred. ETags (= entity tags) refer to the HTTP meaning, and thus links/references/relationships are HTTP entities that can have their own ETags.
Also clarify:
Can a "HTTP entity" / "link entity" identified by xxx/$ref have an ETag?
Is the ETag of a "link entity" logically independent of the ETags of the linked OData entities at either end?
If xxx is a collection resource, can the references returned by GET xxx/$ref contain @odata.etag control information to carry the individual ETag of each "link entity"?
Are EntitySet/$ref and EntitySet(<key>)/$ref only accidentally allowed by the ABNF and the prose text in Protocol 11.2.8: Requesting Entity References or are these valid resource paths?
[18:50] Ralf Handl (SAP SE): Proposal: Make clear that EntitySet/$ref and EntitySet(<key>)/$ref are intentionally allowed.
An entity reference identified by xxx/$ref as defined in JSON Format currently cannot contain @odata.etag control information.
An entity reference identified by xxx/$ref can have an (own) ETag that only changes if the reference is changed to point to a different OData entity. Changes to the referenced entity do not influence the ETag of the reference.
A collection of references can have an (own) ETag which only changes if the list of references changes, i.e. a reference is added or removed.
[18:56] Ralf Handl (SAP SE): Orders(123)/Customer --> ETag1 [18:56] Ralf Handl (SAP SE): Orders(123)/Customer/$ref --> ETag2 [19:03] Ralf Handl (SAP SE): 6.Next meetings [9:50 am PT] a.Thursday February 14, 2019 during 8-10 am PST (17:00-19:00 CET)
b.Thursday February 21, 2019 during 8-10 am PST (17:00-19:00 CET)
[19:03] Ralf Handl (SAP SE): Hubert cannot attend on February 14 [19:03] Ralf Handl (SAP SE): Mike cannot attend on February 21 [19:03] Ralf Handl (SAP SE): 7.AOB and wrap up [9:55 am PT] [19:04] Ralf Handl (SAP SE): Meeting is adjourned [19:04] Ralf Handl (SAP SE): Thanks! 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 07, 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-1266
Geo literals with three dimensions
i. ODATA-1280
Clarify insert entity defined only by key properties of related entities
ii. ODATA-1259
Clarify @type (@odata.type) and metadata=full
iii. ODATA-1250
GeoJSON, SRID, and LineString
iv. ODATA-1243
Clarify whether $orderby and string comparison with ge, gt, le, lt is language-specific
v. ODATA-1242
Clarify that resolved relative URIs in batch responses cannot contain content-ID references
vi. ODATA-1238
Clarifications for select-list in ContextUrl
vii. ODATA-1168
Clarify the use of ETags for Avoiding Update Conflicts
viii. ODATA-1165
Describe $expand and $select via prose text and examples, remove ABNF snippets
ix. ODATA-1267
URL Conventions example in 5.1.1.5.1 has "bad" whitespace
x. ODATA-1260
Clarify read-write access via URLs differing from the canonical/read/edit URL
xi. ODATA-1226
Ambiguity with Capabilities.ChangeTracking annotation
xii. 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)
xiii. ODATA-1064
Add ability to annotate collections to return only count and NextLink
xiv. 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]