OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [odata] Agenda for OData TC meeting on 2017-01-19 - chat transcript


[15:47] Room information was updated by: Stefan Hagen
OASIS Open Data Protocol (OData) TC OData TC Weekly Meeting (Conference Call) #158
- Thursday, 19 January 2017, 08:00am to 10:00am PT
  - i.e. 2017-01-19 17:00 to 19:00 CET (UTC+1)
 
Meeting Member URL:
- URL = "">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43961
  - Please use starting approx. 15 minutes before the meeting for self registration. Thanks.
 
Agenda-Draft E-Mail URL:
- E-Mail Public URL = "">https://lists.oasis-open.org/archives/odata/201701/msg00052.html
 
Minutes Draft Public URL (previous meeting):
- URL = "">https://www.oasis-open.org/committees/download.php/59782/odata-meeting-157_on-20170112-minutes.html
 
Online document walkthroughs or presentations:
- URL = "">https://sap.emea.pgiconnect.com/OData-TC/
 
Timeline:
- URL = "">https://www.oasis-open.org/committees/download.php/59831/TC%20Timeline-2017-01-19.docx
 
Agenda Draft (for meeting #15http://webconf.soaphub.org/conf/images/glasses.gif:
- Roll call
- Approve agenda 
- Approve minutes from previous meeting(s)
  - Minutes from January 12, 2016 TC meeting #157: https://www.oasis-open.org/committees/download.php/59782/odata-meeting-157_on-20170112-minutes.html
- Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php]
  - Action items due
    - None
- TC Timeline
  - Topics for this year
    - OData Core and JSON Version 4.01 CSD01 and CS01
    - Whats New in OData Version 4.01 (CND01 and) CN01
      - Do we want to publish a Note Draft or directly a Note?
    - CSDL JSON Version 4.01 CSD01, 
    - OData to OpenAPI Mapping Version 4.0 CND01 and CN01
    - Extension for Temporal Data Version 4.0 CSD01, 
    - REST Profile for OData Version 4.01 CND01 and CN01
    - ... ?
- V4.0 ERRATA04
  - How to deal with errors/clarifications in V4.0 ERRATA03: plan for ERRATA04 or fix them in V4.01 only?
  - Issues for V4.0_ERRATA04 in New or Open state
    - ODATA-955 Specifying odata.type on a collection of entities
    - ODATA-1024 5.1.1.5.7 substring: explicitly state that the index N (second parameter value) is zero-based
    - ODATA-1026 Clarify when $it is required
- V4.01
  - Issues for V4.01_CSD02 without assignee
    - ODATA-955 Specifying odata.type on a collection of entities
    - ODATA-1018 Allow $expand and $select with modifying requests that return a collection in combination with return=representation to specify the response shape
    - ODATA-1019 Add term Core.OptionallyComputed or Core.ComputedDefault
    - ODATA-1020 Remove / in reference in instance annotation in filter and orderby _expression_
    - ODATA-1021 Are additional values needed for the reason property of a removed Annotation
    - ODATA-1022 Add an example of a delta payload used in a PATCH request to the Delta Payload section
    - ODATA-1023 Provide stable anchors to all sections
    - ODATA-1024 5.1.1.5.7 substring: explicitly state that the index N (second parameter value) is zero-based
    - ODATA-1025 Treatment of same query option in multiple "spellings"
    - ODATA-1026 Clarify when $it is required
 
  - Issues for V4.01_CSD02 ready for resolution
    - ODATA-817 Add client-side function odata.matchesRegularExpression
    - ODATA-1008 Consider deprecating symbolic "max" length
    - ODATA-1013 Selected nav props in a defining query should specify interest in added/deleted links
    - ODATA-1017 Extend FilterExpressionRestrictions with "Pattern"
 
  - Issues for V4.01_CSD02 in New or Open state without concrete proposal
    - ODATA-674 Specify navigation property binding combined with containment
    - ODATA-760 Add to depth restrictions to Capabilities Vocabulary
    - ODATA-854 Consider use of OPTIONS for discovering formats, other capabilities and features
    - ODATA-868 Describe HTTP encoding for streamed requests and responses
    - ODATA-879 Support Arrays of Arrays
    - ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)
    - ODATA-919 Specify the result type for each operation based on operator types
    - ODATA-920 Specify overflow for int data types (-INF, INF, NaN)
    - ODATA-923 $expand (or $include) for $metadata to include referenced schemas
    - ODATA-950 Clarify what requests can be delta enabled
    - ODATA-962 CORS Support
    - ODATA-994 consider replacing SchemaVersion header with $SchemaVersion query option, or root URL versioning
    - ODATA-1002 Add build in functions operating on collections of primitive (and complex?) types
    - ODATA-1003 Allow casting of entities and complex type instances to arbitrary structural type
    - ODATA-1005 Make sure we have capabilities for all new 4.01 functionality
    - ODATA-1011 Security experts at RSA suggest adding guidance on the use of OAuth and openID
