OASIS Open Data Protocol (OData) TC

 View Only

[odata] Agenda for OData TC meeting on 2015-09-24

  • 1.  [odata] Agenda for OData TC meeting on 2015-09-24

    Posted 09-23-2015 14:22
    Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday September 24, 2015 during 8-10am PDT (17:00-19:00 CEST) . 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   1.         Roll call [8:00am PT] a.      Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=39117   2.         Approve agenda [8:05am PT]   3.         Approve minutes from previous meeting(s) [8:10am PT] a.      Minutes from September 17, 2015 TC meeting: https://www.oasis-open.org/committees/download.php/56539/odata-meeting-105_on-20150917-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                                   i.     None   5.         Discuss grouping of issues for V4.01 [8:20am PT] a.      Issues for V4.01_WD01 in New or Open state                                   i.     Annotations 1.      ODATA-516 Add super type Edm.AnyPath for Edm.PropertyPath, Edm.NavigationPropertyPath, and Edm.AnnotationPath 2.      ODATA-735 Enhance the CSDL for instance annotations 3.      ODATA-786 Extend definition of edm:Path _expression_ 4.      ODATA-811 Define propagation and (partial) overriding of annotations 5.      ODATA-631 Allow expressing that a term can be applied any collection and is not restricted to entity sets                                    ii.     Batch 1.      ODATA-480 $batch: remove restriction "within the same change set " for Content-ID referencing 2.      ODATA-541 Allow the If-Match header to reference the ETag that resulted from an earlier operation in a batch request                                   iii.     Complex Types 1.      ODATA-560 Allow arbitrary properties in referential constraints 2.      ODATA-572 Clarify that eq, ne can be used with complex type 3.      ODATA-617 Allow eq/ne comparison of instances of same structured (complex or entity) type, allow eq/ne comparison with null for 0..1 nav props                                   iv.     Decimal 1.      ODATA-557 Allow exponential notation for Edm.Decimal 2.      ODATA-747 Allow IEEE 754 constants [-]INF and NaN also for Edm.Decimal                                    v.     Enum Types 1.      ODATA-494 Define inheritance for enumeration types 2.      ODATA-849 Add possibility for enumeration types to "extend" another enumeration type                                   vi.     Interfaces 1.      ODATA-619 Attach action and function signatures to terms, i.e. make a term definition an interface definition 2.      ODATA-696 Support "interfaces" for casting entities to multiple different types                                  vii.     New Query Capabilities 1.      ODATA-482 Allow inlining stream properties and media resources 2.      ODATA-614 Allow $expand, $select, ... with POST/PATCH/PUT in combination with return=representation to specify the response shape 3.      ODATA-827 introduce $compute query option 4.      ODATA-556 Add "in" operator as syntactic sugar for a chain of "or" expressions 5.      ODATA-820 Allow indexing into collections                                 viii.     Set Operations 1.      ODATA-666 Define Deep Update and Deep Upsert operations 2.      ODATA-836 Allow applying actions to a filtered collection of entities 3.      ODATA-613 Allow POST to entity sets using the delta-response format 4.      ODATA-615 Allow PATCH and DELETE with $filter on collections to modify or delete all (and only) the matching entities 5.      ODATA-616 Allow POST to collections of complex and primitive types, and DELETE with $filter                                   ix.     Simplified Payload 1.      ODATA-561 odata.type shouldn't require "#" for primitive types 2.      ODATA-630 Consider making odata the default namespace for annotations 3.      ODATA-813 Allow no metadata for non-OData clients 4.      ODATA-814 Don't need TargetId in a deleted link for a to 0..1 relationship 5.      ODATA-809 Define non-message format for final response of async request                                    x.     Simplified Syntax 1.      ODATA-664 Consider supporting parameterless function imports with no parens 2.      ODATA-812 Allow omitting namespaces for unambiguous functions/actions 3.      ODATA-763 Allowing implicit aliasing of parameters (public comment c201412e00001) 4.      ODATA-799 Define Key-As-Segment URL convention for resource paths 5.      ODATA-834 Make type prefix optional for enumeration literals in URLs                                   xi.     OData CSDL 1.      ODATA-674 Specify navigation property binding combined with containment 2.      ODATA-618 Allow using term names in positions that allow type names 3.      ODATA-743 Restructure/rename documents CSDL, JSON Format, and JSON Format for CSDL 4.      ODATA-798 Semantic Key or Alternate Key for entity types 5.      ODATA-817 Add client-side function odata.matchesRegularExpression                                  xii.     OData JSON Format 1.      ODATA-656 Requesting clarity on payload ordering constraints for clients 2.      ODATA-838 Allow inclusion of "untyped JSON" into JSON requests and responses                                 xiii.     OData Protocol 1.      ODATA-824 Header Content-Transfer-Encoding not used in HTTP 2.      ODATA-846 Add version 4.01                                xiv.     OData URL Conventions 1.      ODATA-850 Improve document structure for functions used in common expressions                                 xv.     Vocabularies 1.      ODATA-571 Add annotation for properties that are (not) part of the default selection if no $select is specified 2.      ODATA-760 Add to depth restrictions to Capabilities Vocabulary 3.      ODATA-816 Add Capability term for filter _expression_ restrictions   6.         Process issues [Issues list: https://issues.oasis-open.org/issues/?jql=project%20%3D%20ODATA ] [8:35am PT] a.      Issues for V4.01_WD01 in New or Open state                                   i.     OData URL Conventions 1.      ODATA-850 Improve document structure for functions used in common expressions                                    ii.     OData Protocol 1.      ODATA-824 Header Content-Transfer-Encoding not used in HTTP 2.      ODATA-846 Add version 4.01                                   iii.     New Query Capabilities 1.      ODATA-482 Allow inlining stream properties and media resources 2.      ODATA-614 Allow $expand, $select, ... with POST/PATCH/PUT in combination with return=representation to specify the response shape 3.      ODATA-827 introduce $compute query option 4.      ODATA-556 Add "in" operator as syntactic sugar for a chain of "or" expressions 5.      ODATA-820 Allow indexing into collections                                   iv.     Set Operations 1.      ODATA-666 Define Deep Update and Deep Upsert operations 2.      ODATA-836 Allow applying actions to a filtered collection of entities 3.      ODATA-613 Allow POST to entity sets using the delta-response format 4.      ODATA-615 Allow PATCH and DELETE with $filter on collections to modify or delete all (and only) the matching entities 5.      ODATA-616 Allow POST to collections of complex and primitive types, and DELETE with $filter   7.         Next meeting [9:50am PT] a.      Thursday October 01, 2015 during 8-10am PT?   8.         AOB and wrap up [9:55am 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/document.php?document_id=56024&wg_abbrev=odata