OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Agenda for OData TC meeting 2013.05.09

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




[1] Agenda for 2013.05.09 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 2, 2013 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/49055/odata-meeting-35_on-20130502-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 9, 2013

                                                         i.            None

b.      Action items NOT due by May 9, 2013 but MAY be ready for closure

                                                         i.            Any?


5.       Preparing towards Committee Specification Draft 02

a.       In order to stick to the timeline [3], we need to file any remaining technical issues ASAP, so we can process those issues (along with any public review comments) by mid-June, in time for approving CSD02 by end of June.

b.      Are there significant technical issues you plan to file? If so, when do you expect to file them?


6.       5th TC face-to-face meeting

a.       At the recently concluded face-to-face meeting in Walldorf, Germany, we discussed the possibility of holding the next F2F meeting  during the week of June 17th.

b.      Would the week of June 17 or June 10th work for you, if it were to be held in Redmond, WA?


7.       Documentation of changes between OData version 3 and version 4 [8:20am PT]

a.       Recently there were some questions about what are the changes between OData v3 and v4. Let’s discuss the next steps towards identifying what those changes are and how to publish them.


8.       Process issues [Issues list: https://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10103] [8:30am PT]

a.       Issues in Proposed state (may be ripe for resolution)

                                                         i.            OData CSDL

1.       ODATA-373: Add boolean expressions that can be used in <edm:If>

2.       ODATA-346: Order of child elements of <edm:Collection> is significant

3.       ODATA-370: Disallow Nullable facet for collection-valued properties

4.       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

                                                       ii.            OData Protocol

1.       ODATA-371: Clearly describe behavior of PUT for structural and navigation properties

2.       ODATA-369: POST to navigation link with binding information leading to a different "parent" is invalid

3.       ODATA-367: Explicitly state that server MAY expand results beyond what's requested with $expand

4.       ODATA-365: Rename edm:AssertType to edm:Cast and clarify behavior of edm:Cast and cast()

5.       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

6.       ODATA-368: Deep insert: if server responds with 201 Created it MUST respond with at least the expansion depth of the insert operation

7.       ODATA-366: Clarify whether server-generated properties can be omitted in POST, even if they are not nullable

                                                      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

                                                     iv.            OData ABNF Construction Rules, OData URL Conventions

1.       ODATA-375: Allow querying collections of complex type instances similar to querying collections of entities

                                                       v.            OData JSON Format

1.       ODATA-376: Navigation link representation for navigation properties of complex type instances

b.      Issues in Proposed state (may need deeper discussion)

                                                         i.            OData Protocol

1.       ODATA-262: Specify how OData services can be protected against cross-site request forgery (CSRF or XSRF)

                                                       ii.            OData Protocol, OData URL Conventions

1.       ODATA-314: CLONE - Please clarify the meaning of filter functions applied to DateTimeOffset values

                                                      iii.            OData CSDL, OData Protocol, OData URL Conventions

1.       ODATA-126: Metadata as an OData service

                                                     iv.            OData JSON Format

1.       ODATA-316: Allow omitting properties with null or default values from responses

                                                       v.            OData CSDL

1.       ODATA-346: Order of child elements of <edm:Collection> is significant

                                                     vi.            OData CSDL, OData Protocol

1.       ODATA-295: Services should be able to "advertise" what form of change tracking they support

c.       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

                                                       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/48609/TC%20Timeline%204.htm  



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]