- Next meeting
  - Thursday January 26, 2017 during 8-10 am PST (2017-01-26 17:00 to 19:00 UTC) ?
- AOB and wrap up

 

[16:48] Stefan Hagen: PI[Voting Members: 1 of 11 (9%) (used for quorum calculation) ]
[16:55] Stefan Hagen: PI[Voting Members: 1 of 11 (9%) (used for quorum calculation) ]
[16:56] Stefan Hagen: PI[Voting Members: 2 of 11 (18%) (used for quorum calculation) ]
[16:59] Stefan Hagen: PI[Voting Members: 4 of 11 (36%) (used for quorum calculation) ]

 

Room Information:
OASIS Open Data Protocol (OData) TC OData TC Weekly Meeting (Conference Call) #158
- Thursday, 19 January 2017, 08:00am to 10:00am PT
  - i.e. 2017-01-19 17:00 to 19:00 CET (UTC+1)
 
Meeting Member URL:
- URL = "">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43961
  - Please use starting approx. 15 minutes before the meeting for self registration. Thanks.
 
Agenda-Draft E-Mail URL:
- E-Mail Public URL = "">https://lists.oasis-open.org/archives/odata/201701/msg00052.html
 
Minutes Draft Public URL (previous meeting):
- URL = "">https://www.oasis-open.org/committees/download.php/59782/odata-meeting-157_on-20170112-minutes.html
 
Online document walkthroughs or presentations:
- URL = "">https://sap.emea.pgiconnect.com/OData-TC/
 
Timeline:
- URL = "">https://www.oasis-open.org/committees/download.php/59831/TC%20Timeline-2017-01-19.docx
 
Agenda Draft (for meeting #15http://webconf.soaphub.org/conf/images/glasses.gif:
- Roll call
- Approve agenda 
- Approve minutes from previous meeting(s)
  - Minutes from January 12, 2016 TC meeting #157: https://www.oasis-open.org/committees/download.php/59782/odata-meeting-157_on-20170112-minutes.html
- Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php]
  - Action items due
    - None
- TC Timeline
  - Topics for this year
    - OData Core and JSON Version 4.01 CSD01 and CS01
    - Whats New in OData Version 4.01 (CND01 and) CN01
      - Do we want to publish a Note Draft or directly a Note?
    - CSDL JSON Version 4.01 CSD01, 
    - OData to OpenAPI Mapping Version 4.0 CND01 and CN01
    - Extension for Temporal Data Version 4.0 CSD01, 
    - REST Profile for OData Version 4.01 CND01 and CN01
    - ... ?
- V4.0 ERRATA04
  - How to deal with errors/clarifications in V4.0 ERRATA03: plan for ERRATA04 or fix them in V4.01 only?
  - Issues for V4.0_ERRATA04 in New or Open state
    - ODATA-955 Specifying odata.type on a collection of entities
    - ODATA-1024 5.1.1.5.7 substring: explicitly state that the index N (second parameter value) is zero-based
    - ODATA-1026 Clarify when $it is required
