Agenda for OData TC meeting 2013.04.04

["Ram Jeyaraman (MS OPEN TECH)" <Ram.Jeyaraman@microsoft.com>]

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

 

NOTE (attendees in Europe): Please take note of the clock change in Europe and ensure you dial-in at the appropriate local time for the TC meeting.

 

Thanks.

 

[1] Agenda for 2013.04.04 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 March 21, 2013 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/48622/odata-meeting-30_on-20130321-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 April 4, 2013

                                                         i.            None

b.      Action items NOT due by April 4, 2013 but MAY be ready for closure

                                                         i.            Any?

 

5.       Review progress and next steps towards public review [8:20am PT]

a.       Let’s review where we are (in terms of progress against timeline) and discuss/determine what we need to do in the next 3 weeks leading up to the public review starting on May 1^st. See timeline [3] for reference.

 

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

a.       Issues in Proposed state (carried over from March 14, 2013)

                                                         i.            OData CSDL

1.       ODATA-271 Support IsAlwaysBindable through annotation, rather than attribute of function/action [Open]

b.      Issues in Proposed state (since March 21, 2013 TC meeting)

                                                         i.            OData ABNF Construction Rules, OData Protocol, OData URL Conventions

1.       ODATA-263: Define whether $select=* returns only data properties or also navigation properties [Open]

                                                       ii.            OData ATOM Format, OData CSDL, OData JSON Format, OData Protocol

1.       ODATA-315: Entities that may be queryable can be omitted from service document, but then their "url" cannot be specified. [New]

                                                      iii.            OData ATOM Format, OData JSON Format

1.       ODATA-319: Allow services to include metadata links and metadata ETags into responses [New]

                                                     iv.            OData Batch Processing Format

1.       ODATA-317: Allow multiple reads in the same transaction [New]

                                                       v.            OData Protocol, OData URL Conventions

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

                                                     vi.            OData CSDL

1.       ODATA-318: Explicitly state which calendar Date and DateTimeOffset use [New]

2.       ODATA-312: ATOM and JSON formats for Service Document appear to omit information for action imports [New]

3.       ODATA-320: Should use /@<annotation-name> to reference applied annotations [New]

                                                    vii.            OData JSON Format

1.       ODATA-308: Clarify whether format parameters odata.metadata and odata.streaming may be ignored by services [New]

2.       ODATA-316: Allow omitting properties with null or default values from responses [New]

3.       ODATA-307: Return odata.etag in collections also for odata=minimalmetadata [New]

                                                  viii.            OData Protocol, OData URL Conventions

1.       ODATA-313: Problem with "Function Overload Resolution" due to null values having ambiguous type [New]

                                                     ix.            OData Protocol

1.       ODATA-306: Batch Request processing: Define server behavior, if one or more request(s) didn't succeed [New]

2.       ODATA-298: Clarify Requesting Changes to entity sets that include Stream properties [New]

3.       ODATA-321: Use consistent naming for headers [New]

4.       ODATA-326: include-annotations should allow inclusion (or exclusion) of specific terms [New]

                                                       x.            OData ATOM Format, OData JSON Format, OData Protocol

1.       ODATA-325: Clarify what aliases can be used in instance annotations [New]

2.       ODATA-324: Support external metadata references in payload [New]

                                                     xi.            OData ATOM Format, OData Extension for JSON Data, OData Protocol

1.       ODATA-322: Define how nested service documents are supported [New]

                                                    xii.            OData ABNF Construction Rules, OData Protocol

1.       ODATA-323: InlineCount should just be boolean [New]

c.       Issues in Applied state (carried over from March 7, 2013)

                                                         i.            OData Protocol

1.       ODATA-34: Control verbosity of $metadata response: include annotations or documentation

2.       ODATA-274: OData clients should always use PATCH, deprecate PUT

3.       ODATA-260: Make explicit that DELETE on an entity may implicitly change links to and from other entities

                                                       ii.            OData CSDL

1.       ODATA-284: Annotating an Annotation

2.       ODATA-267: Allow Qualifier attribute on Annotation elements within an Annotations element that does NOT specify a Qualifier attribute

                                                      iii.            OData ABNF Construction Rules, OData CSDL, OData Protocol

