[odata] Agenda for OData TC meeting 2014-04-03

["Handl, Ralf" <ralf.handl@sap.com>]

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday April 03, 2014 during 8-10am PT. 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 for 2014-04-03 OData TC meeting

 

1.       Roll call [8:00am PT]

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

 

2.       Approve agenda [8:05am PT]

 

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

a.       Minutes from March 27, 2014 TC meeting: https://www.oasis-open.org/committees/download.php/52414/odata-meeting-67_on-20140227-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 by April 03, 2014

i.      None

 

5.       Process issues [Issues list: https://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10103] [8:20am PT]

a.       Issues for V4.0_ERRATA01 in New or Open state

i.      OData ABNF Construction Rules

1. ODATA-633         Rule pct-encoded-unescaped unintentionally omits hex pairs starting with 7

 

ii.      OData CSDL

1. ODATA-606         Specify navigation property binding combined with containment

 

iii.      OData JSON Format

1. ODATA-596         Discrepancy between order of elements for geo-positions between GeoJSON and GML may cause interoperability difficulties.
2. ODATA-587         Add example for complex value that is an empty object
3. ODATA-592         JSON example 11: "type":"Point" with uppercase P according to GeoJSON spec
4. ODATA-594         Discrepancy between ATOM and JSON formats (GML, GeoJson) for Polygon information content
5. ODATA-597         Seeking clarification of naming for GeographyCollection with GeoJSON
6. ODATA-598         Update JSON RFC reference
7. ODATA-599         Let's update the GeoJSON reference
8. ODATA-600         Ensure future compatibility by reference to draft-bray-i-json-n (The I-JSON Message Format)
9. ODATA-607         Section 4.5.4: explicitly state that @odata.count can be applied to expanded to-many navigation properties with server-driven paging

 

iv.      OData Protocol

1. ODATA-578         Contains example has order of arguments backwards
2. ODATA-580         8.2.4 If-Match should refer to term Core.OptimisticConcurrency
3. ODATA-591         Part1, examples 36-40: replace "associated" with "related"
4. ODATA-609         Section 11.4.4 Upsert: key values in URL win over key values in request body
5. ODATA-610         11.4.4: Upsert and server-generated keys
6. ODATA-612         Consistently use "edit link" and "edit URL"
7. ODATA-623         11:4.3: be more specific on updating key properties
8. ODATA-624         Clarify that (clients and) services may include additional format parameters in Content-Type header.
9. ODATA-632         "Core.OptimisticConcurrencyControl" should be "Core.OptimisticConcurrency"
10. ODATA-636       Clarify that complex types and arrays can only be passed to functions through parameter aliases

 

6.       Next Face-to-Face meeting Thursday May 15 and Friday May 16 in Redmond [9:40am PT]

a.       Mike: possibility of Microsoft hosting the F2F?

 

7.       Next meeting [9:50am PT]

a.       Thursday April 10, 2014 during 8-10am PT?

 

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

 

[2] References

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

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

 

[3] Timeline

·         https://www.oasis-open.org/committees/download.php/50823/TC%20Timeline%206.htm