Agenda for OData TC meeting 2014.07.03

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

2. Approve agenda [8:05am PT]

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

a. Minutes from June 12, 2014 TC meeting: https://www.oasis-open.org/committees/download.php/53453/odata-meeting-75_on-20140612-minutes.html

b. Minutes from June 26, 2014 TC meeting: TBD

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 July 3, 2014

i. None

5. Process issues [8:20am PT]

a. OData v4 Errata issues in New or Open state

a. ODATA-685: ODATA-674 Prepare clients in 4.0 to deal with nav property binding on containmnet [open]

b. ODATA-707: 4.5.3: Type inference for numeric values doesn't work with JSON.parse() [Open]

c. ODATA-712: In chapter 10 we missed to spell out various Context URL templates. [Open]

d. ODATA-713: 11.7.3 and 11.7.4: replace "query operation" with "operation"

a. Review Applied Issues from previous two meetings

1. ODATA-682: 11.4.1.5 Returning Results from Data Modification Requests - media resources and stream properties

2. ODATA-678: Clarify delta responses with containment, OnDelete, or referential constraints

3. ODATA-688: DELETE requests to raw property values, media resources, and stream properties

4. ODATA-689: Deep Insert and Media Entities

5. ODATA-680: Clarify use of if-match with actions

6. ODATA-684: Define what it means for an added property to conflict with an existing dynamic property

7. ODATA-683: Clients should be prepared to deal with new derived types

8. ODATA-681: What happens if an alias has the same name as an included namespace?

9. ODATA-586: Allow 405 Method Not Allowed when attempting to delete a non-nullable value

10. ODATA-679: 11.7.1, Example 78: OData-Version and OData-MaxVersion should be 4.0

11. Others?

b. Discuss How to Handle OData V4 Errata issues for Future Consideration

1. ODATA-631: How do annotations that target entity sets work against singletons/containment?

2. ODATA-696: Support "interfaces" for casting entities to multiple different types

3. ODATA-695: ODATA-585 Returning 200 in place of 204 no content

4. ODATA-694: ODATA-579 Dynamic actions/functions in errata

5. ODATA-692: ODATA-560 Future versions are expected to support referential constraints to complex/nav properties

6. ODATA-691: ODATA-618 Call out that services may support the use of term names in place of type names

7. ODATA-690: ODATA-557 Alert clients to new symbolic scale value "float"

8. ODATA-687: ODATA-561 Prepare clients to deal with type annotations without the leading "#"

9. ODATA-686: ODATA-630 Alert clients that odata may be default namespace in future versions of the protocol

6. Re-approve Errata Draft 01 [9:40am PT]

a. Sample motion to approve OData v4 Errata Draft 01: “I move that the TC approve OData v4.0 Errata Draft 01 Working Draft 02 and the accompanying OData v4.0 OASIS Standard (marked version) incorporating the proposed errata corrections all contained in <ZIP file> as Errata Draft 01 to the OData v4.0 OASIS Standard approved on 24 February 2014 and confirm that the errata corrections do not constitute Substantive Changes to the Standard. Further, I move that the TC approve submitting OData v4.0 Errata Draft 01 contained in <ZIP file> for 15 day public review.”

b. Sample motion to approve OData JSON Format v4 Errata Draft 01: “I move that the TC approve OData JSON Format v4.0 Errata Draft 01 Working Draft 02 and the accompanying OData JSON Format v4.0 OASIS Standard (marked version) incorporating the proposed errata corrections all contained in <ZIP file> as Errata Draft 01 to the OData JSON Format v4.0 OASIS Standard approved on 24 February 2014 and confirm that the errata corrections do not constitute Substantive Changes to the Standard. Further, I move that the TC approve submitting OData JSON Format v4.0 Errata Draft 01 contained in <ZIP file> for 15 day public review.”

7. Next meeting [9:50am PT]

a. Thursday July 17, 2014 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/52831/TC%20Timeline%207.htm

odata message