[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [odata] Agenda for OData TC meeting 2014-03-27
PS: Sorry for being late, but I was so happy to read again long lists of issues to process, that I first did not realize, that item was not included.
All the best, Stefan. Am 26.03.14 13:40, schrieb Handl, Ralf:
Here [1] is a draft agenda for the OData TC (Technical Committee) meeting*//*scheduled on Thursday March 27, 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.03.27 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 Feb 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 March 27, 2014 i.None 5.Process issues [Issues list: https://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10103] [8:30am PT] a.Issues for V4.0_ERRATA01 in New or Open state <https://tools.oasis-open.org/issues/issues/?jql=project%20%3D%20ODATA%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%22V4.0_ERRATA01%22%20ORDER%20BY%20component%20ASC%2C%20key%20ASC> i.OData ABNF Construction Rules 1._ODATA-565 <https://tools.oasis-open.org/issues/browse/ODATA-565>_ 2: Clarify interpretation of path segments and query option values with respect to percent-encoded punctuation 2._ODATA-569 <https://tools.oasis-open.org/issues/browse/ODATA-569>_ Allow type-cast segment after function/action call in path expressions 3._ODATA-590 <https://tools.oasis-open.org/issues/browse/ODATA-590>_ Leading zeroes in values for $level 4._ODATA-604 <https://tools.oasis-open.org/issues/browse/ODATA-604>_ Add type cast segment for complex types in rules for $select and $expand ii. OData CSDL 1._ODATA-559 <https://tools.oasis-open.org/issues/browse/ODATA-559>_ Clarify that Derived types inherit HasStream property 2._ODATA-566 <https://tools.oasis-open.org/issues/browse/ODATA-566>_ 6.2.4 Attribute Scale: clarify allowed range of Scale values 3._ODATA-570 <https://tools.oasis-open.org/issues/browse/ODATA-570>_ Clearify behavior of edm:UrlRef expression 4._ODATA-603 <https://tools.oasis-open.org/issues/browse/ODATA-603>_ Primitive type Edm.Stream: use as type of collection, input parameter, return type, or underlying type of type definition 5._ODATA-605 <https://tools.oasis-open.org/issues/browse/ODATA-605>_ Annotation target path syntax insufficient to annotate contained entity sets 6._ODATA-606 <https://tools.oasis-open.org/issues/browse/ODATA-606>_ Specify navigation property binding combined with containment 7._ODATA-620 <https://tools.oasis-open.org/issues/browse/ODATA-620>_ Replace "scalar type" with "primitive type" and "scalar property" with "structural property" 8._ODATA-621 <https://tools.oasis-open.org/issues/browse/ODATA-621>_ Clarify: Specifying an unbound function with overloads in a function import should import all overloads of that function to the entity container 9._ODATA-625 <https://tools.oasis-open.org/issues/browse/ODATA-625>_ Add example for UrlRef in attribute notation iii. OData JSON Format 1._ODATA-596 <https://tools.oasis-open.org/issues/browse/ODATA-596>_ Discrepancy between order of elements for geo-positions between GeoJSON and GML may cause interoperability difficulties. 2._ODATA-587 <https://tools.oasis-open.org/issues/browse/ODATA-587>_ Add example for complex value that is an empty object 3._ODATA-592 <https://tools.oasis-open.org/issues/browse/ODATA-592>_ JSON example 11: "type":"Point" with uppercase P according to GeoJSON spec 4._ODATA-594 <https://tools.oasis-open.org/issues/browse/ODATA-594>_ Discrepancy between ATOM and JSON formats (GML, GeoJson) for Polygon information content 5._ODATA-597 <https://tools.oasis-open.org/issues/browse/ODATA-597>_ Seeking clarification of naming for GeographyCollection with GeoJSON 6._ODATA-598 <https://tools.oasis-open.org/issues/browse/ODATA-598>_ Update JSON RFC reference 7._ODATA-599 <https://tools.oasis-open.org/issues/browse/ODATA-599>_ Let's update the GeoJSON reference 8._ODATA-600 <https://tools.oasis-open.org/issues/browse/ODATA-600>_ Ensure future compatibility by reference to draft-bray-i-json-n (The I-JSON Message Format) 9._ODATA-607 <https://tools.oasis-open.org/issues/browse/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 <https://tools.oasis-open.org/issues/browse/ODATA-578>_ Contains example has order of arguments backwards 2._ODATA-580 <https://tools.oasis-open.org/issues/browse/ODATA-580>_ 8.2.4 If-Match should refer to term Core.OptimisticConcurrency 3._ODATA-591 <https://tools.oasis-open.org/issues/browse/ODATA-591>_ Part1, examples 36-40: replace "associated" with "related" 4._ODATA-609 <https://tools.oasis-open.org/issues/browse/ODATA-609>_ Section 11.4.4 Upsert: key values in URL win over key values in request body 5._ODATA-610 <https://tools.oasis-open.org/issues/browse/ODATA-610>_ 11.4.4: Upsert and server-generated keys 6._ODATA-612 <https://tools.oasis-open.org/issues/browse/ODATA-612>_ Consistently use "edit link" and "edit URL" 7._ODATA-623 <https://tools.oasis-open.org/issues/browse/ODATA-623>_ 11:4.3: be more specific on updating key properties 8._ODATA-624 <https://tools.oasis-open.org/issues/browse/ODATA-624>_ Clarify that (clients and) services may include additional format parameters in Content-Type header. 9._ODATA-632 <https://tools.oasis-open.org/issues/browse/ODATA-632>_ "Core.OptimisticConcurrencyControl" should be "Core.OptimisticConcurrency" v. OData URL Conventions 1._ODATA-562 <https://tools.oasis-open.org/issues/browse/ODATA-562>_ 5.1.1.4.29: cast function is optional for first four rules 2._ODATA-564 <https://tools.oasis-open.org/issues/browse/ODATA-564>_ 5.1.1.4.28: define "assignable" 3._ODATA-602 <https://tools.oasis-open.org/issues/browse/ODATA-602>_ Explicitly state what's allowed after /$all 4._ODATA-608 <https://tools.oasis-open.org/issues/browse/ODATA-608>_ Explicitly state that the path segment /$count can be combined with $search and $filter, and that the calculated count is identical to $count=true 5._ODATA-611 <https://tools.oasis-open.org/issues/browse/ODATA-611>_ Explicitly state that the service root URL ends with a forward-slash 6.Next meeting [9:40am PT] a.Thursday April 03, 2014 during 8-10am PT? 7.AOB and wrap up [9:50am 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]