RE: Agenda for OData TC meeting on 2018-12-20

Please change your name from 'anonymous' using the Settings button

[16:58] anonymous morphed into Ralf Handl (SAP SE)

[16:59] 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 December 20, 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]

a.Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46287

2.Approve agenda [8:05 am PT]

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

a.Minutes from December 13, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/64435/odata-meeting-240_on-20181212-minutes.html

4.How to proceed with minutes?

a.Stefan Hagen unfortunately will resign as TC Secretary

b.Volunteers for TC Secretary?

i.Benefits: permanent voting rights, prominently named on TC home page

ii.Tasks: minutes keeper

5.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

6.Issues [8:20 am PT]

a.V4.01

i.ODATA-1177 Add "JSON properties" to OData

ii.ODATA-1265 Clarify property paths used in a lambda predicate _expression_

iii.ODATA-1257 Do URLs within a Batch Request need to be URL Encoded?

iv.ODATA-1249 edm.xsd: ActionImport and IncludeInServiceDocument

v.ODATA-1248 csdl.schema.json: add descriptions to all schema elements

vi.ODATA-1245 Extract _expression_ syntax into own sub-section next to $filter

b.Data Aggregation

i.ODATA-1072 Annotation to describe supported aggregation methods

1.Structured term AggregationConstraints as currently proposed introduces ambiguity on how to express no constraints on aggregation methods

2.New proposal: split into separate terms for each aspect, no annotation means no constraint for this aspect

ii.ODATA-1244 Add a function to determine aggregated values within common expressions

c.V4.01: NEW or OPEN

i.ODATA-1263 Requirement for 204 (No Content) with 11.4.3 "Update an Entity" is not backwards compatible

ii.ODATA-1262 Explicitly state structural restrictions of type Edm.Untyped

iii.ODATA-1261 Allow $pagesize system query option

iv.ODATA-1260 Clarify read-write access via URLs differing from the canonical/read/edit URL

v.ODATA-1259 Clarify @type (@odata.type) and metadata=full

vi.ODATA-1266 Geo literals with three dimensions

vii.ODATA-1250 GeoJSON, SRID, and LineString

viii.ODATA-1243 Clarify whether $orderby and string comparison with ge, gt, le, lt is language-specific

ix.ODATA-1242 Clarify that resolved relative URIs in batch responses cannot contain content-ID references

x.ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation

xi.ODATA-1165 Describe $expand and $select via prose text and examples, remove ABNF snippets

xii.ODATA-1267 URL Conventions example in 5.1.1.5.1 has "bad" whitespace

xiii.ODATA-1253 Abstract type definition Core.Number as a super-type of all numeric types

xiv.ODATA-1246 Allow BaseType to be a ComplexType

xv.ODATA-1239 Define a mechanism to distinguish between inserted and updated entities in a Delta Response

xvi.ODATA-1238 Clarifications for select-list in ContextUrl

xvii.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)

xviii.ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts

xix.ODATA-1135 Document use of JSON $schema

xx.ODATA-1064 Add ability to annotate collections to return only count and NextLink

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

d.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-1207 Clarify need for @odata.id in nested response structures

iv.ODATA-945 Correct examples 53 and 54

e.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

f.Vocabularies: NEW or OPEN that need more discussion

i.ODATA-1264 CRUD descriptions on entity sets

ii.ODATA-1214 Annotate constructor actions

iii.ODATA-1140 ODATA-884 / Add details to HTTPResponseCode term

iv.ODATA-1107 Introduce instance annotation to specify which types an instance "implements"

v.ODATA-1060 Improve specification of element response requirements

vi.ODATA-884 Enable enumerating the valid requests and responses for a particular resource.

7.Next meetings [9:50 am PT]

a.Thursday January 10, 2019 during 8-10 am PST (17:00-19:00 CET)  moderator: Mike Pizzo  minutes keeper: ???

b.Thursday January 17, 2019 during 8-10 am PST (17:00-19:00 CET)

c.Thursday January 21, 2019 during 8-10 am PST (17:00-19:00 CET)

