[13:43] Room information was updated by: Stefan Hagen
OASIS Open Data Protocol (OData) TC OData TC Weekly Meeting (Conference Call) #205
- Thursday, 01 March 2018, 08:00am to 10:00am PST
- i.e. 2018-03-01 17:00 to 19:00 CET (UTC+1)
- other timezone? Try eg.:
- https://www.timeanddate.com/worldclock/meetingdetails.html?year=2018&month=3&day=1&hour=16&min=0&sec=0&p1=47&p2=69&p3=179
UsefulPlaces:
- Chat:
- http://webconf.soaphub.org/conf/room/odatatc # ... this place
- ScreenShare and Voice:
- https://sap.emea.pgiconnect.com/OData-TC/
Next Planned meetings (tentative):
- Thursday March 08, 2018 during 8-10 am PST (17:00-19:00 CET)
- https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46246
- Thursday March 15, 2018 during 8-10 am PST (16:00-18:00 CEST) Daylight Saving Time in Central Europe
- https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46247
Agenda-Draft E-Mail URL:
- E-Mail Public URL = "" href="https://lists.oasis-open.org/archives/odata/201802/msg00105.html" target="_blank">https://lists.oasis-open.org/archives/odata/201802/msg00105.html
Minutes Draft Public URL (previous meeting):
- URL = "" href="https://www.oasis-open.org/committees/download.php/62583/odata-meeting-204_on-20180222-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/62583/odata-meeting-204_on-20180222-minutes.html
Online document walkthroughs or presentations:
- URL = "" href="https://sap.emea.pgiconnect.com/OData-TC/" target="_blank">https://sap.emea.pgiconnect.com/OData-TC/
Timeline(Updated!):
- URL = "" href="https://www.oasis-open.org/committees/download.php/61677/TC%20Timeline-2017-09-29.docx" target="_blank">https://www.oasis-open.org/committees/download.php/61677/TC%20Timeline-2017-09-29.docx
Agenda Draft (for meeting #205):
==============================================================
1. Roll call [8:00 am PT]
1.1 Self-registration link:
URL = "" href="https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46245" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46245
2. Approve agenda [8:05 am PT]
3. Approve minutes from previous meeting(s) [8:10 am PT]
3.1 Minutes from February 22, 2018 TC meeting:
URL = "" href="https://www.oasis-open.org/committees/download.php/62583/odata-meeting-204_on-20180222-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/62583/odata-meeting-204_on-20180222-minutes.html
4. Review action items [Action item list:
URL = "" href="https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]
4.1 Action items due
4.1.1 none
5. Issues [8:20 am PT]
5.1 APPLIED
5.1.1 ODATA-1132 Propagation of NavigationRestrictions
5.1.2 ODATA-1153 Core.Immutable: clarify that value can be provided *by client* in insert
5.2 V4.01: NEW or OPEN
5.2.1 ODATA-1154 Clarify which OData-Version a service should return
5.2.2 ODATA-1151 Edm.Stream and Nullable
5.2.3 ODATA-1150 Case Sensitivity of Property Names, EntitySets, Singletons and Operations
5.2.4 ODATA-1149 Support Delta responses for Singletons
5.2.5 ODATA-1148 PATCH with nested nav props should not remove omitted resources
5.2.6 ODATA-1141 Upsert: clarify upsert along nullable single-valued navigation path
5.3 Vocabularies: NEW or OPEN with concrete proposal
5.3.1 ODATA-1064 Add ability to annotate collections to return only count and NextLink
5.3.2 ODATA-1072 Annotation to describe supported aggregation methods
5.4 Vocabularies: NEW or OPEN that need more discussion
5.4.1 ODATA-1099 Add annotations to describe custom query options and custom headers
5.4.2 ODATA-1067 Consider ability to define computed default values
5.4.3 ODATA-1005 Make sure we have capabilities for all new 4.01 functionality
5.4.4 ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)
6. Next meetings [9:50 am PT]
6.1 Thursday March 08, 2018 during 8-10 am PST (17:00-19:00 CET)
6.2 Thursday March 15, 2018 during 8-10 am PST (16:00-18:00 CEST) Daylight Saving Time in Central Europe
7. AOB and wrap up [9:55 am PT]
==============================================================
Meeting Member URL:
- URL = "" href="https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46245" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46245
- Please use starting approx. 15 minutes before the meeting for self registration. Thanks.
- Self registration deep link (as a service):
- https://www.oasis-open.org/apps/org/workgroup/odata/record_my_attendance.php?event_id=46245&confirmed=1
[15:38] Stefan Hagen: Ping
[16:15] Stefan Hagen: Ping
[16:53] Stefan Hagen: Ping
[16:57] Gerald Krause (SAP): Pong
Room Information:
OASIS Open Data Protocol (OData) TC OData TC Weekly Meeting (Conference Call) #205
- Thursday, 01 March 2018, 08:00am to 10:00am PST
- i.e. 2018-03-01 17:00 to 19:00 CET (UTC+1)
- other timezone? Try eg.:
- https://www.timeanddate.com/worldclock/meetingdetails.html?year=2018&month=3&day=1&hour=16&min=0&sec=0&p1=47&p2=69&p3=179
UsefulPlaces:
- Chat:
- http://webconf.soaphub.org/conf/room/odatatc # ... this place
- ScreenShare and Voice:
- https://sap.emea.pgiconnect.com/OData-TC/
Next Planned meetings (tentative):
- Thursday March 08, 2018 during 8-10 am PST (17:00-19:00 CET)
- https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46246
- Thursday March 15, 2018 during 8-10 am PST (16:00-18:00 CEST) Daylight Saving Time in Central Europe
- https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46247
Agenda-Draft E-Mail URL:
- E-Mail Public URL = "" href="https://lists.oasis-open.org/archives/odata/201802/msg00105.html" target="_blank">https://lists.oasis-open.org/archives/odata/201802/msg00105.html
Minutes Draft Public URL (previous meeting):
- URL = "" href="https://www.oasis-open.org/committees/download.php/62583/odata-meeting-204_on-20180222-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/62583/odata-meeting-204_on-20180222-minutes.html
Online document walkthroughs or presentations:
- URL = "" href="https://sap.emea.pgiconnect.com/OData-TC/" target="_blank">https://sap.emea.pgiconnect.com/OData-TC/
Timeline(Updated!):
- URL = "" href="https://www.oasis-open.org/committees/download.php/61677/TC%20Timeline-2017-09-29.docx" target="_blank">https://www.oasis-open.org/committees/download.php/61677/TC%20Timeline-2017-09-29.docx
Agenda Draft (for meeting #205):
==============================================================
1. Roll call [8:00 am PT]
1.1 Self-registration link:
URL = "" href="https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46245" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46245
2. Approve agenda [8:05 am PT]
3. Approve minutes from previous meeting(s) [8:10 am PT]
3.1 Minutes from February 22, 2018 TC meeting:
URL = "" href="https://www.oasis-open.org/committees/download.php/62583/odata-meeting-204_on-20180222-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/62583/odata-meeting-204_on-20180222-minutes.html
4. Review action items [Action item list:
URL = "" href="https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]
4.1 Action items due
4.1.1 none
5. Issues [8:20 am PT]
5.1 APPLIED
5.1.1 ODATA-1132 Propagation of NavigationRestrictions
5.1.2 ODATA-1153 Core.Immutable: clarify that value can be provided *by client* in insert
5.2 V4.01: NEW or OPEN
5.2.1 ODATA-1154 Clarify which OData-Version a service should return
5.2.2 ODATA-1151 Edm.Stream and Nullable
5.2.3 ODATA-1150 Case Sensitivity of Property Names, EntitySets, Singletons and Operations
5.2.4 ODATA-1149 Support Delta responses for Singletons
5.2.5 ODATA-1148 PATCH with nested nav props should not remove omitted resources
5.2.6 ODATA-1141 Upsert: clarify upsert along nullable single-valued navigation path
5.3 Vocabularies: NEW or OPEN with concrete proposal
5.3.1 ODATA-1064 Add ability to annotate collections to return only count and NextLink
5.3.2 ODATA-1072 Annotation to describe supported aggregation methods
5.4 Vocabularies: NEW or OPEN that need more discussion
5.4.1 ODATA-1099 Add annotations to describe custom query options and custom headers
5.4.2 ODATA-1067 Consider ability to define computed default values
5.4.3 ODATA-1005 Make sure we have capabilities for all new 4.01 functionality
5.4.4 ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)
6. Next meetings [9:50 am PT]
6.1 Thursday March 08, 2018 during 8-10 am PST (17:00-19:00 CET)
6.2 Thursday March 15, 2018 during 8-10 am PST (16:00-18:00 CEST) Daylight Saving Time in Central Europe
7. AOB and wrap up [9:55 am PT]
==============================================================
Meeting Member URL:
- URL = "" href="https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46245" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46245
- Please use starting approx. 15 minutes before the meeting for self registration. Thanks.
- Self registration deep link (as a service):
- https://www.oasis-open.org/apps/org/workgroup/odata/record_my_attendance.php?event_id=46245&confirmed=1
[17:02] Ralf Handl (SAP SE): Voting Members: 5 of 11 (45%) (used for quorum calculation)
[17:02] Stefan Hagen: Quroum reached: Voting Members: 6 of 11 (54%) (used for quorum calculation)
[17:03] Ralf Handl (SAP SE): Voting Members: 6 of 11 (54%) (used for quorum calculation)
[17:03] Ralf Handl (SAP SE): Quorum achieved: yes
[17:03] Ralf Handl (SAP SE): Waiting for more people to join the telco
[17:03] Ralf Handl (SAP SE): Voting Members: 8 of 11 (72%) (used for quorum calculation)
[17:05] Ralf Handl (SAP SE): 2.Approve agenda [8:05 am PT]
[17:05] Ralf Handl (SAP SE): Mike: timeline and prioritization of next steps
[17:06] Ralf Handl (SAP SE): George: Redfish/Swordfish community seems fine with GitHub-based vocabularies
[17:06] Ralf Handl (SAP SE): No need for Errata 04 from that perspective
[17:07] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1155
[17:07] Ralf Handl (SAP SE): ABNF: allow omitting default namespaces everywhere in the URL
[17:07] Ralf Handl (SAP SE): Agenda is approved with these additions
[17:08] Ralf Handl (SAP SE): 3.Approve minutes from previous meeting(s) [8:10 am PT]
a.Minutes from February 22, 2018 TC meeting:
[17:08] Ralf Handl (SAP SE): https://www.oasis-open.org/apps/org/workgroup/odata/download.php/62583/latest/odata-meeting-204_on-20180222-minutes.html
[17:09] Ralf Handl (SAP SE): Sorry for omitting the link from the agenda
[17:10] Stefan Hagen: (Link always accessible via publication mail to TC mailing list)
[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] [8:15am PT]
a.Action items due
i.none
[17:12] Ralf Handl (SAP SE): 4.5 timeline and prioritization of next steps
[17:12] Ralf Handl (SAP SE): https://www.oasis-open.org/committees/download.php/61677/TC Timeline-2017-09-29.docx
[17:12] Ralf Handl (SAP SE): https://www.oasis-open.org/committees/download.php/61677/TC%20Timeline-2017-09-29.docx
[17:13] Ralf Handl (SAP SE): Whats New in OData Version 4.01
September 2017Approve Whats New in OData Version 4.01 CN02
OData Core and JSON Version 4.01
September 2017Initiate public review of CSD03
November 2017Approve OData Core and JSON Version 4.01 CS01
CSDL JSON Version 4.01
September 2017Initiate public review of CSD02
November 2017Approve CSDL JSON Version 4.01 CS01
[17:14] Ralf Handl (SAP SE): Not achieved
[17:14] Ralf Handl (SAP SE): OData Vocabularies Version 4.0
November 2017Initiate public review of CSD02
January 2018Approve OData Vocabularies Version 4.0 CS01
[17:14] Ralf Handl (SAP SE): OData to OpenAPI Mapping Version 1.0
December 2017Initiate public review of CND02 based on OpenAPI 3.0.0
February 2018Approve OData to OpenAPI Mapping Version 1.0 CN01
[17:14] Ralf Handl (SAP SE): Planned next:
[17:15] Ralf Handl (SAP SE): REST Profile for OData Version 4.01
- February 2018Initiate public review of CND01
- April 2018Approve REST Profile for OData Version 4.01 CN01
[17:15] Ralf Handl (SAP SE): Securing OData Version 4.0
- December 2017Initiate public review of CND01
- February 2018Approve Securing OData Version 4.0 CN01
[17:16] Ralf Handl (SAP SE): Mike: someone needs to prepare proposal for REST Profile
[17:17] Ralf Handl (SAP SE): Mike: OpenAPI mapping might be next
[17:17] Ralf Handl (SAP SE): George: vocabularies almost done
[17:18] Ralf Handl (SAP SE): George: triage remaining vocabulary issues
[17:18] Ralf Handl (SAP SE): 1. Vocabularies
2. OpenAPI Mapping
3. REST Profile
[17:19] Ralf Handl (SAP SE): Ralf to ping Stefan regarding "Securing OData"
[17:19] Ralf Handl (SAP SE): Extension for Data Aggregation Version 4.0
- July 2018Initiate public review of CSD04
- September 2018Approve Extension for Data Aggregation Version 4.0 CS03
[17:21] Ralf Handl (SAP SE): Mike volunteers to prepare a proposal for the REST profile
[17:23] Ralf Handl (SAP SE): Vocabularies: issues resolved and applied by end of march
[17:26] Ralf Handl (SAP SE): OpenAPI mapping: someone (default: Ralf) needs to apply issues identified in last walk-through December 2017
[17:26] Ralf Handl (SAP SE): George: RedFish is also working on an OpenAPI mapping
[17:28] Ralf Handl (SAP SE): George to set up meeting with RedFish folks and Mike
[17:29] Ralf Handl (SAP SE): Mike: take March to update OpenAPI mapping document and potentially work in DMTF feedback
[17:30] Ralf Handl (SAP SE): Mike: initial REST Profile document by mid of April
[17:31] Ralf Handl (SAP SE): Ralf to create action item
[17:32] Ralf Handl (SAP SE): Data Aggregation: walk through "Grid-like Access" sometime within next six weeks to get feedback and direction
[17:34] Ralf Handl (SAP SE): V4.01 CS02
[17:35] Ralf Handl (SAP SE): Mike: keep V4.01 open long enough to get feedback from implementation teams
[17:35] Ralf Handl (SAP SE): Three "statements of use" needed for progressing V4.01 to Candidate OASIS Standard
[17:37] George Ericson (Dell): "OData Essentials" ???
[17:38] Ralf Handl (SAP SE): Nice name!
[17:39] Ralf Handl (SAP SE): Ralf to update timeline accordingly
[17:39] Ralf Handl (SAP SE): 5.Issues [8:20 am PT]
a.APPLIED
i.ODATA-1132 Propagation of NavigationRestrictions
ii.ODATA-1153 Core.Immutable: clarify that value can be provided *by client* in insert
[17:39] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1132
[17:39] Ralf Handl (SAP SE): https://github.com/oasis-tcs/odata-vocabularies/pull/11
[17:41] Ralf Handl (SAP SE): Change: new long description for NavigationRestrictions:
"@Core.LongDescription": "Restrictions specified on an entity set are valid whether the request is directly to the entity set or through a navigation property bound to that entity set. Services can specify a different set of restrictions specific to a path, in which case the more specific restrictions take precedence."
[17:41] Michael Pizzo: I move we close ODATA-1132 as applied.
[17:41] George Ericson (Dell): Second
[17:42] Ralf Handl (SAP SE): No objections, ODATA-1132 is CLOSED as applied
[17:42] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1153
[17:42] Ralf Handl (SAP SE): https://github.com/oasis-tcs/odata-vocabularies/pull/10
[17:43] Ralf Handl (SAP SE): Immutable and ComputedDefaultValue: value can be provided by the client
[17:44] Michael Pizzo: I move we close ODATA-1153 as applied.
[17:44] George Ericson (Dell): Second
[17:44] Ralf Handl (SAP SE): ODATA-1153 is CLOSED as applied
[17:44] Ralf Handl (SAP SE): b.V4.01: NEW or OPEN
[17:44] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1155
[17:45] Ralf Handl (SAP SE): ABNF: allow omitting default namespaces everywhere in the URL
[17:45] Ralf Handl (SAP SE): Relax ABNF to allow omitting namespaces for
- functions
- actions
- type-cast
in
- path
- query options
[17:45] Ralf Handl (SAP SE): But NOT in the context URL.
[17:47] Ralf Handl (SAP SE): ODATA-1155 is OPEN
[17:47] Michael Pizzo: I move we make the ABNF consistent with the prose by resolving ODATA-1155 as proposed.
[17:47] George Ericson (Dell): Second
[17:47] Ralf Handl (SAP SE): ODATA-1155 is RESOLVED as proposed
[17:48] Ralf Handl (SAP SE): i.ODATA-1154 Clarify which OData-Version a service should return
[17:48] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1154
[17:48] Ralf Handl (SAP SE): The service MUST respond with the minimum of the request's OData-MaxVersion, if specified, and the maximum version of the protocol that the service implements.
[17:49] Ralf Handl (SAP SE): ODATA-1154 is OPEN
[17:50] Ralf Handl (SAP SE): Mike: trickier than it seems at first glance
[17:55] Michael Pizzo: Proposed re-wording: The service MUST respond with a payload compliant with the greatest version of the protocol that is less than or equal to the request's OData-MaxVersion, if specified.
[17:56] George Ericson (Dell): Add 'supported'
[17:56] George Ericson (Dell): The service MUST respond with a payload compliant with the greatest supported version of the protocol that is less than or equal to the request's OData-MaxVersion, if specified.
[18:00] Ralf Handl (SAP SE): Mike: potential gap for clients that support only 4:01
[18:14] Ralf Handl (SAP SE): Mike: OData-Version should only tell what was used to generate the request body, not the URL
[18:17] Ralf Handl (SAP SE): Problem are "scared recipients" that stop processing on receiving OData-Version:4.01
[18:19] George Ericson (Dell): Rightly so, since a 4.0 client may not understand a 4.01 response.
[18:19] Michael Pizzo: If a client only understands the 4.0 payload format (in requests, as well as responses) but wants to use a URL construct introduced in 4.01 (which a 4.0 service is allowed to support), then I would want to say that my request is a 4.0 request (because the payload is a 4.0 payload) but use a 4.01 construct.
[18:20] Michael Pizzo: Can either say odata-version only describes the payload, or we can say it describes the request but the request may include compatible extensions introduced in later versions of the payload.
[18:26] Ralf Handl (SAP SE): Mike: distinguish version of protocol and version of format
[18:32] Michael Pizzo: Probably adds unnecessary complexity to try and separately specify payload version and url/protocol version.
[18:33] Ralf Handl (SAP SE): Mike to craft a more detailed proposal
[18:34] Michael Pizzo: Open Questions:
Questions:
1) What if no OData-MaxVersion is specified?
2) Does specifying an OData-Version limit the constructs that the request can use in the URL? i.e., if I have a 4.0 payload, am I restricted to 4.0 URL constructs, even if I know the service supports them?
3) What if the client *only* support 4.01? Do we have a way to specify NOT to return 4.0?
[18:37] Michael Pizzo: 4) Does a service have to return a 4.01 payload if the request uses a 4.01 construct?
[18:39] Ralf Handl (SAP SE): ii.ODATA-1151 Edm.Stream and Nullable
[18:39] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1151
[18:39] Ralf Handl (SAP SE): Can stream properties be nullable?
If yes, how would a null value be represented?
- if expanded: "streamProp":null
- if not expanded: "streamProp@mediaReadLink":null, i.e. no link?
[18:40] Ralf Handl (SAP SE): What if that stream property is directly accessed
[18:41] Ralf Handl (SAP SE): GET es(1)/streamProp
[18:41] Ralf Handl (SAP SE): Would that be 204, 404, or 200 with Content-Length:0
[18:41] Ralf Handl (SAP SE): ODATA-1151 is OPEN
[18:42] Ralf Handl (SAP SE): Mike: expanded representation makes sense
[18:43] Ralf Handl (SAP SE): Mike: you'd need an edit link in order to write/create it
[18:43] Michael Pizzo: Can we say:
Can we say:
1) Expanded returns null
2) Link is always valid, returns 204 if the value is null
[18:44] Ralf Handl (SAP SE): Same behavior as for navigation properties
[18:44] Ralf Handl (SAP SE): Ralf to craft proposal conforming to discussion and nav prop behavior
[18:45] Ralf Handl (SAP SE): iii.ODATA-1150 Case Sensitivity of Property Names, EntitySets, Singletons and Operations
[18:45] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1150
[18:45] Ralf Handl (SAP SE): Proposal:
Interoperable clients SHOULD specify identifiers (in payloads and URLs) in the case they are specified in $metadata.
Services MUST return identifiers (payloads, contextUrl, etc.) in the case defined in $metadata.
Services SHOULD NOT have identifiers within a uniqueness scope that differ only by case.
Services MAY support case-insensitive comparisons of identifiers in URLs and request payloads if no exact match is found, following the existing precedence rules.
[18:46] Ralf Handl (SAP SE): ODATA-1150 is OPEN
[18:49] Ralf Handl (SAP SE): Would prefer MUST for interoperable clients
[18:50] Ralf Handl (SAP SE): Non-interoperable clients are free to send arbitrary requests
[18:51] Ralf Handl (SAP SE): MAY also for 4.01 services
[18:52] Ralf Handl (SAP SE): Mike: not worth defining a capability for this
[18:52] Ralf Handl (SAP SE): Mike: interoperable clients will use $metadata case
[18:53] Michael Pizzo: Updated proposal (just changed "SHOULD" to "MUST" for interoperable clients):
Interoperable clients MUST specify identifiers (in payloads and URLs) in the case they are specified in $metadata.
Services MUST return identifiers (payloads, contextUrl, etc.) in the case defined in $metadata.
Services SHOULD NOT have identifiers within a uniqueness scope that differ only by case.
Services MAY support case-insensitive comparisons of identifiers in URLs and request payloads if no exact match is found, following the existing precedence rules.
[18:54] Michael Pizzo: I move we resolve ODATA-1150 as proposed.
[18:54] Ted Jones (Red Hat): I second
[18:54] Ralf Handl (SAP SE): ODATA-1150 is RESOLVED with the modified proposal
[18:55] Ralf Handl (SAP SE): c.Vocabularies: NEW or OPEN with concrete proposal
i.ODATA-1064 Add ability to annotate collections to return only count and NextLink
[18:55] Ralf Handl (SAP SE): ----------------
Add new example to Prefer header to showing use of count and navigation links
--------------------
To OData Version 4.01. Part 1: Protocol, clause 8.2.8.4 Preference include-annotations (odata.include-annotations)
Add:
Example 8: a Prefer header requesting that navigation links be returned in the case that the format metadata=minimal is specified in the Accept header.
Prefer: include-annotations="odata.navigationLink,odata.count"
Add paragraph before example 3.
Regardless of the metadata format specified, annotations specified by the include-annotations preference should be added to response.
--------------------
Example:
------------------
Proposed schema
<EntityType Name="Top">
<NavigationProperty Name="Systems" Type="Collection(ComputerSystem)"/>
</EntityType>
----------
Example: GET
GET /redfish/v1/Top
Prefer: include-annotations="odata.count,odata.navigationLink"
Response
Preferences-Applied: include-annotations="odata.count,odata.navigationLink"
{
"@odata.context": "/redfish/v1/$metadata#Top",
"@odata.id": "/redfish/v1/Top",
"@odata.type": "#Top ",
"Name": "Top",
"Systems@odata.count": 15,
"Systems@odata.navigationLink": {"/redfish/v1/Systems"}
}
[18:57] Ralf Handl (SAP SE): Current JSON Format spec text:
In addition, the client may use the include-annotations preference in the Prefer header to request additional control information. Services supporting this MUST NOT omit control information required by the chosen metadata parameter, and services MUST NOT exclude the nextLink, deltaLink, and count if they are required by the response type.
[19:00] George Ericson (Dell): Alternative: include-controls preference
[19:02] Ralf Handl (SAP SE): Note: this paragraph was already in V4
[19:04] Ralf Handl (SAP SE): 6.Next meetings [9:50 am PT]
a.Thursday March 08, 2018 during 8-10 am PST (17:00-19:00 CET)
b.Thursday March 15, 2018 during 8-10 am PST (16:00-18:00 CEST) Daylight Saving Time in Central Europe
[19:04] Ralf Handl (SAP SE): Mike might not attend next week
[19:05] Ralf Handl (SAP SE): Mike to send "minimum list" of vocab issues from his perspective
[19:05] Ralf Handl (SAP SE): 7.AOB and wrap up [9:55 am PT]
[19:05] Ralf Handl (SAP SE): The meeting is adjourned
From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org]
On Behalf Of Handl, Ralf
Sent: Montag, 26. Februar 2018 14:31
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2018-03-01
Here [1] is a draft agenda for the OData TC (Technical Committee) meeting
scheduled on
Thursday March 01, 2018 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]
- Self-registration link:
https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46245
2.
Approve agenda [8:05 am PT]
3.
Approve minutes from previous meeting(s) [8:10 am PT]
- Minutes from February 22, 2018 TC meeting:
4.
Review action items [Action item list:
https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]
-
Action items due
i. none
5.
Issues [8:20 am PT]
i. ODATA-1132
Propagation of NavigationRestrictions
ii. ODATA-1153
Core.Immutable: clarify that value can be provided *by client* in insert
-
V4.01:
NEW or OPEN
i. ODATA-1154
Clarify which OData-Version a service should return
ii. ODATA-1151
Edm.Stream and Nullable
iii. ODATA-1150
Case Sensitivity of Property Names, EntitySets, Singletons and Operations
iv. ODATA-1149
Support Delta responses for Singletons
v. ODATA-1148
PATCH with nested nav props should not remove omitted resources
vi. ODATA-1141
Upsert: clarify upsert along nullable single-valued navigation path
-
Vocabularies:
NEW or OPEN with concrete proposal
i. ODATA-1064
Add ability to annotate collections to return only count and NextLink
ii. ODATA-1072
Annotation to describe supported aggregation methods
-
Vocabularies:
NEW or OPEN that need more discussion
i. ODATA-1099
Add annotations to describe custom query options and custom headers
ii. ODATA-1067
Consider ability to define computed default values
iii. ODATA-1005
Make sure we have capabilities for all new 4.01 functionality
iv. ODATA-884
Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)
6.
Next meetings [9:50 am PT]
- Thursday March 08, 2018 during 8-10 am PST (17:00-19:00 CET)
- Thursday March 15, 2018 during 8-10 am PST
(16:00-18:00 CEST) – Daylight Saving Time in Central Europe
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://sap.emea.pgiconnect.com/OData-TC
- Conference call details:
https://www.oasis-open.org/apps/org/workgroup/odata/download.php/56760/TC%20meeting%20dial-in%20details.htm
[3]
Timeline