Here [1] is a draft agenda for the OData TC (Technical Committee) meeting
scheduled on Thursday July 10, 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.10 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=36549
2.
Approve agenda [8:05am PT]
3.
Approve minutes from previous meeting(s) [8:10am PT]
a.
Minutes from July 3, 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 10, 2014
i.
None
5.
Process issues [8:20am PT]
a.
OData v4 Errata issues in New or Open state ready to be resolved
1.
ODATA-718:
5.1.2: Add example for $expand=Items/$count
2.
ODATA-717:
Clarify PATCH/PUT/DELETE Property/$value
3.
ODATA-622:
Allow comparison of geo types, binary to null.
4.
ODATA-719:
atom:id cannot be relative
b.
Review Applied Issues from previous two meetings
1.
ODATA-716:
Upsert does not work with OptimisticConcurrency
2.
ODATA-713:
11.7.3 and 11.7.4: replace "query operation" with "operation"
3.
ODATA-712:
In chapter 10 we missed to spell out various Context URL templates.
4.
ODATA-711:
Misleading description of {type-name} in chapter 10
5.
ODATA-710:
Unclear description in chapter 10.14 an 10.15
6.
ODATA-709:
FunctionImport in example 25, 26, 27: parentheses missing
7.
ODATA-708:
Clarify inclusion of @odata.id if key fields are not selected
8.
ODATA-707:
4.5.3: Type inference for numeric values doesn't work with JSON.parse()
9.
ODATA-706:
Substitute references to obsolete RFC2616
10.
ODATA-705:
Move example 19 to section 10.9
11.
ODATA-704:
Missing comma in JSON Delta Response example
12.
ODATA-700:
ODATA-631 Allow Annotations to target propertypath/navpropertypath rooted at entity set
13.
ODATA-699:
Include Action and Function as targets for Annotations
14.
ODATA-698:
Clarify rules around handling of custom query options when building URLs
15.
ODATA-697:
Define how/where $<content-id> can be used within a changeset
16.
ODATA-693:
ODATA-544 ReturnType should support annotations
17.
ODATA-689:
Deep Insert and Media Entities
18.
ODATA-688:
DELETE requests to raw property values, media resources, and stream properties
19.
ODATA-685:
ODATA-674 Prepare clients in 4.0 to deal with nav property binding on containment
20.
ODATA-684:
Define what it means for an added property to conflict with an existing dynamic property
21.
ODATA-683:
Clients should be prepared to deal with new derived types
22.
ODATA-682:
11.4.1.5 Returning Results from Data Modification Requests - media resources and stream properties
23.
ODATA-681:
What happens if an alias has the same name as an included namespace?
24.
ODATA-680:
Clarify use of if-match with actions
25.
ODATA-679:
11.7.1, Example 78: OData-Version and OData-MaxVersion should be 4.0
26.
ODATA-678:
Clarify delta responses with containment, OnDelete, or referential constraints
27.
ODATA-586:
Allow 405 Method Not Allowed when attempting to delete a non-nullable value
c.
Discuss How to Handle OData V4 Errata issues for Future Consideration
1.
ODATA-696:
Support "interfaces" for casting entities to multiple different types
2.
ODATA-695:
ODATA-585 Returning 200 in place of 204 no content
3.
ODATA-694:
ODATA-579 Dynamic actions/functions in errata
4.
ODATA-692:
ODATA-560 Future versions are expected to support referential constraints to complex/nav properties
5.
ODATA-691:
ODATA-618 Call out that services may support the use of term names in place of type names
6.
ODATA-690:
ODATA-557 Alert clients to new symbolic scale value "float"
7.
ODATA-687:
ODATA-561 Prepare clients to deal with type annotations without the leading "#"
8.
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 0X and the accompanying OData v4.0 OASIS Standard (marked version and clean 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 0X and the accompanying OData JSON Format v4.0 OASIS Standard (marked version and clean 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 31, 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