- V4.01
  - Issues for V4.01_CSD02 without assignee
    - ODATA-955 Specifying odata.type on a collection of entities
    - ODATA-1018 Allow $expand and $select with modifying requests that return a collection in combination with return=representation to specify the response shape
    - ODATA-1019 Add term Core.OptionallyComputed or Core.ComputedDefault
    - ODATA-1020 Remove / in reference in instance annotation in filter and orderby _expression_
    - ODATA-1021 Are additional values needed for the reason property of a removed Annotation
    - ODATA-1022 Add an example of a delta payload used in a PATCH request to the Delta Payload section
    - ODATA-1023 Provide stable anchors to all sections
    - ODATA-1024 5.1.1.5.7 substring: explicitly state that the index N (second parameter value) is zero-based
    - ODATA-1025 Treatment of same query option in multiple "spellings"
    - ODATA-1026 Clarify when $it is required
 
  - Issues for V4.01_CSD02 ready for resolution
    - ODATA-817 Add client-side function odata.matchesRegularExpression
    - ODATA-1008 Consider deprecating symbolic "max" length
    - ODATA-1013 Selected nav props in a defining query should specify interest in added/deleted links
    - ODATA-1017 Extend FilterExpressionRestrictions with "Pattern"
 
  - Issues for V4.01_CSD02 in New or Open state without concrete proposal
    - ODATA-674 Specify navigation property binding combined with containment
    - ODATA-760 Add to depth restrictions to Capabilities Vocabulary
    - ODATA-854 Consider use of OPTIONS for discovering formats, other capabilities and features
    - ODATA-868 Describe HTTP encoding for streamed requests and responses
    - ODATA-879 Support Arrays of Arrays
    - ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)
    - ODATA-919 Specify the result type for each operation based on operator types
    - ODATA-920 Specify overflow for int data types (-INF, INF, NaN)
    - ODATA-923 $expand (or $include) for $metadata to include referenced schemas
    - ODATA-950 Clarify what requests can be delta enabled
    - ODATA-962 CORS Support
    - ODATA-994 consider replacing SchemaVersion header with $SchemaVersion query option, or root URL versioning
    - ODATA-1002 Add build in functions operating on collections of primitive (and complex?) types
    - ODATA-1003 Allow casting of entities and complex type instances to arbitrary structural type
    - ODATA-1005 Make sure we have capabilities for all new 4.01 functionality
    - ODATA-1011 Security experts at RSA suggest adding guidance on the use of OAuth and openID
- Next meeting
  - Thursday January 26, 2017 during 8-10 am PST (2017-01-26 17:00 to 19:00 UTC) ?
- AOB and wrap up

 

[17:01] Stefan Hagen: PI[Voting Members: 4 of 11 (36%) (used for quorum calculation) ]
[17:01] Stefan Hagen: PI[Voting Members: 6 of 11 (54%) (used for quorum calculation)] - I guess quorate http://webconf.soaphub.org/conf/images/smile.gif
[17:04] Stefan Hagen: PI[Voting Members: 9 of 11 (81%) (used for quorum calculation) ]

 

