[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [odata] Agenda for OData TC meeting on 2018-02-15 - chat transcript
[12:37] Room information was updated by: Stefan Hagen OASIS Open Data Protocol (OData) TC OData TC Weekly Meeting (Conference Call) #203
- Thursday, 15 February 2018, 08:00am to 10:00am PST
- i.e. 2018-02-15 17:00 to 19:00 CET (UTC+1)
- other timezone? Try eg.:
- https://www.timeanddate.com/worldclock/meetingdetails.html?year=2018&month=2&day=15&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 February 22, 2018 during 8-10 am PST?
- https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46244
Agenda-Draft E-Mail URL:
- E-Mail Public URL = "" href="https://lists.oasis-open.org/archives/odata/201802/msg00053.html" target="_blank">https://lists.oasis-open.org/archives/odata/201802/msg00053.html
Minutes Draft Public URL (previous meeting):
- URL = "" href="https://www.oasis-open.org/committees/download.php/62475/odata-meeting-202_on-20180208-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/62475/odata-meeting-202_on-20180208-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 #203):
==============================================================
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=46243" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46243
2. Approve agenda [8:05 am PT]
3. Approve minutes from previous meeting(s) [8:10 am PT]
3.1 Minutes from February 08, 2018 TC meeting:
URL = "" href="https://www.oasis-open.org/committees/download.php/62475/odata-meeting-202_on-20180208-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/62475/odata-meeting-202_on-20180208-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. V4.01 Committee Specification 01
5.1 Documents are published
6. V4.0 Errata 04
6.1 ABNF: cross-apply issues such as ODATA-987 Allow digits in search phrases, or just copy V4.01 ABNF over to V4 Errata 04?
6.1.1 Pro: URL Conventions state that ABNF is overly generous and prose specification describes valid constructs, and V4.01 ABNF is super-set of V4
6.1.2 Pro: removes mental barrier for downporting V4.01 features to V4 services/frameworks
6.1.3 Pro: we did the same with the CSDL XML namespaces: http://docs.oasis-open.org/odata/ns/edmx and http://docs.oasis-open.org/odata/ns/edm describe the V4.01 superset.
6.2 XML Schemas for CSDL: pack latest (V4.01) versions into Errata 04?
6.2.1 Pro: see iii. above, XML namespace documents reference V4.01
6.3 Prose Specifications
6.3.1 Any issues that need to be (cross-) applied to the prose specification documents?
6.3.2 Any need to publish Errata 04 for JSON Format?
7. Issues [8:20 am PT]
7.1 APPLIED
7.1.1 ODATA-1144 Allow percent-encoded colon in time values in URLs
7.1 Vocabularies: NEW or OPEN
7.2.1 ODATA-1121 Add FilterExpressionType values "MultiRange" and "MultiRangeOrSearchExpression"
7.2.2 ODATA-1138 Facilitate processing of aggregated results created with concat
7.2.3 ODATA-1099 Add annotations to describe custom query options and custom headers
7.2.4 ODATA-1067 Consider ability to define computed default values
7.2.5 ODATA-1064 Add ability to annotate collections to return only count and NextLink
7.2.6 ODATA-1005 Make sure we have capabilities for all new 4.01 functionality
7.2.7 ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)
7.2.8 ODATA-1147 Annotate a function or action as "availability is advertised per instance"
8. Next meetings [9:50 am PT]
8.1 Thursday February 22, 2018 during 8-10 am PST?
8.2 Thursday March 01, 2018 during 8-10 am PST?
9. 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=46243" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46243
- 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=46243&confirmed=1
[13:11] Stefan Hagen: chat.keep_alive() [14:36] Stefan Hagen: chat.keep_alive() [15:04] Stefan Hagen: chat.keep_alive() [16:06] Stefan Hagen: chat.keep_alive() [16:42] Stefan Hagen1: chat.keep_alive() [16:56] anonymous morphed into George Ericson (Dell) Room Information:
OASIS Open Data Protocol (OData) TC OData TC Weekly Meeting (Conference Call) #203
- Thursday, 15 February 2018, 08:00am to 10:00am PST
- i.e. 2018-02-15 17:00 to 19:00 CET (UTC+1)
- other timezone? Try eg.:
- https://www.timeanddate.com/worldclock/meetingdetails.html?year=2018&month=2&day=15&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 February 22, 2018 during 8-10 am PST?
- https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46244
Agenda-Draft E-Mail URL:
- E-Mail Public URL = "" href="https://lists.oasis-open.org/archives/odata/201802/msg00053.html" target="_blank">https://lists.oasis-open.org/archives/odata/201802/msg00053.html
Minutes Draft Public URL (previous meeting):
- URL = "" href="https://www.oasis-open.org/committees/download.php/62475/odata-meeting-202_on-20180208-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/62475/odata-meeting-202_on-20180208-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 #203):
==============================================================
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=46243" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46243
2. Approve agenda [8:05 am PT]
3. Approve minutes from previous meeting(s) [8:10 am PT]
3.1 Minutes from February 08, 2018 TC meeting:
URL = "" href="https://www.oasis-open.org/committees/download.php/62475/odata-meeting-202_on-20180208-minutes.html" target="_blank">https://www.oasis-open.org/committees/download.php/62475/odata-meeting-202_on-20180208-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. V4.01 Committee Specification 01
5.1 Documents are published
6. V4.0 Errata 04
6.1 ABNF: cross-apply issues such as ODATA-987 Allow digits in search phrases, or just copy V4.01 ABNF over to V4 Errata 04?
6.1.1 Pro: URL Conventions state that ABNF is overly generous and prose specification describes valid constructs, and V4.01 ABNF is super-set of V4
6.1.2 Pro: removes mental barrier for downporting V4.01 features to V4 services/frameworks
6.1.3 Pro: we did the same with the CSDL XML namespaces: http://docs.oasis-open.org/odata/ns/edmx and http://docs.oasis-open.org/odata/ns/edm describe the V4.01 superset.
6.2 XML Schemas for CSDL: pack latest (V4.01) versions into Errata 04?
6.2.1 Pro: see iii. above, XML namespace documents reference V4.01
6.3 Prose Specifications
6.3.1 Any issues that need to be (cross-) applied to the prose specification documents?
6.3.2 Any need to publish Errata 04 for JSON Format?
7. Issues [8:20 am PT]
7.1 APPLIED
7.1.1 ODATA-1144 Allow percent-encoded colon in time values in URLs
7.1 Vocabularies: NEW or OPEN
7.2.1 ODATA-1121 Add FilterExpressionType values "MultiRange" and "MultiRangeOrSearchExpression"
7.2.2 ODATA-1138 Facilitate processing of aggregated results created with concat
7.2.3 ODATA-1099 Add annotations to describe custom query options and custom headers
7.2.4 ODATA-1067 Consider ability to define computed default values
7.2.5 ODATA-1064 Add ability to annotate collections to return only count and NextLink
7.2.6 ODATA-1005 Make sure we have capabilities for all new 4.01 functionality
7.2.7 ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)
7.2.8 ODATA-1147 Annotate a function or action as "availability is advertised per instance"
8. Next meetings [9:50 am PT]
8.1 Thursday February 22, 2018 during 8-10 am PST?
8.2 Thursday March 01, 2018 during 8-10 am PST?
9. 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=46243" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46243
- 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=46243&confirmed=1
[17:03] Ralf Handl (SAP SE): Voting Members: 7 of 11 (63%) (used for quorum calculation) [17:04] Ralf Handl (SAP SE): Achieved quorum: yes [17:04] 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:06] Michael Pizzo: Would also like to discuss: ODATA-1150 Case Sensitivity of Property Names, EntitySets, Singletons and Operations
ODATA-1149 Support Delta responses for Singletons
ODATA-1148 PATCH with nested nav props should not remove omitted resources
[17:07] Michael Pizzo: Can review application of ODATA-1145 in 7a. [17:08] Ralf Handl (SAP SE): George would like to discuss ODATA-1064 first in the Issues section [17:08] Ralf Handl (SAP SE): Agenda is approved with the above modifications [17:08] Ralf Handl (SAP SE): 3.Approve minutes from previous meeting(s) [8:10 am PT] a.Minutes from February 08, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/62475/odata-meeting-202_on-20180208-minutes.html
[17:09] Ralf Handl (SAP SE): Minutes are approved [17:09] 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:09] Ralf Handl (SAP SE): 5.V4.01 Committee Specification 01 a.Documents are published
[17:10] Ralf Handl (SAP SE): 6.V4.0 Errata 04 [17:10] Ralf Handl (SAP SE): a.ABNF: cross-apply issues such as ODATA-987 Allow digits in search phrases, or just copy V4.01 ABNF over to V4 Errata 04? i.Pro: URL Conventions state that ABNF is overly generous and prose specification describes valid constructs, and V4.01 ABNF is super-set of V4
ii.Pro: removes mental barrier for downporting V4.01 features to V4 services/frameworks
iii.Pro: we did the same with the CSDL XML namespaces: http://docs.oasis-open.org/odata/ns/edmx and http://docs.oasis-open.org/odata/ns/edm describe the V4.01 superset.
[17:16] Ralf Handl (SAP SE): Mike: if we do this, we should comment that in the ABNF, e.g. for key-as-segment or optional $ in query option names [17:19] Michael Pizzo: I move we merge the 4.01 extensions into the OData 4.0 ABNF and maintain a common ABNF across versions. [17:19] George Ericson (Dell): Second [17:19] Ralf Handl (SAP SE): No objections, motion passes [17:19] Ralf Handl (SAP SE): b.XML Schemas for CSDL: pack latest (V4.01) versions into Errata 04? i.Pro: see iii. above, XML namespace documents reference V4.01
[17:21] Ralf Handl (SAP SE): c.Prose Specifications i.Any issues that need to be (cross-) applied to the prose specification documents?
ii.Any need to publish Errata 04 for JSON Format?
[17:26] Ralf Handl (SAP SE): Mike: can we reference the V4.01 vocabularies in GitHub from Errata 04? [17:27] Ralf Handl (SAP SE): Ralf to ask Chet whether/how this can be done [17:30] Ralf Handl (SAP SE): 7.Issues [8:20 am PT] [17:31] Ralf Handl (SAP SE): a.APPLIED [17:31] Ralf Handl (SAP SE): later [17:31] Ralf Handl (SAP SE): b.Vocabularies: NEW or OPEN [17:31] Ralf Handl (SAP SE): v.ODATA-1064 Add ability to annotate collections to return only count and NextLink [17:33] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1064 [17:33] Ralf Handl (SAP SE): Add new IncludeMetadata term: ----------------
<Term Name="IncludeMetadata" AppliesTo="NavigationProperty EntitySet Singleton" Type="Core.MetadataKind">
<Annotation Term="Core.Description"
String="Defines metadata that should automatically be returned in a response when the reply is qualified with 'metadata=minimal'." />
</Term>
<EnumType Name="MetadataKind" IsFlags="true">
<Member Name="count" Value="1">
<Annotation Term="Core.Description"
String="Return count metadata, equivalent to $count." />
</Member>
<Member Name="navigationLink" Value="2">
<Annotation Term="Core.Description"
String="This URL can be used to retrieve an entity or collection of entities related to the current entity via a navigation property. Doing a GET on this link is equivalent to specifying $expand."/>
</Member>
<Member Name="associationLink" Value="4">
<Annotation Term="Core.Description"
String=" The value is a URL that can be used to retrieve a reference to an entity or a collection of references to entities related to the current entity via a navigation property. Doing a GET on this link is equivalent to specifying $ref." />
</Member>
</EnumType>
[17:59] Michael Pizzo: We could introduce modifiers to the application/json metadata parameter; i.e., application/json;metadata=minimal+navigationLink. [17:59] Ralf Handl (SAP SE): i.ODATA-1121 Add FilterExpressionType values "MultiRange" and "MultiRangeOrSearchExpression" [18:00] Michael Pizzo: ideally, we wouldn't have to advertise all variations of the added modifiers; a service that supported application/json;metadata=minimal would implicitly support the modifiers. [18:00] Ralf Handl (SAP SE): a.APPLIED i.ODATA-1144 Allow percent-encoded colon in time values in URLs
[18:03] Ralf Handl (SAP SE): V4.01: https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/4.01%20spec/ABNF/odata-abnf-construction-rules.txt?op=diff&rev=1121
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/4.01%20spec/ABNF/odata-abnf-testcases.xml?op=diff&rev=1121
V4:
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-aggregation-abnf.txt?op=diff&rev=1122
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-aggregation-testcases.xml?op=diff&rev=1122
[18:10] Ralf Handl (SAP SE): Hubert: there's a left-over ":" in the offset portion of rule dateTimeOffsetValueInUrl [18:10] Ralf Handl (SAP SE): Postponed to next meeting [18:10] Michael Pizzo: https://github.com/oasis-tcs/odata-vocabularies/pull/7 [18:10] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1145 [18:16] Ralf Handl (SAP SE): Mike walks us through the changes [18:17] Hubert Heijkers (IBM): I move to close ODATA-1145 as applied. [18:17] Michael Pizzo: I second [18:18] Ralf Handl (SAP SE): ODATA-1145 is CLOSED as applied [18:18] Ralf Handl (SAP SE): b.Vocabularies: NEW or OPEN i.ODATA-1121 Add FilterExpressionType values "MultiRange" and "MultiRangeOrSearchExpression"
[18:19] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1121 [18:20] Ralf Handl (SAP SE): Add new allowed values <Record>
<PropertyValue Property="Value" String="MultiRange" />
<Annotation Term="Core.Description" String="Property can be compared to a union of one or more closed, half-open, or open intervals" />
<Annotation Term="Core.LongDescription" String="The filter _expression_ for this property consists of one or more interval expressions combined by OR. A single interval _expression_ is either a single comparison of the property and a literal value with eq, le, lt, ge, or gt, or pair of boundaries combined by AND and enclosed in parentheses. The lower boundary is either ge or gt, the upper boundary either le or lt." />
</Record>
<Record>
<PropertyValue Property="Value" String="MultiRangeOrSearchExpression" />
<Annotation Term="Core.Description" String="Property can be compared to a union of zero or more closed, half-open, or open intervals plus zero or more simple string patters" />
<Annotation Term="Core.LongDescription" String="The filter _expression_ for this property consists of one or more interval expressions or string comparison functions combined by OR. See MultiRange for a definition of an interval _expression_. See SearchExpression for the allowed string comparison functions." />
</Record>
[18:21] Ralf Handl (SAP SE): <TypeDefinition Name="FilterExpressionType" UnderlyingType="Edm.String"> <Annotation Term="Validation.AllowedValues">
<Collection>
<Record>
<PropertyValue Property="Value" String="SingleValue" />
<Annotation Term="Core.Description" String="Property can be used in a single eq clause" />
</Record>
<Record>
<PropertyValue Property="Value" String="MultiValue" />
<Annotation Term="Core.Description" String="Property can be used in a single in clause" />
</Record>
<Record>
<PropertyValue Property="Value" String="SingleRange" />
<Annotation Term="Core.Description" String="Property can be used in at most one ge and/or one le clause, separated by and" />
</Record>
<Record>
<PropertyValue Property="Value" String="SearchExpression" />
<Annotation Term="Core.Description"
String="String property can be used as first operand in startswith, endswith, and contains clauses" />
</Record>
</Collection>
</Annotation>
</TypeDefinition>
[18:28] Ralf Handl (SAP SE): I move to resolve ODATA-1121 as proposed [18:29] Hubert Heijkers (IBM): I second [18:30] Ralf Handl (SAP SE): ODATA-1121 is RESOLVED as proposed [18:30] Ralf Handl (SAP SE): ii.ODATA-1138 Facilitate processing of aggregated results created with concat [18:30] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1138 [18:32] Gerald Krause (SAP): GET ~/Sales?$apply=concat( filter(<complex _expression_ 1>)/groupby((Customer),aggregate(Amount with sum as Total)),
filter(<complex _expression_ 2>)/groupby((Customer),aggregate(Amount with sum as Total)))
[18:34] Gerald Krause (SAP): <Term Name=RelatedConcatParameter Type=Edm.Int16> <Annotation Term="Core.Description" String="Position of the transformation sequence in the list of concat parameters, whose result contans this entity. Position counting starts at 0" />
</Term>
[18:35] Gerald Krause (SAP): <Term Name=ResultOfConcatArgument Type=Edm.Int16> <Annotation Term="Core.Description" String="Index number of the argument provided to the concat transformation whose result contains this and subsequent entities. The first argument has index 0." />
</Term>
[18:40] Gerald Krause (SAP): concat(filter(...)/groupby(...)/compute(1 as idx), ...) [18:44] Gerald Krause (SAP): I move to close ODATA-1138 as proposed [18:46] Ralf Handl (SAP SE): iii.ODATA-1099 Add annotations to describe custom query options and custom headers [18:47] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1099 [18:49] Ralf Handl (SAP SE): Postponed [18:49] Ralf Handl (SAP SE): iv.ODATA-1067 Consider ability to define computed default values [18:49] Ralf Handl (SAP SE): Mike: skip remaining Vocabulary issues [18:50] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1148 [18:50] Ralf Handl (SAP SE): PATCH with nested nav props should not remove omitted resources [18:51] Ralf Handl (SAP SE): viii.ODATA-1147 Annotate a function or action as "availability is advertised per instance" [18:51] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1147 [18:51] Ralf Handl (SAP SE): Actions and functions are by default available for all instances unless stated otherwise. One way to state this is the term Core.OperationAvailable which currently has to evaluate to true or false.
What is missing is a way to say "availability of this operation cannot be determined up-front, please look into the availability advertising in its representation".
[18:55] Ralf Handl (SAP SE): Mike: it already is nullable because there's no Nullable="false" attribute [18:55] Ralf Handl (SAP SE): ODATA-1147 is OPEN [18:55] Ralf Handl (SAP SE): I move to resolve ODATA-1147 as proposed [18:55] Michael Pizzo: I second [18:55] Ralf Handl (SAP SE): ODATA-1147 is RESOLVED as proposed [19:01] Ralf Handl (SAP SE): 8.Next meetings [9:50 am PT] a.Thursday February 22, 2018 during 8-10 am PST?
b.Thursday March 01, 2018 during 8-10 am PST?
[19:02] Ralf Handl (SAP SE): Mike can't make a. [19:02] Ralf Handl (SAP SE): Hubert can make a but not b [19:02] Ralf Handl (SAP SE): Then its a and b [19:03] Ralf Handl (SAP SE): 9.AOB and wrap up [9:55 am PT] [19:03] Ralf Handl (SAP SE): Meeting is adjourned From: Handl, Ralf 7.b.viii: new issue
ODATA-1147 - Annotate a function or action as "availability is advertised per instance" From: odata@lists.oasis-open.org [mailto: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 15, 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]
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] [8:15am PT]
i. none
5.
V4.01 Committee Specification 01
6.
V4.0 Errata 04
i. Pro: URL Conventions state that ABNF is overly generous and prose specification describes valid
constructs, and V4.01 ABNF is super-set of V4
ii. Pro: removes mental barrier for “downporting” V4.01 features to V4 services/frameworks
iii. Pro: we did the same with the CSDL XML namespaces:
http://docs.oasis-open.org/odata/ns/edmx and
http://docs.oasis-open.org/odata/ns/edm describe the V4.01 superset.
i. Pro: see iii. above, XML namespace documents reference V4.01
i. Any issues that need to be (cross-) applied to the prose specification documents?
ii. Any need to publish Errata 04 for JSON Format?
7.
Issues [8:20 am PT]
i. ODATA-1144
Allow percent-encoded colon in time values in URLs
i. ODATA-1121
Add FilterExpressionType values "MultiRange" and "MultiRangeOrSearchExpression"
ii. ODATA-1138
Facilitate processing of aggregated results created with concat
iii. ODATA-1099
Add annotations to describe custom query options and custom headers
iv. ODATA-1067
Consider ability to define computed default values
v. ODATA-1064
Add ability to annotate collections to return only count and NextLink
vi. ODATA-1005
Make sure we have capabilities for all new 4.01 functionality
vii. ODATA-884
Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)
viii. ODATA-1147
Annotate a function or action as "availability is advertised per instance"
8.
Next meetings [9:50 am PT]
9.
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]