[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Agenda for OData TC meeting 2013.04.18
Here [1] is a draft agenda for the OData TC (Technical Committee) meeting
scheduled on Thursday April 18, 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.
Thanks. [1] Agenda for 2013.04.18 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 April 11, 2013 TC meeting:
https://www.oasis-open.org/apps/org/workgroup/odata/download.php/48829/odata-meeting-32_on-20130411-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 18, 2013
i. None
b.
Action items NOT due by April 18, 2013 but MAY be ready for closure
i. Any?
5.
Issues whose resolutions may help with the specification review [8:20am PT]
a.
ODATA-329:
Approve Editorial Changes
b.
ODATA-224:
Fill out Capabilities sections of an OData Service
c.
ODATA-324:
Support external metadata references in payload
d.
ODATA-322:
Define how nested service documents are supported
e.
ODATA-348:
Require the use of <edmx:Include> to pull in specific namespaces from <edmx:Reference>
f.
ODATA-328:
Remove MinDataServiceVersion (OData-MinVersion)
g.
ODATA-327:
Service MUST only return async if return-async is specified
6.
Specification review [8:30am PT] [NOTE: A link to an online meeting (to collectively review documents) will be provided in the chat room during the meeting]
a.
Review
OData JSON Format Version 4.0 (document on skydrive, discuss comments)
b.
Review
OData Version 4.0 Part 3: CSDL (document on skydrive, discuss comments)
c.
Review
OData Version 4.0 Part 1: Protocol (document on skydrive, discuss comments)
d.
Review
OData Version 4.0 Part 2: URL Conventions (document on skydrive, discuss comments)
7.
Process issues [Issues list:
https://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10103] [9:50am PT] [time permitting]
a.
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
b.
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
c.
Issues in Applied state (carried over from April 4, 2013)
i. 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)
ii. OData JSON Format OData Protocol
1.
ODATA-283
Accept-Charset HTTP Request Header and charset content-type parameter
d.
Issues in Applied state since April 11, 2013
i. OData CSDL
1.
ODATA-318:
Explicitly state which calendar Date and DateTimeOffset use
2.
ODATA-312:
ATOM and JSON formats for Service Document appear to omit information for action imports
3.
ODATA-305:
Annotations: introduce path segment to address the count of a collection
4.
ODATA-304:
Add TargetKey attribute to <PropertyRef> within a <ReferentialConstraint>
5.
ODATA-303:
Support abstract entity types without key properties
6.
ODATA-302:
Clarify scope uniqueness for EntityContainer name
7.
ODATA-271:
Support IsAlwaysBindable through annotation, rather than attribute of function/action
8.
ODATA-266:
Strengthen the requirements for the URL Attribute in edmx:Reference and edmx:AnnotationReference
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-223:
Specify Service behavior for not implemented functionality [New]
6.
Next meeting [9:58am PT]
a.
4th F2F meeting in Walldorf, Germany during April 25-26, 2013
b.
https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=35050
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]