[17:04] Ralf Handl (SAP SE): 2.Approve agenda [8:05 am PT]
[17:06] Ralf Handl (SAP SE): Mike opened a new issue ODATA-1027
Support instance annotations in $orderby, add it to 7.b.
[17:06] Ralf Handl (SAP SE): Agenda is approved
[17:06] Ralf Handl (SAP SE): 3.Approve minutes from previous meeting(s) [8:10 am PT]
a.Minutes from January 12, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/59782/odata-meeting-157_on-20170112-minutes.html
[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] [8:15am PT]
a.Action items due
i.None
[17:07] Ralf Handl (SAP SE): 5.TC Timeline [8:16 am PT]
a.Topics for this year
i.OData Core and JSON Version 4.01 CSD01 and CS01
ii.Whats New in OData Version 4.01 (CND01 and) CN01
1.Do we want to publish a Note Draft or directly a Note?
iii.CSDL JSON Version 4.01 CSD01, 
iv.OData to OpenAPI Mapping Version 4.0 CND01 and CN01
v.Extension for Temporal Data Version 4.0 CSD01, 
vi.REST Profile for OData Version 4.01 CND01 and CN01
vii.?
[17:09] Ralf Handl (SAP SE): Gerald: vii. Extension for Data Aggregation
[17:09] Ralf Handl (SAP SE): Close open issues
[17:09] Ralf Handl (SAP SE): Add enhanced hierarchy handling
[17:11] Ralf Handl (SAP SE): ii.Whats New in OData Version 4.01 (CND01 and) CN01
[17:11] Ralf Handl (SAP SE): Stefan: directly publish CN01
[17:11] Ralf Handl (SAP SE): Mike: may be useful for reviewers of V4.01, so publish it together with CSD02
[17:13] Ralf Handl (SAP SE): Timeline:
- URL = "">https://www.oasis-open.org/committees/download.php/59831/TC%20Timeline-2017-01-19.docx
[17:20] Ralf Handl (SAP SE): Do Data Aggregation in parallel to CSDL JSON
[17:22] Ralf Handl (SAP SE): 6.V4.0 ERRATA04 [9:00 am PT]
a.How to deal with errors/clarifications in V4.0 ERRATA03: plan for ERRATA04 or fix them in V4.01 only?
b.Issues for V4.0_ERRATA04 in New or Open state
i.ODATA-955 Specifying odata.type on a collection of entities
ii.ODATA-1024 5.1.1.5.7 substring: explicitly state that the index N (second parameter value) is zero-based
iii.ODATA-1026 Clarify when $it is required
[17:24] Ralf Handl (SAP SE): Mike: not "backporting" issue resolutions to ERRATA04 will save a lot of work, make instead V4.01 the "current" document set
[17:25] Ralf Handl (SAP SE): Mike: can the "latest" link for V4 point to V4.01? Ralf to clarify with TC Admin.
[17:27] Ralf Handl (SAP SE): All agree to apply issues to V4.01 only from now on.
[17:27] Ralf Handl (SAP SE): 7.V4.01 [9:20 am PT]
a.Issues for V4.01_CSD02 without assignee
i.ODATA-955 Specifying odata.type on a collection of entities
[17:29] Ralf Handl (SAP SE): ODATA-955 is OPEN

 

[17:29] Mike Pizzo: I move we resolve ODATA-955 as proposed.

 

[17:29] Stefan Hagen: second

 

[17:29] Ralf Handl (SAP SE): ODATA-955 is RESOLVED as proposed
[17:29] Ralf Handl (SAP SE): ii.ODATA-1018 Allow $expand and $select with modifying requests that return a collection in combination with return=representation to specify the response shape
[17:31] Ralf Handl (SAP SE): Mike: will need more discussion
[17:31] Ralf Handl (SAP SE): Assign to Mike
[17:32] Ralf Handl (SAP SE): iii.ODATA-1019 Add term Core.OptionallyComputed or Core.ComputedDefault
[17:33] Ralf Handl (SAP SE): Assign to Ralf
[17:34] Ralf Handl (SAP SE): iv.ODATA-1020 Remove / in reference in instance annotation in filter and orderby _expression_
[17:35] Ralf Handl (SAP SE): Assign to Hubert
[17:35] Ralf Handl (SAP SE): v.ODATA-1021 Are additional values needed for the reason property of a removed Annotation
[17:36] Ralf Handl (SAP SE): Matt will take this
[17:36] Ralf Handl (SAP SE): vi.ODATA-1022 Add an example of a delta payload used in a PATCH request to the Delta Payload section
[17:38] Ralf Handl (SAP SE): ODATA-1022 is OPEN

 

[17:38] Stefan Hagen: I move to resolve ODATA-1022 as proposed and regard as pure editorial addition.

 

[17:38] Matt Borges (SAP): i second

 

[17:39] Ralf Handl (SAP SE): ODATA-1022 is RESOLVED
[17:39] Ralf Handl (SAP SE): vii.ODATA-1023 Provide stable anchors to all sections
[17:39] Ralf Handl (SAP SE): ODATA-1022 is OPEN

 

[17:40] Mike Pizzo: I move we resolve ODATA-1022 as proposed

 

[17:40] Stefan Hagen: second

 

[17:40] Ralf Handl (SAP SE): ODATA-1022 is RESOLVED

 

[17:41] Stefan Hagen: the last lines targeted ODATA-1023 http://webconf.soaphub.org/conf/images/wink.gif

 