8.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/62637/TC%20Timeline-2018-03-02.docx

[17:01] Ralf Handl (SAP SE): Voting Members: 2 of 10 (20%) (used for quorum calculation)

[17:02] Ralf Handl (SAP SE): Voting Members: 4 of 10 (40%) (used for quorum calculation)

[17:03] Ralf Handl (SAP SE): Voting Members: 5 of 10 (50%) (used for quorum calculation)

[17:04] Ralf Handl (SAP SE): Voting Members: 6 of 10 (60%) (used for quorum calculation)

[17:04] Ralf Handl (SAP SE): Achieved quorum:yes

[17:05] Ralf Handl (SAP SE): Voting Members: 7 of 10 (70%) (used for quorum calculation)

[17:05] Ralf Handl (SAP SE): 2.Approve agenda [8:05 am PT]

[17:05] 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 December 13, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/64435/odata-meeting-240_on-20181212-minutes.html

[17:06] Ralf Handl (SAP SE): Minutes are approved

[17:06] Ralf Handl (SAP SE): 4.How to proceed with minutes?

a.Stefan Hagen unfortunately will resign as TC Secretary

b.Volunteers for TC Secretary?

i.Benefits: permanent voting rights, prominently named on TC home page

ii.Tasks: minutes keeper

[17:09] Ralf Handl (SAP SE): George volunteers to be secretary

[17:11] Ralf Handl (SAP SE): I move to approve George Ericson as new secretary

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

[17:11] Ralf Handl (SAP SE): No objection, motion passes

[17:11] Ralf Handl (SAP SE): @George: congratulations!

[17:11] Ralf Handl (SAP SE): And a lot of thanks!

[17:12] Ralf Handl (SAP SE): 5.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:16] Ralf Handl (SAP SE): Mark Nottingham responded to our preference submission:

[17:16] Ralf Handl (SAP SE): Hi Chet and Mark,

I agree that some of these are potentially generic. See specific comments below.

Generally, we like to see extensions that are generic being documented in a way that isn't specific to one application. For example, WebDAV's previous definitions of HTTP methods and status codes is now considered bad practice; if they were done today, we'd make sure to define them in their own document.

Note that's not a formal policy for HTTP preferences (AFAIK; ultimately it's up to the experts); just a preference that's been expressed and accepted in the community for other extension points that seems pretty applicable here. Experience has shown that people who aren't intimately familiar with the context will assume that those extensions are limited to that application.

Would there be a willingness in your community to spin some of these extensions into a separate, non-ODATA-specific document? Something else from OASIS would be fine, it doesn't need to be an RFC. I imagine that ODATA might still have something to say about their specific use in that protocol (which might resolve the question below).

Cheers,

> On 19 Dec 2018, at 8:18 am, Chet Ensign <chet.ensign@oasis-open.org> wrote:

> Hi Mark,

> Our thinking is that a number of the preferences may be of general use and are not specific to OData.  Looking at each of the preferences the ones we feel are of general interest and independent of OData are

>          callback as an add-on to respond-async can be used with any payload format  respond-async defined in - https://tools.ietf.org/html/rfc7240 - author is James Snell

>          maxpagesize as an add-on to the "next" link relation, see https://www.iana.org/assignments/link-relations/link-relations.xhtml.

>          Can be used in Atom with <link rel="next" ... /> as we do it in the OData Atom format

>          Can be used with a link header with this relation, see https://tools.ietf.org/html/rfc5988 - author is Mark Nottingham

>          omit-values  interesting for other JSON or name-value pair formats

>          track-changes  can be used with other payload formats that allow representing diffs, e.g. JSON PATCH - https://tools.ietf.org/html/rfc6902 - author is Mark Nottingham

I think I agree that these are potentially generic. However, their descriptions mention ODATA-specific concepts; e.g., "delta links" and ODATA capabilities. Could you factor those out into more generic things, omit them, or move them to ODATA-specific text elsewhere?

> The remaining three are less obvious to us as to whether they would be useful in other cases

>          allow-entityreferences  needs a concept and representation of references to be useful

