FW: Agenda for OData TC meeting on 2019-01-10

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday January 10, 2019 during 8-10 am PST (17:00-19:00 CET). For additional information, such as dial-in details and chat room, refer to [2]. For TC timeline, see [3]. Feel free to suggest additions or modifications.

Thanks.

[1] Agenda

1. Roll call [8:00 am PT]

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

2. Approve agenda [8:05 am PT]

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

Minutes from December 20, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/64481/odata-meeting-241_on-20181220-minutes.html

4. Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php?sort_field=due_closed_date] [8:15am PT]

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

Feedback from Mark Nottingham, 2019-01-03, on the header OData-Isolation:

My .02 - If it were me, I'd just register OData-Isolation, because in my experience, things that are defined without having multiple communities tend to miss the requirements that other communities have, so they don't get used.

Colloquially, we call this "hope-based standardisation" -- it's sometimes appropriate, but it requires some amount of engagement/research, and from what I can see you don't have that here. If other folks with REST APIs have requirements along these lines, they can learn from your experiences, have their discussions, and mint a new header that they can use, rather than trying to fit their use cases into what you've sketched out.

Feedback from Mark Nottingham, 2019-01-03, on the preferences:

See also my note just now about optimistic standardisation; personally, I tend to think that registering the OData-* prefixed versions is the right thing to do here.

5. Issues [8:20 am PT]

V4.01: NEW or OPEN

i. ODATA-1268 Clarify meaning of Nullable for collection-valued structural properties

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-1263 Requirement for 204 (No Content) with 11.4.3 "Update an Entity" is not backwards compatible

v. ODATA-1261 Allow $pagesize system query option

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

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

viii. ODATA-1266 Geo literals with three dimensions

ix. ODATA-1250 GeoJSON, SRID, and LineString

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

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

xii. ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation

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

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

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

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

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

xviii. ODATA-1246 Allow BaseType to be a ComplexType

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

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

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

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

xxiii. ODATA-1135 Document use of JSON $schema

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

xxv. 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-1244 Add a function to determine aggregated values within common expressions

iii. ODATA-1218 Transformations for recursive hierarchy processing

iv. ODATA-1207 Clarify need for @odata.id in nested response structures

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

6. Review Permissions annotations [9:30 am PT]

7. Next meetings [9:50 am PT]

Thursday January 17, 2019 during 8-10 am PST (17:00-19:00 CET)
Thursday January 24, 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