Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday February 21, 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.21 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 14, 2013 TC meeting: https://www.oasis-open.org/committees/download.php/48291/odata-meeting-25_on-20130214-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 21, 2013
- None
- Action items NOT due by Feb 21, 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 14, 2013 TC meeting)
- OData Protocol v1.0
- ODATA-253: Clients should be prepared to handle unadvertised properties
[New]
- ODATA-247: More clearly define extensibility of Formats [New]
- ODATA-255: Consider adding support for requesting flattened results
[New]
- ODATA-243: Add client preferences for server-driven paging [New]
- ODATA-261: Improve section 10.2.3.8 The $format System Query Option
[New]
- OData CSDL v1.0
- ODATA-269: Separate Functions and Actions [New]
- ODATA-237: Require type usage to always specify a qualified name for types
other than the built-in primitive types [New]
- ODATA-273: Clarify whether derived types MUST introduce new properties
[New]
- ODATA-268: Use http://docs.oasis-open.org/odata/ns/edm/4.0 as the EDM namespace
URL [New]
- ODATA-272: FixedLength facet is Boolean [New]
- ODATA-258: Advertise parameter-less function imports in service document
[New]
- ODATA-76: new boolean facet FixedScale or VariableScale to make clients
aware of floating point semantics [Open]
- OData URL Conventions v1.0
- ODATA-215: Remove hour(), minute() and second() query functions and add
corresponding overloads to the hours(), minutes(), and seconds() functions [New]
- ODATA-122: Please clarify the meaning of filter functions applied to DateTimeOffset
values [New]
- OData JSON v1.0
- ODATA-259: Add Annotation Groups to JSON format [New]
- ODATA-249: "Kind" property should be optional for EntitySets in JSON Service
Documents [New]
- OData ATOM v1.0
- ODATA-250: For instance annotations in Atom, "Annotation" element, "Type",
"Term" and "Target" attributes should be lower case [New]
- ODATA-251: Clarify, within [ATOM], that complex types can be annotated
[New]
- ODATA-252: Clarify ordering of instance annotations in [ATOM] and [JSON]
[New]
- ODATA-254: Selection of individual properties in [ATOM] should not include
property name [New]
- OData ABNF Construction Rules v1.0, OData URL Conventions v1.0
- ODATA-222: free-text search within a property [New]
- OData ABNF Construction Rules v1.0, OData Protocol v1.0, OData URL Conventions v1.0
- ODATA-228: Specify $search for free-text search within a OData Service
and specify $search for free-text search within an entityContainer [New]
- Editorial issues in Proposed state, planned to be processed in a group without detailed discussion. Please have a look at and speak up if you want a discussion on specific issues
- ODATA-146 Add example for inlining expanded entities [New] (OData ATOM Format v1.0)
- ODATA-147 Add example for $inlinecount representation [New] (OData ATOM Format v1.0)
- ODATA-153 Atom: Add examples for all request and response types using
a consistent sample OData service [New] (OData ATOM Format v1.0)
- ODATA-152 JSON: Add examples for all request and response types using
a consistent sample OData service [New] (OData JSON Format v1.0)
- ODATA-178 Enhance abstract, distinguish its content from 1st paragraph
of introduction and edit the payload object listing in 2nd para of 1 Introduction [New] (OData ATOM Format v1.0)
- ODATA-179 Adapt OData inter document references to new work product
structuring of core [New] (OData ATOM Format v1.0)
- Editorial issues in Proposed state to be discussed in the meeting
- ODATA-214 Find consensus on "Additional artifacts"-section of multi
component Work Products (and implement accordingly) [New]
- Issues in Applied state
- OData ABNF Construction Rules v1.0 OData ATOM Format v1.0 OData CSDL v1.0 OData JSON Format v1.0 OData Protocol v1.0
- ODATA-96 Need to define semantics, serialization format, etc. for Enums
- OData ABNF Construction Rules v1.0 OData CSDL v1.0
- ODATA-225 Define Functions in Schema; reference in Container using FunctionImport
- OData ABNF Construction Rules v1.0 OData URL Conventions v1.0
- ODATA-230 Support use of parameter aliases in $filter and $orderby
- OData ATOM Format v1.0 OData JSON Format v1.0
- ODATA-221 Flatten the message element in the JSON Error Represention (Section 4.18 Representing Errors in a Response)
- OData ATOM Format v1.0 OData JSON Format v1.0 OData Protocol v1.0
- ODATA-212 Define request body format for Actions in Atom and JSON format specifications
- OData ATOM Format v1.0
- ODATA-202 Custom Mapping to Atom Elements not defined (editorial)
- ODATA-162 Define OASIS XML namespaces for data: and metadata: in Atom payloads
- OData Protocol v1.0
- ODATA-110 Track Prefer Header in Http
- 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
- Issues in Proposed state (since Feb 14, 2013)
- 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-129 Explicitly mention dynamic navigation properties in [Core] [Open]
- 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]
- Next F2F meeting [9:50am PT]
- April 25/26 in Walldorf, Germany
- Next meeting [9:58am PT]
- Feb 28, 2013 during 8-10am PT
- AOB and wrap up [9:59am PT]
[2] References
[3] Timeline