>          continue-on-error  needs a batch or bulk format

>          include-annotations  needs annotations

> Do you or other experts know of existing specs that utilize the concept of references, batch or bulk operations or annotations?  If so could any of these remaining three be useful to those specs?

I think I agree that these are less likely to be useful generic. I'd encourage you to continue using the odata.* names.

Cheers,

--

Mark Nottingham   https://www.mnot.net/

[17:17] Ralf Handl (SAP SE): 6.Issues [8:20 am PT]

a.V4.01

i.ODATA-1177 Add "JSON properties" to OData

[17:17] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1177

[17:18] Ralf Handl (SAP SE): Description

Allow defining "JSON properties" in OData models, i.e. properties whose value is well-formed JSON.

Requirements:

JSON property values are represented "inline" in JSON responses, i.e. "JSONproperty": <well-formed JSON data>

Common expressions (e.g. in $filter) can address parts of JSON data

JSON properties can specify a JSON Schema that describes/restricts their data values

This would finally resolve/replace the long-planned OData Extension for JSON Data.

[17:20] Ralf Handl (SAP SE): George: the type should specify the value range and behaviors

[17:20] Ralf Handl (SAP SE): George: need not be specific to JSON, JSON could be just one of the possible mappings, with e.g. XML being another mapping

[17:21] Ralf Handl (SAP SE): Sort of what Edm.Untyped is, but without the restriction on "property names"

[17:21] Ralf Handl (SAP SE): George: fundamentally we want a type system that covers all use cases

[17:25] Ralf Handl (SAP SE): Mark: in the past we had an XML format in addition to JSON, and non-JSON formats would have to define how to render "JSON property"

[17:29] Ralf Handl (SAP SE): George: identify type by its value restrictions, not by an existing language binding, here "JSON"

[17:31] Ralf Handl (SAP SE): Mark: is it a new OData type, or is it just Edm.String with certain value restrictions and a special representation in the JSON Format

[17:32] Ralf Handl (SAP SE): George: tend to make it part of the type system

[17:32] Ralf Handl (SAP SE): ODATA-1177 is OPEN

[17:34] Ralf Handl (SAP SE): George: what about compatibility?

[17:35] Ralf Handl (SAP SE): Could say: it is Edm.String and a JSON string in V4 responses, and native embedded JSON in a V4.01 response

[17:37] Ralf Handl (SAP SE): Mark: leaning towards a type

[17:38] Ralf Handl (SAP SE): George: also leaning towards a type

[17:40] Ralf Handl (SAP SE): George: use Edm.JSONString or something similar

[17:40] Ralf Handl (SAP SE): ii.ODATA-1265 Clarify property paths used in a lambda predicate _expression_

[17:41] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1265

[18:00] Ralf Handl (SAP SE): Matt: define what "scope" is

[18:01] Ralf Handl (SAP SE): Have two examples, one with a direct $filter not nested within $expand

[18:06] Gerald Krause (SAP): AI for Gerald to update proposal of ODATA-1265

[18:08] Ralf Handl (SAP SE): New in V4.01: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/64157/new-in-odata-v4.01-wd03-2018-10-26.docx

[18:09] George Ericson (Dell): Placeholder request to add presentations that introduce OData functionality.

[18:10] Ralf Handl (SAP SE): iii.ODATA-1257 Do URLs within a Batch Request need to be URL Encoded?

[18:10] Ralf Handl (SAP SE): Proposal:

URLs must be fully percent encoded in the request, including in a multipart batch request

URLs represented as string within a JSON payload, including JSON batch, must be safely encoded. Need to define what safely encoded means - colons within the path must be encoded, (and forward-slashes used within data values) percent-encoded. Question marks within path must be encoded, and hashes must be encoded.

Question: must colons in query string be percent-encoded?

[18:12] Ralf Handl (SAP SE): Mark will answer this question

[18:12] Ralf Handl (SAP SE): iv.ODATA-1249 edm.xsd: ActionImport and IncludeInServiceDocument

[18:13] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1249

[18:14] Ralf Handl (SAP SE): Description