[17:42] Ralf Handl (SAP SE): viii.ODATA-1024 5.1.1.5.7 substring: explicitly state that the index N (second parameter value) is zero-based
[17:43] Ralf Handl (SAP SE): ODATA-1024 is OPEN

 

[17:44] Mike Pizzo: I propose we resolve ODATA-1024 as proposed

 

[17:44] Gerald Krause (SAP): I second

 

[17:44] Ralf Handl (SAP SE): ODATA-1024 is RESOLVED
[17:44] Ralf Handl (SAP SE): ODATA-1025 Treatment of same query option in multiple "spellings"
[17:45] Ralf Handl (SAP SE): ODATA-1025 is OPEN
[17:45] Ralf Handl (SAP SE): In Section 5.1, System Query Options], of URL Conventions, change: 
 
 "The same system query option MUST NOT be specified more than once for any resource." 
 
to: 
 
"The same system query option, irrespective of casing or whether or not it is prefixed with "$", MUST NOT be specified more than once for any resource."

 

[17:46] Stefan Hagen: I move to resolve ODATA-1025 AS PROPOSE

 

[17:46] Ramesh Reddy (Red Hat): second

 

[17:46] Mike Pizzo: I second

 

[17:47] Ralf Handl (SAP SE): ODATA-1025 is RESOLVED as proposed
[17:47] Ralf Handl (SAP SE): x.ODATA-1026 Clarify when $it is required
[17:47] Ralf Handl (SAP SE): Description:
The description of $it says it CAN be used in a number of cases (see section 5.1.11.4 in the URL conventions document) but it isn't specific about when $it MUST be used. We should clarify when $it is required. For example, my understanding is that both of these queries are equivalent (in which case the $it is not required): 
 
http://host/service/Customers?$filter=Orders/any(d:d/Quantity ge Age) 
vs. 
http://host/service/Customers?$filter=Orders/any(d:d/Quantity ge $it/Age) 
 
However, my understanding is that in the case below the $it is required: 
 
http://host/service/Customers?$expand=Orders($filter=$it/Address/City eq ShipTo/City)
[17:48] Ralf Handl (SAP SE): ODATA-1026 is OPEN
[17:50] Ralf Handl (SAP SE): Michael Pizzo added a comment - Yesterday 11:57 PM
$it allows referencing the resource identified by the resource path. unqualified property references reference the current "scope". These may be the same thing in a simple request, but are not the same within a $expand (where an unqualified property reference references a property on the expanded nav prop). So in: 
http://host/service/Customers?$expand=Orders($filter=$it/Address/City eq ShipTo/City) 
Address would refer to a property on a Customer and ShipTo would refer to a property on an Order. 
 
$it is also used: 
-when referencing the resource itself (not a property of the resource), and 
-when invoking a function or action bound to the resource (to distinguish from an unbound action or function)

 

[17:54] Matt Borges (SAP): I move we resolve ODATA-1026 as proposed in Mike's comment

 

[17:55] Mike Pizzo: I second

 

[17:55] Ralf Handl (SAP SE): ODATA-1026 is RESOLVED according to Mike's comment
[17:55] Ralf Handl (SAP SE): b.Issues for V4.01_CSD02 ready for resolution
i.ODATA-817 Add client-side function odata.matchesRegularExpression

 

[18:00] Stefan Hagen: I move to resolve ODATA-1026 as proposed.

 

[18:00] Mike Pizzo: I second

 

[18:01] Stefan Hagen: I move to resolve ODATA-817 as proposed.

 

[18:01] Mike Pizzo: I second

 

[18:01] Ralf Handl (SAP SE): ODATA-817 is RESOLVED as proposed
[18:01] Ralf Handl (SAP SE): ii.ODATA-1008 Consider deprecating symbolic "max" length

 

[18:02] Stefan Hagen: Stefan'S bove duplicate motion for ODATA-1026 shall be disregarded, ODATA-817 is correct.

 

