Agenda for OData TC meeting 2013.04.11

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday April 11, 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. A link to an online meeting will be provided in the chat room.

 

Thanks.

 

[1] Agenda for 2013.04.11 OData TC meeting

Roll call [8:00am PT]

 

Approve agenda [8:05am PT]

 

Approve minutes from previous meeting(s) [8:10am PT]

Minutes from April 4, 2013 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/48752/odata-meeting-31_on-20130404-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 Feb 28, 2013 

None

Action items NOT due by Feb 28, 2013 but MAY be ready for closure

Any?

 

Review OData ATOM Format Version 4.0 (document on skydrive,
discuss comments) ] [8:20am PT]

 

Review OData JSON Format Version 4.0  (document on skydrive,
discuss comments) ] [8:50am PT]

 

Process issues in applied state. A short comment if the issues is applied as proposed or if there has been difficulties when applying.  [9:20am PT]

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

OData Protocol

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

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

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

OData CSDL

ODATA-284: Annotating an Annotation

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

OData ABNF Construction Rules, OData CSDL, OData Protocol

ODATA-244: Support navigation properties on complex types

OData CSDL, OData Protocol

ODATA-204: Define namespace versioning policy for XML namespaces

OData JSON Format

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

OData ABNF Construction Rules, OData Protocol, OData URL Conventions

ODATA-159: Handling inline attachments in requests/responses

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

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

ODATA-280: Support cast segment in $expand 

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

OData ABNF Construction Rules, OData URL Conventions 

ODATA-222: free-text search within a property

OData URL Conventions

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

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

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

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

OData ABNF Construction RulesOData CSDL

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

OData ABNF Construction Rules OData URL Conventions

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

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

OData ABNF Construction RulesOData CSDL OData Protocol OData URL Conventions

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

OData Atom Format OData CSDL OData JSON Format

ODATA-68 Describe representation of ReferenceTypes in responses

OData CSDL

ODATA-288 Change default decimal Scale to variable 

ODATA-277 Remove Collation attribute

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

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

OData Protocol

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

ODATA-246 IDs should be dereferenceable URIs

ODATA-111 Define supported numeric promotions

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

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

OData JSON Format

ODATA-300 Valid Syntax in JSON samples

URL Conventions

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

Vocabularies

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

Issues in Applied state since April 4, 2013

OData Protocol

ODATA-321 Use consistent naming for headers

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

ODATA-31 Section 9.1.3: Describe call choreography for 202 Accepted (Async responses)

OData JSON Format OData Protocol

ODATA-283 Accept-Charset HTTP Request Header and charset content-type parameter

 

Next meeting [9:58am PT]

April 18, 2013 during 8-10am PT

 

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/48148/TC%20Timeline%203.htm