The edm.xsd erroneously allows specifying the IncludeInServiceDocument attribute for the edm:ActionImport

[18:14] Ralf Handl (SAP SE): Proposal:

edm.xsd: restrict IncludeInServiceDocument to edm:FunctionImport as defined in the prose specification

[18:20] Ralf Handl (SAP SE): ODATA-1249 is OPEN

[18:20] George Ericson (Dell): Move to to resolve ODATA-1249

[18:20] Matt Borges (SAP): I seccond

[18:21] Ralf Handl (SAP SE): ODATA-1249 is RESOLVED as proposed

[18:23] Ralf Handl (SAP SE): I move to close ODATA-1249 as applied

[18:24] Ralf Handl (SAP SE): And merge https://github.com/oasis-tcs/odata-csdl-schemas/pull/5

[18:24] Mark Biamonte (Progress)1: I second

[18:24] Ralf Handl (SAP SE): ODATA-1249 is CLOSED as applied

[18:24] Ralf Handl (SAP SE): v.ODATA-1248 csdl.schema.json: add descriptions to all schema elements

[18:24] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1248

[18:27] Ralf Handl (SAP SE): ODATA-1248 is OPEN

[18:30] George Ericson (Dell): I Move to resolve OData-1248 as proposed.

[18:30] Mark Biamonte (Progress)1: I second

[18:31] Ralf Handl (SAP SE): ODATA-1248 is RESOLVED as proposed

[18:32] George Ericson (Dell): I Move to close ODATA-1248 as applied.

[18:33] Mark Biamonte (Progress)1: I second

[18:33] Ralf Handl (SAP SE): ODATA-1248 is CLOSED as applied

[18:33] Ralf Handl (SAP SE): vi.ODATA-1245 Extract _expression_ syntax into own sub-section next to $filter

[18:33] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1245

[18:35] Ralf Handl (SAP SE): ODATA-1245 is OPEN

[18:38] Ralf Handl (SAP SE): Ralf to prepare a document with this change applied

[18:39] Mark Biamonte (Progress)1: I move to have Common Expressions broken out into a separate section as described in OData-1245

[18:40] George Ericson (Dell): I second

[18:40] Ralf Handl (SAP SE): ODATA-1245 is RESOLVED as proposed

[18:40] Ralf Handl (SAP SE): b.Data Aggregation

i.ODATA-1072 Annotation to describe supported aggregation methods

1.Structured term AggregationConstraints as currently proposed introduces ambiguity on how to express no constraints on aggregation methods

2.New proposal: split into separate terms for each aspect, no annotation means no constraint for this aspect

[18:40] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1072

[18:45] Ralf Handl (SAP SE): ODATA-1072 is OPEN

[18:49] Gerald Krause (SAP): I move to resolve ODATA-1072 as proposed.

[18:50] George Ericson (Dell): I move to resolve ODATA-1072 as proposed.

[18:50] George Ericson (Dell): I second

[18:51] Ralf Handl (SAP SE): ODATA-1072 is RESOLVED with the new proposal

[18:51] Ralf Handl (SAP SE): ii.ODATA-1244 Add a function to determine aggregated values within common expressions

[18:51] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1244

[19:04] Ralf Handl (SAP SE): 7.Next meetings [9:50 am PT]

a.Thursday January 10, 2019 during 8-10 am PST (17:00-19:00 CET)  moderator: Mike Pizzo  minutes keeper: George Ericson

b.Thursday January 17, 2019 during 8-10 am PST (17:00-19:00 CET)

c.Thursday January 21, 2019 during 8-10 am PST (17:00-19:00 CET)

[19:05] Ralf Handl (SAP SE): 8.AOB and wrap up [9:55 am PT]

[19:05] George Ericson (Dell): Next meeting is Jan 10, 2019....

[19:05] Ralf Handl (SAP SE): Merry Christmas and a Happy New Year!

[19:06] Ralf Handl (SAP SE): Meeting is adjourned

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf
Sent: Mittwoch, 19. Dezember 2018 09:37
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2018-12-20

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