[18:02] Ralf Handl (SAP SE): Proposal:
Instead of an integer value the constant max MAY be specified as a shorthand for the maximum length supported for the type by the service. Responses for OData version 4.01 or later MUST/SHOULD NOT use the symbolic value max and instead specify the concrete maximum length supported for the type by the service.
[18:02] Ralf Handl (SAP SE): The OData 4.0 use of the symbolic value max in place of an integer value is deprecated in OData 4.01. While OData 4.0 clients MUST be prepared for this value, OData 4.01 and greater services MUST NOT return a value of max for the MaxLength attribute and MAY instead specify the concrete maximum length supported for the type by the service, or omit the attribute entirely.

 

[18:04] Matt Borges (SAP): I move we resolve ODATA-1008 as proposed in Mike's comment

 

[18:04] Ramesh Reddy (Red Hat): I second

 

[18:04] Ralf Handl (SAP SE): ODATA-1008 is RESOLVED as proposed
[18:04] Ralf Handl (SAP SE): iii.ODATA-1013 Selected nav props in a defining query should specify interest in added/deleted links
[18:05] Ralf Handl (SAP SE): Proposal:
 
Nav properties specified in the select list of a defining query define the links for which the client is interested in receiving notifications. 
 
Delta responses contain AddedLinks and DeletedLinks entries for navigation properties specified in the select list of the defining request.
[18:07] Ralf Handl (SAP SE): ODATA-1013 is OPEN
[18:11] Ralf Handl (SAP SE): Mike: alternatively use $expand=NavProp/$ref
[18:11] Ralf Handl (SAP SE): Matt agrees

 

[18:16] Mike Pizzo: Updated proposal: Nav properties specified in the select list of a defining query are not used to define the scope or contents of the items being tracked. Clients can specify /$ref in order to specify interest in the set of related entities without interest in changes to the content of those related entities.
 
Delta responses contain AddedLinks and DeletedLinks entries (or, for nested collections, (at least) entity references representing the current membership) for navigation properties expanded with $ref in the defining request.

 

[18:19] Ralf Handl (SAP SE): Mike to craft a revised proposal
[18:20] Ralf Handl (SAP SE): iv.ODATA-1017 Extend FilterExpressionRestrictions with "Pattern"
[18:20] Ralf Handl (SAP SE): FilterExpressionRestrictionType
 
PropertyTypeDescription
PropertyPropertyPathPath to the restricted property
AllowedExpressionsFilterExpressionTypeAllowed subset of expressions
 
 
FilterExpressionType
 
Type: String
 
Allowed ValueDescription
SingleValueProperty can be used in a single eq clause
MultiValueProperty can be used in a single in clause
SingleRangeProperty can be used in at most one ge and/or one le clause, separated by and
[18:22] Ralf Handl (SAP SE): Proposal:
Add new allowed value 
 
  <Record> 
    <PropertyValue Property="Value" String="Pattern" /> 
    <Annotation Term="Core.Description" String="String property can be used as first operand in startswith, endswith, and contains clauses" /> 
  </Record> 
 
for properties representing character large objects.
[18:24] Ralf Handl (SAP SE): Mike: "Pattern" might lead to confusion with Validation.Pattern and odata.matchesPattern which allow regular expressions
[18:25] Ralf Handl (SAP SE): So we need a term for something weaker than regular expressions
[18:28] Ralf Handl (SAP SE): Mike: SearchExpression
[18:28] Ralf Handl (SAP SE): Stefan agrees

 

[18:29] Stefan Hagen: I move to resolve ODATA-1017 as proposed.

 

[18:30] Mike Pizzo: I second

 

