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: Agenda for OData TC meeting on 2019-01-24

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




[1] Agenda


1.        Roll call [8:00 am PT]

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


2.        Approve agenda [8:05 am PT]


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

    1. Minutes from January 17, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/64553/Minutes%20of%202019-01-17%20Meeting%20%23243.docx


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]

    1. Upcoming

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

    1. In progress

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


5.        Review TC Timeline for 2019

    1. https://www.oasis-open.org/committees/download.php/64563/TC%20Timeline%202019-01-23.docx  


6.        Issues [8:20 am PT]

    1. V4.01: Triage issues:

                                  i.    List of issue NEW or OPEN


    1. V4.01: NEW or OPEN

                                  i.    ODATA-1177 Embed "JSON properties" in OData JSON requests and responses

                                 ii.    ODATA-1274 Clarify that a server MUST respond with content-id annotations and MUST include nested entity IDs

                                iii.    ODATA-1272 Highlight implications of derived complex types to their annotations

                                iv.    ODATA-1270 14.4.11: rephrase prose text for dynamic _expression_ Null

                                 v.    ODATA-1266 Geo literals with three dimensions

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

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

                              viii.    ODATA-1250 GeoJSON, SRID, and LineString

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

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

                                xi.    ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation

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


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

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

                               xv.    ODATA-1261 Allow $pagesize system query option

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

                             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


    1. 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-945 Correct examples 53 and 54


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


    1. Vocabularies: NEW or OPEN that need more discussion

                                  i.    ODATA-1275 Describing and querying "JSON properties"

                                 ii.    ODATA-1269 Add QueryRestrictions to the Capabilities Vocabulary

                                iii.    ODATA-1264 CRUD descriptions on entity sets

                                iv.    ODATA-1214 Annotate constructor actions

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

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

                               vii.    ODATA-1060 Improve specification of element response requirements

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


7.        Next meetings [9:50 am PT]

    1. Thursday January 31, 2019 during 8-10 am PST (17:00-19:00 CET)
    2. Thursday February 07, 2019 during 8-10 am PST (17:00-19:00 CET)


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