[1] Agenda
for 2013.05.16 OData TC meeting
1.
Roll call [8:00am PT]
2.
Approve agenda [8:05am PT]
3.
Approve minutes from previous meeting(s)
[8:10am PT]
a.
Minutes
from May 9, 2013 TC meeting:
https://www.oasis-open.org/apps/org/workgroup/odata/download.php/49125/odata-meeting-36_on-20130509-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 by May 16, 2013
i. None
b.
Action items NOT due by May 16, 2013 but
MAY be ready for closure
i. Any?
5.
Preparing towards Committee
Specification Draft 02
a.
Reminder – as discussed earlier, please
file significant technical issues by June 2nd if
possible.
b.
Review timeline [3] for CSD02.
6.
5th TC face-to-face meeting (https://www.oasis-open.org/apps/org/workgroup/odata/manage/modify_event.php?day=&event_id=34201)
a.
Any questions?
7.
Process issues [Issues list:
https://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10103] [8:30am PT]
a.
Public review issues to be
reviewed
i. ODATA-387:
Replace
(at least) the second example in Section 13 of the CSDL
document (public comment c201305e00002)
b.
Issues in Proposed state (may be
ripe for resolution) (carried over from May 9, 2013)
i. OData
CSDL
1.
ODATA-364:
Explicitly
state that the restriction that a property MUST NOT have the
same name as its containing type only applies to directly
declared properties [Open]
ii. OData
Protocol
1.
ODATA-379:
Ensure
consistency and clear description in specification of $count
for 'Delta Responses' (public comment c201305e00000)
[Open]
2.
ODATA-296:
Change
tracking may require server-side state, but client cannot
advise server to stop tracking in order to allow server to
release resources
[Closed with no action?]
iii. OData
ATOM Format, OData JSON Format, OData Protocol
1.
ODATA-351:
Define
ID, ReadLink and EditLink in Part 1: Protocol, define
representation in Atom and JSON [Open]
c.
Issues in Proposed state (may
need deeper discussion) (carried over from May 9, 2013)
i. OData
Protocol
1.
ODATA-262:
Specify
how OData services can be protected against cross-site
request forgery (CSRF or XSRF) [Open]
ii. OData
Protocol, OData URL Conventions
1.
ODATA-314:
CLONE
- Please clarify the meaning of filter functions applied to
DateTimeOffset values [Open]
iii. OData
CSDL, OData Protocol, OData URL Conventions
1.
ODATA-126:
Metadata
as an OData service [Open]
iv. OData
JSON Format
1.
ODATA-316:
Allow
omitting properties with null or default values from
responses [Open]
v. OData
CSDL
1.
ODATA-346:
Order
of child elements of <edm:Collection> is significant
[New]
vi. OData
CSDL, OData Protocol
1.
ODATA-295:
Services
should be able to "advertise" what form of change tracking
they support [New]
d.
Issues in Proposed state (since
May 9, 2013)
i. OData
JSON Format
1.
ODATA-388:
Rename
"when" to "odata.when" and allow it in added/changed
entities
2.
ODATA-390:
Additional
description of use of GeoJSON in OData JSON.
e.
Issues in Applied state
i. OData
Protocol
1.
ODATA-301:
Guidance
around data authorization model and secure authenticated
access to an OData Service
1.
ODATA-219:
Detail
state and procedures in format agnostic description of
In-Stream Error handling
[Closed already?]
ii. OData
Extension for Data Aggregation
1.
ODATA-164:
Consider
syntax and rules around client specifying custom aggregation
functions for rollups
6.
Next meeting [9:58am PT]
a.
May 16, 2013 8-10am PT?
7.
AOB and wrap up [9:59am 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/49178/TC%20Timeline%205.htm