[18:30] Ralf Handl (SAP SE): ODATA-1017 is RESOLVED with the amended proposal
[18:30] Ralf Handl (SAP SE): ODATA-1027
Support instance annotations in $orderby
[18:35] Ralf Handl (SAP SE): Mike: what about other places, e.g. $select?
[18:36] Ralf Handl (SAP SE): ODATA-1027 is OPEN
[18:36] Ralf Handl (SAP SE): Mike to investigate if there are use cases for instance annotations in $select
[18:38] Ralf Handl (SAP SE): i.ODATA-674 Specify navigation property binding combined with containment
[18:38] Ralf Handl (SAP SE): ODATA-674 is OPEN
[18:39] Ralf Handl (SAP SE): iii.ODATA-854 Consider use of OPTIONS for discovering formats, other capabilities and features
[18:39] Ralf Handl (SAP SE): ODATA-854 is OPEN
[18:39] Ralf Handl (SAP SE): iv.ODATA-868 Describe HTTP encoding for streamed requests and responses
[18:39] Ralf Handl (SAP SE): ODATA-868 is OPEN
[18:40] Ralf Handl (SAP SE): vi.ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)
[18:40] Ralf Handl (SAP SE): ODATA-884 is OPEN
[18:42] Ralf Handl (SAP SE): vii.ODATA-919 Specify the result type for each operation based on operator types
[18:42] Ralf Handl (SAP SE): ODATA-919 is OPEN
[18:42] Ralf Handl (SAP SE): xi.ODATA-962 CORS Support
[18:43] Ralf Handl (SAP SE): ODATA-962 is OPEN
[18:44] Ralf Handl (SAP SE): xii.ODATA-994 consider replacing SchemaVersion header with $SchemaVersion query option, or root URL versioning
[18:44] Ralf Handl (SAP SE): ODATA-994 is OPEN
[18:46] Ralf Handl (SAP SE): xvi.ODATA-1011 Security experts at RSA suggest adding guidance on the use of OAuth and openID
[18:46] Ralf Handl (SAP SE): ODATA-1011 is OPEN
[18:47] Ralf Handl (SAP SE): 8.Next meeting [9:50 am PT]
a.Thursday January 26, 2017 during 8-10 am PST?
[18:47] Ralf Handl (SAP SE): No objections to a., we meet next week usual time
[18:47] Ralf Handl (SAP SE): 9.AOB and wrap up [9:55 am PT]
[18:48] Ralf Handl (SAP SE): Mike: public reviews for V4.01 have started, please circulate the news and invite people to give feedback
[18:49] Ralf Handl (SAP SE): Mike has been contacted by Open Data Institute http://theodi.org/
[18:50] Ralf Handl (SAP SE): Want to list Wales open data OData services in their data catalog
[18:51] Ralf Handl (SAP SE): Would benefit from having a mapping to DCAT https://www.w3.org/TR/vocab-dcat/
[18:52] Ralf Handl (SAP SE): A self-contained catalog vocabulary that correlates to DCAT would be sufficient

 

[18:57] Mike Pizzo: Link for OData.org community vocabularies: https://github.com/oasis-tcs/odata-vocabularies

 

[18:57] Stefan Hagen: Stefan has started to change Committee Note "Securing OData Version 4.0" Working Draft 01 - as this work product never progressed for months, I plan to radically simplify the document and shorten it's score (presumably also integrate changes helping resolve ODATA-1011). Question: Do the members of the TC object to this, or can I go ahead and provide a new revised draft?
[18:59] Stefan Hagen: Stefan will check the current draft on one drive into kavi
[18:59] Stefan Hagen: then he will change
[19:00] Stefan Hagen: CORS, CSRF, XSS, and OpenID,OAUTH (latter maybe)

 

[19:00] 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: Mittwoch, 18. Januar 2017 18:17
To: odata@lists.oasis-open.org
Subject: RE: [odata] Agenda for OData TC meeting on 2017-01-19

 

Update:

·         TC Timeline – new agenda item 5.

·         Assign issues – new agenda item 7.a.

 

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Mittwoch, 18. Januar 2017 14:34
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2017-01-19

 

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday January 19, 2017 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=43961

 

2.        Approve agenda [8:05 am PT]

 

3.        Approve minutes from previous meeting(s) [8:10 am PT]

a.     Minutes from January 12, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/59782/odata-meeting-157_on-20170112-minutes.html

 

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

 

5.        TC Timeline [8:16 am PT]

a.     Topics for this year

                                  i.    OData Core and JSON Version 4.01 CSD01 and CS01

                                 ii.    What’s New in OData Version 4.01 (CND01 and) CN01

