5. a. iv. Added ODATA-635 (received via comments list)
From: [mailto:] On Behalf Of Handl, Ralf
Sent: Wednesday, 2. April 2014 14:39
To:
Subject: [odata] Agenda for OData TC meeting 2014-04-03
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
Roll call [8:00am PT]
Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=36532
Approve agenda [8:05am PT]
Approve minutes from previous meeting(s) [8:10am PT]
Minutes from March 27, 2014 TC meeting: https://www.oasis-open.org/committees/download.php/52414/odata-meeting-67_on-20140227-minutes.html
Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]
Action items due by April 03, 2014
None
Process issues [Issues list: https://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10103]
[8:20am PT]
Issues
for V4.0_ERRATA01 in New or Open state
OData ABNF Construction Rules
ODATA-633
Rule pct-encoded-unescaped unintentionally omits hex pairs starting with 7
OData CSDL
ODATA-606
Specify navigation property binding combined with containment
OData JSON Format
ODATA-596
Discrepancy between order of elements for geo-positions between GeoJSON and GML may cause interoperability difficulties.
ODATA-587
Add example for complex value that is an empty object
ODATA-592
JSON example 11: "type":"Point" with uppercase P according to GeoJSON spec
ODATA-594
Discrepancy between ATOM and JSON formats (GML, GeoJson) for Polygon information content
ODATA-597
Seeking clarification of naming for GeographyCollection with GeoJSON
ODATA-598
Update JSON RFC reference
ODATA-599
Let's update the GeoJSON reference
ODATA-600
Ensure future compatibility by reference to draft-bray-i-json-n (The I-JSON Message Format)
ODATA-607
Section 4.5.4: explicitly state that @odata.count can be applied to expanded to-many navigation properties with server-driven paging
OData Protocol
ODATA-578
Contains example has order of arguments backwards
ODATA-580
8.2.4 If-Match should refer to term Core.OptimisticConcurrency
ODATA-591
Part1, examples 36-40: replace "associated" with "related"
ODATA-609
Section 11.4.4 Upsert: key values in URL win over key values in request body
ODATA-610
11.4.4: Upsert and server-generated keys
ODATA-612
Consistently use "edit link" and "edit URL"
ODATA-623
11:4.3: be more specific on updating key properties
ODATA-624
Clarify that (clients and) services may include additional format parameters in Content-Type header.
ODATA-632
"Core.OptimisticConcurrencyControl" should be "Core.OptimisticConcurrency"
ODATA-635 Clarify
if a PUT request is allowed to change the odata.type of the entity (public comment c201403e00002)
ODATA-636 Clarify
that complex types and arrays can only be passed to functions through parameter aliases
Next Face-to-Face meeting Thursday May 15 and Friday May 16 in Redmond [9:40am PT]
Mike: possibility of Microsoft hosting the F2F?
Next meeting [9:50am PT]
Thursday April 10, 2014 during 8-10am PT?
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
