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.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.
[1] Agenda for 2013.04.11 OData TC meeting
  1. Roll call [8:00am PT]
  1. Approve agenda [8:05am PT]
  1. Approve minutes from previous meeting(s) [8:10am PT]
  1. 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
  1. Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]
  1. Action items due by Feb 28, 2013
  1. None
  1. Action items NOT due by Feb 28, 2013 but MAY be ready for closure
  1. Any?
  1. Review OData ATOM Format Version 4.0 (document on skydrive, discuss comments) ] [8:20am PT]
  1. Review OData JSON Format Version 4.0  (document on skydrive, discuss comments) ] [8:50am PT]
  1. 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]
  1. Issues in Applied state (carried over from March 7, 2013)
  1. 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
  1. 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
  1. OData ABNF Construction Rules, OData CSDL, OData Protocol
  1. ODATA-244: Support navigation properties on complex types
  1. OData CSDL, OData Protocol
  1. ODATA-204: Define namespace versioning policy for XML namespaces
  1. OData JSON Format
  1. ODATA-102: 5.4.1/2 Representing Actions/Functions Bound to Multiple Entities
  1. 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
  1. OData ABNF Construction Rules, OData URL Conventions
  1. ODATA-222: free-text search within a property
  1. OData URL Conventions
  1. ODATA-264: Allow omitting parent key(s) in URLs to contained children
  1. 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
  1. Issues in Applied state (carried over from March 14, 2013)
  1. 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?
  1. 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
  1. OData ABNF Construction RulesOData CSDL OData Protocol OData URL Conventions
  1. ODATA-279 Define URL conventions for addressing functions and function imports
  1. OData Atom Format OData CSDL OData JSON Format
  1. ODATA-68 Describe representation of ReferenceTypes in responses
  1. OData CSDL
  1. ODATA-288 Change default decimal Scale to variable
  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
  1. 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
  1. OData JSON Format
  1. ODATA-300 Valid Syntax in JSON samples
  1. URL Conventions
  1. ODATA-285 Section 4.7: explicitly mention which property types allow appending /$value
  1. Vocabularies
  1. ODATA-192 Define vocabulary term as a replacement for StoreGeneratedPattern attribute
  1. Issues in Applied state since April 4, 2013
  1. OData Protocol
  1. ODATA-321 Use consistent naming for headers
  2. ODATA-306 Batch Request processing: Define server behavior, if one or more request(s) didn't succeed
  3. ODATA-31 Section 9.1.3: Describe call choreography for 202 Accepted (Async responses)
  1. OData JSON Format OData Protocol
  1. ODATA-283 Accept-Charset HTTP Request Header and charset content-type parameter
  1. Next meeting [9:58am PT]
  1. April 18, 2013 during 8-10am PT
  1. AOB and wrap up [9:59am PT]
[2] References
[3] Timeline

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