Added ODATA-239, ODATA-240 and ODATA-243 for opening and link to timeline.
Best regards, Barbara
_____________________________________________
From: Hartel, Barbara
Sent: Dienstag, 5. Februar 2013 17:59
To: odata@lists.oasis-open.org
Subject: Agenda for OData TC meeting 2013.02.07
Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday February 7, 2013 during 8-9am 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 2013.02.07 OData TC meeting
- Roll call [8:00am PT]
- Approve agenda [8:05am PT]
- Approve minutes from previous meeting(s) [8:10am PT]
- Minutes of 2013-01-30/31 Meeting#23: https://www.oasis-open.org/committees/download.php/48116/odata-meeting-23_on-20130130_31-F2F-minutes.html
- Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]
- Action items due by February 7, 2013
- #0005 Come up with a first milestone for the temporal extension (Andrew Eisenberg) – Close and set due date for
proposal(action item #0018) to next f2f, April 26.
- #0006 Come up with estimate for first milestone for XML data extension (Andrew Eisenberg) – Close and set due
date for proposal (action item #0019) to next f2f, April 26.
- #0007 Come up with estimate for first milestone for JSON data extension (Susan Malaika) – Set due date to next
f2f, April 26.
- #0028 Introduce fix target versions 4.0, minor and next major into JIRA (Ram Jeyaraman) – Set due date to February
14.
- Action items NOT due by February 7, 2013 but MAY be ready for closure
- Any?
- Process issues [Issues list: https://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10103]
[8:20am PT]
- Issues in Applied state
- ODATA-11 date/time values without explicit time zones need further investigation
- ODATA-107 Should OData support a "clock time" (xs:time) datatype?
- ODATA-194 Inside section 4.1.1 The Version Attribute, the version defined by this spec should be 4.0 and not 1.0 for the EDMX wrapper
- ODATA-195 Simplify entity set qualification rules for NavigationPropertyBinding
- ODATA-60 Allow complex properties or components of complex properties as key parts
- Issues in Proposed state
- CSDL
- ODATA-235: Limit primitive types allowed
as key parts to the "sufficiently discrete" types (New)
- ODATA-234: Merge Reference and AnnotationReference
element (New)
- ODATA-227: Support of symbolic names in
annotations (New)
- ODATA-217: property facets in ValueTerm
element (New)
- ODATA-216: Allow edm:Documentation element
in edm:TypeDefinition element (Resolved)
- ODATA-173: Define Action values for OnDelete
element (Open)
- Vocabularies
- ODATA-202: Custom Mapping to Atom Elements
not defined (New)
- ODATA-201: Allow specifying a list of acceptable
media types for media entities and named resource properties (New)
- ODATA-192: Define core vocabulary term
as a replacement for StoreGeneratedPattern attribute (New)
- ODATA-43: No indicator for optimistic concurrency
control on EntityType or EntitySet level (New)
- Atom & JSON
- ODATA-212: Define request body format for
Actions in Atom and JSON format specifications (New)
- ODATA-221: Flatten the message element
in the JSON Error Represention (Section 4.18 Representing Errors in a Response) (New)
- ODATA-68: Describe representation of ReferenceTypes
in responses (New)
- Issues in New state to be Opened
- ODATA-239: Allowing expressions to be passed as parameters to (super) functions
- ODATA-240: Better describe, and possible extend, expected behavior of dealing with async $batch requests
- ODATA-243: Add client preferences for server-driven paging
- Next meeting [8:58am PT]
- Next weekly TC meeting will be February 14, 2013 during 8-9am PT.
- AOB and wrap up [8:59am PT]
[2] References
[3] Timeline