2. Approve agenda [8:05 am PT]

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

Minutes from December 13, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/64435/odata-meeting-240_on-20181212-minutes.html

4. How to proceed with minutes?

Stefan Hagen unfortunately will resign as TC Secretary
Volunteers for TC Secretary?

i. Benefits: permanent voting rights, prominently named on TC home page

ii. Tasks: minutes keeper

5. 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]

Upcoming

i. #0037 Concept for Google Protocol Buffers as a data format – Hubert Heijkers – 2019-03-28

In progress

i. #0036 Register the OData- headers and preferences with IANA – Mark Biamonte – 2018-07-26

6. Issues [8:20 am PT]

V4.01

i. ODATA-1177 Add "JSON properties" to OData

ii. ODATA-1265 Clarify property paths used in a lambda predicate _expression_

iii. ODATA-1257 Do URLs within a Batch Request need to be URL Encoded?

iv. ODATA-1249 edm.xsd: ActionImport and IncludeInServiceDocument

v. ODATA-1248 csdl.schema.json: add descriptions to all schema elements

vi. ODATA-1245 Extract _expression_ syntax into own sub-section next to $filter

Data Aggregation

i. ODATA-1072 Annotation to describe supported aggregation methods

Structured term AggregationConstraints as currently proposed introduces ambiguity on how to express “no constraints on aggregation methods
New proposal: split into separate terms for each aspect, no annotation means “no constraint for this aspect”

ii. ODATA-1244 Add a function to determine aggregated values within common expressions

V4.01: NEW or OPEN

i. ODATA-1263 Requirement for 204 (No Content) with 11.4.3 "Update an Entity" is not backwards compatible

ii. ODATA-1262 Explicitly state structural restrictions of type Edm.Untyped

iii. ODATA-1261 Allow $pagesize system query option

iv. ODATA-1260 Clarify read-write access via URLs differing from the canonical/read/edit URL

v. ODATA-1259 Clarify @type (@odata.type) and metadata=full

vi. ODATA-1266 Geo literals with three dimensions

vii. ODATA-1250 GeoJSON, SRID, and LineString

viii. ODATA-1243 Clarify whether $orderby and string comparison with ge, gt, le, lt is language-specific

ix. ODATA-1242 Clarify that resolved relative URIs in batch responses cannot contain content-ID references

x. ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation

xi. ODATA-1165 Describe $expand and $select via prose text and examples, remove ABNF snippets

xii. ODATA-1267 URL Conventions example in 5.1.1.5.1 has "bad" whitespace

xiii. ODATA-1253 Abstract type definition Core.Number as a super-type of all numeric types

xiv. ODATA-1246 Allow BaseType to be a ComplexType

xv. ODATA-1239 Define a mechanism to distinguish between inserted and updated entities in a Delta Response

xvi. ODATA-1238 Clarifications for select-list in ContextUrl

xvii. 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)

xviii. ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts

xix. ODATA-1135 Document use of JSON $schema

xx. ODATA-1064 Add ability to annotate collections to return only count and NextLink

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

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-1207 Clarify need for @odata.id in nested response structures

iv. ODATA-945 Correct examples 53 and 54

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

Vocabularies: NEW or OPEN that need more discussion

i. ODATA-1264 CRUD descriptions on entity sets

ii. ODATA-1214 Annotate constructor actions

iii. ODATA-1140 ODATA-884 / Add details to HTTPResponseCode term

iv. ODATA-1107 Introduce instance annotation to specify which types an instance "implements"

v. ODATA-1060 Improve specification of element response requirements

vi. ODATA-884 Enable enumerating the valid requests and responses for a particular resource.

7. Next meetings [9:50 am PT]

Thursday January 10, 2019 during 8-10 am PST (17:00-19:00 CET) – moderator: Mike Pizzo – minutes keeper: ???
Thursday January 17, 2019 during 8-10 am PST (17:00-19:00 CET)
Thursday January 21, 2019 during 8-10 am PST (17:00-19:00 CET)

8. 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/62637/TC%20Timeline-2018-03-02.docx

odata message