1.     Do we want to publish a Note Draft or directly a Note?

                                iii.    CSDL JSON Version 4.01 CSD01, …

                                iv.    OData to OpenAPI Mapping Version 4.0 CND01 and CN01

                                 v.    Extension for Temporal Data Version 4.0 CSD01, …

                                vi.    REST Profile for OData Version 4.01 CND01 and CN01

                               vii.    …?

 

6.        V4.0 ERRATA04 [9:00 am PT]

a.     How to deal with errors/clarifications in V4.0 ERRATA03: plan for ERRATA04 or fix them in V4.01 only?

b.     Issues for V4.0_ERRATA04 in New or Open state

                                  i.    ODATA-955 Specifying odata.type on a collection of entities

                                 ii.    ODATA-1024 5.1.1.5.7 substring: explicitly state that the index N (second parameter value) is zero-based

                                iii.    ODATA-1026 Clarify when $it is required

 

7.        V4.01 [9:20 am PT]

a.       Issues for V4.01_CSD02 without assignee

                                  i.    ODATA-955 Specifying odata.type on a collection of entities

                                 ii.    ODATA-1018 Allow $expand and $select with modifying requests that return a collection in combination with return=representation to specify the response shape

                                iii.    ODATA-1019 Add term Core.OptionallyComputed or Core.ComputedDefault

                                iv.    ODATA-1020 Remove / in reference in instance annotation in filter and orderby _expression_

                                 v.    ODATA-1021 Are additional values needed for the reason property of a removed Annotation

                                vi.    ODATA-1022 Add an example of a delta payload used in a PATCH request to the Delta Payload section

                               vii.    ODATA-1023 Provide stable anchors to all sections

                              viii.    ODATA-1024 5.1.1.5.7 substring: explicitly state that the index N (second parameter value) is zero-based

                                ix.    ODATA-1025 Treatment of same query option in multiple "spellings"

                                 x.    ODATA-1026 Clarify when $it is required

b.     Issues for V4.01_CSD02 ready for resolution

                                  i.    ODATA-817 Add client-side function odata.matchesRegularExpression

                                 ii.    ODATA-1008 Consider deprecating symbolic "max" length

                                iii.    ODATA-1013 Selected nav props in a defining query should specify interest in added/deleted links

                                iv.    ODATA-1017 Extend FilterExpressionRestrictions with "Pattern"

c.       Issues for V4.01_CSD02 in New or Open state without concrete proposal

                                  i.    ODATA-674 Specify navigation property binding combined with containment

                                 ii.    ODATA-760 Add to depth restrictions to Capabilities Vocabulary

                                iii.    ODATA-854 Consider use of OPTIONS for discovering formats, other capabilities and features

                                iv.    ODATA-868 Describe HTTP encoding for streamed requests and responses

                                 v.    ODATA-879 Support Arrays of Arrays

                                vi.    ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)

                               vii.    ODATA-919 Specify the result type for each operation based on operator types

                              viii.    ODATA-920 Specify overflow for int data types (-INF, INF, NaN)

                                ix.    ODATA-923 $expand (or $include) for $metadata to include referenced schemas

                                 x.    ODATA-950 Clarify what requests can be delta enabled

                                xi.    ODATA-962 CORS Support

                               xii.    ODATA-994 consider replacing SchemaVersion header with $SchemaVersion query option, or root URL versioning

                              xiii.    ODATA-1002 Add build in functions operating on collections of primitive (and complex?) types

                              xiv.    ODATA-1003 Allow casting of entities and complex type instances to arbitrary structural type

                               xv.    ODATA-1005 Make sure we have capabilities for all new 4.01 functionality

                              xvi.    ODATA-1011 Security experts at RSA suggest adding guidance on the use of OAuth and openID

 

8.        Next meeting [9:50 am PT]

a.     Thursday January 26, 2017 during 8-10 am PST?

 

9.        AOB and wrap up [9:55 am PT]

 

[2] References

·         Conference call details: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/56760/TC%20meeting%20dial-in%20details.htm

·         Chat room: http://webconf.soaphub.org/conf/room/odatatc

 

[3] Timeline

·         https://www.oasis-open.org/committees/document.php?document_id=56024&wg_abbrev=odata

 

 

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]