1.       ODATA-244: Support navigation properties on complex types

                                                     iv.            OData CSDL, OData Protocol

1.       ODATA-204: Define namespace versioning policy for XML namespaces

                                                       v.            OData JSON Format

1.       ODATA-102: 5.4.1/2 Representing Actions/Functions Bound to Multiple Entities

                                                     vi.            OData ABNF Construction Rules, OData Protocol, OData URL Conventions

1.       ODATA-159: Handling inline attachments in requests/responses

2.       ODATA-139: New system query option $search for free-text search within an entity set

3.       ODATA-228: Specify $search for free-text search within a OData Service and specify $search for free-text search within an entityContainer

4.       ODATA-280: Support cast segment in $expand

5.       ODATA-281: Keep second() as integer, introduce FractionalSeconds

                                                    vii.            OData ABNF Construction Rules, OData URL Conventions

1.       ODATA-222: free-text search within a property

                                                  viii.            OData URL Conventions

1.       ODATA-264: Allow omitting parent key(s) in URLs to contained children

                                                     ix.            OData ABNF Construction Rules, OData ATOM Format, OData JSON Format, OData Protocol, OData URL Conventions

1.       ODATA-276: Fix issues with entity references and rationalize with $links

d.      Issues in Applied state (carried over from March 14, 2013)

                                                         i.            OData ABNF Construction RulesOData CSDL

1.       ODATA-124 For round-tripping values, what precision must agents support for DateTime(Offset), and are leap seconds permitted?

                                                       ii.            OData ABNF Construction Rules OData URL Conventions

1.       ODATA-232 Enhance description of normalization procedures (public comment c201301e00001)

2.       ODATA-230 Support use of parameter aliases in $filter and $orderby

                                                      iii.            OData ABNF Construction RulesOData CSDL OData Protocol OData URL Conventions

1.       ODATA-279 Define URL conventions for addressing functions and function imports

                                                     iv.            OData Atom Format OData CSDL OData JSON Format

1.       ODATA-68 Describe representation of ReferenceTypes in responses

                                                       v.            OData CSDL

1.       ODATA-288 Change default decimal Scale to variable [seems Closed already? When did we agree to close?]

2.       ODATA-277 Remove Collation attribute

3.       ODATA-275 Clarify whether binding parameters for actions and functions can be nullable

4.       ODATA-270 Collections of Edm.PrimitiveType are problematic in JSON

                                                     vi.             OData Protocol

1.       ODATA-292 Questions on POST, PATCH and merge/replace semantics with related entities in composite relationships

2.       ODATA-246 IDs should be dereferenceable URIs

3.       ODATA-111 Define supported numeric promotions

4.       ODATA-42 8.2.5 If-None-Match: clarify use of If-None-Match in data modification or action requests

5.       ODATA-37 UPSERT: allow PUT and PATCH to the URL of a not yet existing entity to create this entity

                                                    vii.            OData JSON Format

1.       ODATA-300 Valid Syntax in JSON samples

                                                  viii.            URL Conventions

1.       ODATA-285 Section 4.7: explicitly mention which property types allow appending /$value

                                                     ix.             Vocabularies

1.       ODATA-192 Define vocabulary term as a replacement for StoreGeneratedPattern attribute

e.      Issues likely to carry over to the face-to-face meeting (during April 25-25, 2013)

1.       ODATA-239 Allowing expressions to be passed as parameters to (super) functions [Open] [Proposed]

2.       ODATA-262 Specify how OData services can be protected against cross-site request forgery (CSRF or XSRF) [Open] [Proposed]

3.       ODATA-166: Inconsistent lifted operators for $filter [Open]

4.       ODATA-126: Metadata as an OData service [Open]

5.       Issues relating to Conformance Levels

a.       ODATA-248: Define required/optional format(s) for OData [New]

b.      ODATA-224: Fill out Capabilities sections of an OData Service [New]

c.       ODATA-223: Specify Service behavior for not implemented functionality [New]

6.        Next meetings [9:58am PT]

a.       April 11, 2013 during 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