[odata] Agenda for OData TC meeting on 2015-02-05

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

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

 

[1] Agenda

 

1.         Roll call [8:00am PT]

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

 

2.         Approve agenda [8:05am PT]

 

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

a.     Minutes from January 15, 2015 TC meeting: https://www.oasis-open.org/committees/download.php/54951/odata-meeting-89_on-20150115-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

                                         i.     None

 

5.         Process issues [Issues list: https://issues.oasis-open.org/issues/?jql=project%20%3D%20ODATA] [8:20am PT]

a.     Issues for V4.0_ERRATA03 in Applied state

                                         i.     OData CSDL

1.     ODATA-746 12.2.3: IsComposable - clarify what is allowed even if set to false

2.     ODATA-733 Clarify handling of cycles in Extends for EntityContainers

3.     ODATA-752 Bug in example 47

4.     ODATA-751 Clarification of Edm.NavigationPropertyPath and Edm.PropertyPath

5.     ODATA-742 Usage of domain contoso.com and term name contoso in examples (affects also OData JSON Format and OData Protocol)

 

                                        ii.     OData JSON Format

1.     ODATA-745 Sections 4.5.5, 7.3, and 7.4: is odata.nextLink allowed for all collections?

2.     ODATA-748 Section 4.5.4: odata.count needs to be allowed for all collections

3.     ODATA-756 Clarify when odata.metadataEtag will be returned

4.     ODATA-750 Explicitly mention the @ sign in instance annotations

5.     ODATA-740 Let's update the GeoJSON reference (again)

6.     ODATA-731 Explicitly state that JSON service documents may contain annotations

 

                                      iii.     OData Protocol

1.     ODATA-749 What should service return when attempting to related two entities that are already related?

 

                                      iv.     OData URL Conventions

1.     ODATA-741 Mismatch between explanatory text and URL in example 96

2.     ODATA-755 Construction rule for canonical URL is incomplete

3.     ODATA-758 Example 81: wrong parameter style

 

                                       v.     OData Vocabularies

1.     ODATA-732 Add enumeration member "Write" to "Permission" type

 

b.     Issues for V4.0_ERRATA03 in New or Open state

                                         i.     OData JSON Format

1.     ODATA-770 18.2: incomplete description of annotation name format

2.     ODATA-771 Exponential notation for Edm.Decimal values in JSON payloads

3.     ODATA-773 Qualifiers for instance annotations: JSON Format

 

                                        ii.     OData Protocol

1.     ODATA-774 Qualifiers for annotations: Preference odata.include-annotations

2.     ODATA-479 Allow Content-ID referencing in request bodies for inserting links to newly created entities

3.     ODATA-776 Clarify function invocation

 

6.         Next meeting [9:50am PT]

a.     Thursday February 12 or 26, 2015 during 8-10am PT?

 

7.         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/document.php?document_id=54822&wg_abbrev=odata