Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday February 28, 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.02.28 OData TC meeting
- Roll call [8:00am PT]
- Approve agenda [8:05am PT]
- Approve minutes from previous meeting(s) [8:10am PT]
- Minutes from February 21, 2013 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/48346/odata-meeting-26_on-20130221-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?
- Process issues [Issues list: https://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10103]
[8:20am PT]
- Issues in Proposed state state (carried over from Feb 21, 2013 TC meeting)
- OData ABNF Construction Rules v1.0 OData URL Conventions v1.0
- ODATA-263 Remove $select=* [New]
- OData ATOM Format v1.0 OData JSON Format v1.0
- ODATA-68 Describe representation of ReferenceTypes in responses [New]
- ODATA-265 Allow omitting key properties from PUT and PATCH request bodies and from nested entities in deep-insert requests
[New]
- OData ATOM Format v1.0
- ODATA-200 Remove metadata:type attribute from example in section 5.1 [New]
- OData CSDL v1.0
- ODATA-43 No indicator for optimistic concurrency control on EntityType or EntitySet level [New]
- ODATA-173 Define Action values for OnDelete element [Open]
- ODATA-201 Allow specifying a list of acceptable media types for media entities and named resource properties [New]
- ODATA-234 Merge Reference and AnnotationReference element [Open]
- ODATA-236 Define maximum length of namespace names and simple identifiers [New]
- ODATA-242 Allow Path expressions also for annotations targeting an entity container [New]
- ODATA-257 Define standard client-side function for filling URL templates (RFC6570) [New]
- ODATA-266 Strengthen the requirements for the URL Attribute in edmx:Reference and edmx:AnnotationReference [New]
- ODATA-267 Allow Qualifier attribute on Annotation elements within an Annotations element that does NOT specify a Qualifier
attribute [New]
- OData JSON Format v1.0
- ODATA-102 5.4.1/2 Representing Actions/Functions Bound to Multiple Entities [Open]
- OData Protocol v1.0
- ODATA-37 UPSERT: allow PUT and PATCH to the URL of a not yet existing entity to create this entity [New]
- ODATA-42 8.2.5 If-None-Match: clarify use of If-None-Match in data modification or action requests [New]
- ODATA-204 Define namespace versioning policy for XML namespaces [New]
- ODATA-244 Support navigation properties on complex types [New]
- ODATA-246 IDs should be dereferenceable URIs [New]
- ODATA-260 Make explicit that DELETE on an entity may implicitly change links to and from other entities [New]
- ODATA-262 Specify how OData services can be protected against cross-site request forgery (CSRF or XSRF) [New]
- OData URL Conventions v1.0
- ODATA-264 Allow omitting parent key(s) in URLs to contained children [New]
- Vocabularies
- ODATA-192 Define core vocabulary term as a replacement for StoreGeneratedPattern attribute [New]
- Issues in Applied state
- OData ABNF Construction Rules OData ATOM Format OData CSDL OData JSON Format OData Protocol OData URL Conventions
- ODATA-214 Find consensus on "Additional artifacts"-section of multi component Work Products (and implement accordingly)
- ODATA-179 Adapt OData inter document references to new work product structuring of core
- OData ABNF Construction Rules OData URL Conventions
- ODATA-215 Remove hour(), minute() and second() query functions and add corresponding overloads to the hours(), minutes(),
and seconds() functions
- OData ATOM Format
- ODATA-251 Clarify, within [ATOM], that complex types can be annotated
- ODATA-250 For instance annotations in Atom, "Annotation" element, "Type", "Term" and "Target" attributes should be lower
case
- ODATA-178 Enhance abstract, distinguish its content from 1st paragraph of introduction and edit the payload object listing
in 2nd para of 1 Introduction
- ODATA-147 Add example for $inlinecount representation
- ODATA-146 Add example for inlining expanded entities
- OData CSDL
- ODATA-273 Clarify whether derived types MUST introduce new properties
- ODATA-272 Remove FixedLength facet
- ODATA-268 Use
http://docs.oasis-open.org/odata/ns/edm as the EDM namespace URL
- ODATA-237 Require type usage to always specify a qualified name for types other than the built-in primitive types
- ODATA-76 Edm.Decimal is a floating-point type
- OData CSDL OData Protocol
- ODATA-269 Separate Functions and Actions
- OData JSON Format
- ODATA-249 "Kind" property should be optional for EntitySets in JSON Service Documents
- OData Protocol v1.0
- ODATA-110 Track Prefer Header in Http
- ODATA-129 Explicitly mention dynamic navigation properties in
- ODATA-261 Improve section 10.2.3.8 The $format System Query Option
- ODATA-103 5.4.1 Representing Actions Bound to Multiple Entities: specify treatment of action overloads
- OData URL Conventions v1.0
- ODATA-142 Define URL functions geo.distance, geo.length, geo.intersects, and gettotaloffsetminutes
- ODATA-140 Describe rules for accessing derived entity and complex types in URLs
- ODATA-203 Specify Operator Precedence more clearly
- ODATA-104 Consider supporting nullable complex typed properties
- ODATA-72 Describe any() and all() lambda filter expressions
- ODATA-122 Please clarify the meaning of filter functions applied to DateTimeOffset values
- Issues in Proposed state (since Feb 21, 2013)
- OData ABNF Construction Rules OData Protocol OData URL Conventions
- ODATA-280 Support cast segment in $expand [New]
- OData ATOM Format OData CSDL OData JSON Format OData Protocol OData URL Conventions
- ODATA-276 Fix issues with entity references and rationalize with $links [New]
- OData CSDL
- ODATA-275 Clarify that binding parameters for actions and functions cannot be nullable [New]
- ODATA-278 Introduce vocabulary _expression_ edm:Url [New]
- OData Protocol OData URL Conventions
- ODATA-274 OData clients should always use PATCH, deprecate PUT [New]
- OData URL Conventions
- ODATA-279 Define URL conventions for addressing functions and function imports [New]
- Next meeting [9:58am PT]
- March 07, 2013 during 8-10am PT
- AOB and wrap up [9:59am PT]
[2] References
[3] Timeline