Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday January 08, 2015 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 and Happy Holidays! [1] Agenda for 2014-12-11 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=39080 2. Approve Agenda [8:05am PT] 3. Approve minutes from previous meeting(s) [8:10am PT] a. Minutes from 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 January 08, 2015 i. None 5. Issues for V4.0_ERRATA03 in Applied state [8:20am PT] a. Vocabularies i. ODATA-732 Add enumeration member "Write" to "Permission" type b. OData URL Conventions i. ODATA-741 Mismatch between explanatory text and URL in example 96 ii. ODATA-753 Minor typo in references to bound function calls iii. ODATA-755 Construction rule for canonical URL is incomplete iv. ODATA-758 Example 81: wrong parameter style c. OData Protocol i. ODATA-749 What should service return when attempting to related two entities that are already related? d. OData JSON Format i. ODATA-731 Explicitly state that JSON service documents may contain annotations ii. ODATA-740 Let's update the GeoJSON reference (again) iii. ODATA-745 Sections 4.5.5, 7.3, and 7.4: is odata.nextLink allowed for all collections? iv. ODATA-748 Section 4.5.4: odata.count needs to be allowed for all collections v. ODATA-750 Explicitly mention the @ sign in instance annotations vi. ODATA-756 Clarify when odata.metadataEtag will be returned e. OData CSDL i. ODATA-733 Clarify handling of cycles in Extends for EntityContainers ii. ODATA-742 Usage of domain contoso.com and term name contoso in examples iii. ODATA-746 12.2.3: IsComposable - clarify what is allowed even if set to false iv. ODATA-751 Clarification of Edm.NavigationPropertyPath and Edm.PropertyPath v. ODATA-752 Bug in example 47 6. Issues for V4.0_ERRATA03 in New or Open state [8:20am PT] a. OData Protocol i. ODATA-479 Allow Content-ID referencing in request bodies for inserting links to newly created entities ii. ODATA-761 11.5.4.1 Invoking an Action: Location header for 201 Created responses b. OData JSON Format i. ODATA-754 Clarify that numeric enum values are serialized as strings ii. ODATA-762 Section 8.5: clarify that @odata.bind:null is valid for updating of 0..1 navigation properties c. OData CSDL i. ODATA-734 Unicode Facet is inadequate 7. OData JSON Format for Common Schema Definition Language (CSDL) [9.00am PT] a. Discuss further direction of JSON CSDL i. OData-specific JSON ii. JSON Schema with OData extensions iii. Both (i) and (ii) iv. OData-specific JSON and separately JSON Schema without OData extensions 8. Next meeting [9:50am PT] a. Thursday January 15, 2014 during 8-10am PT? 9. 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