OASIS Open Data Protocol (OData) TC

 View Only
  • 1.  [odata] Agenda for OData TC meeting on 2015-09-10

    Posted 09-08-2015 16:11
    Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday September 10, 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=39115   2.         Approve agenda [8:05am PT]   3.         Approve minutes from previous meeting(s) [8:10am PT] a.      Minutes from September 03, 2015 TC meeting: https://www.oasis-open.org/committees/download.php/56430/odata-meeting-103_on-20150903-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.         Process issues [Issues list: https://issues.oasis-open.org/issues/?jql=project%20%3D%20ODATA ] [8:20am PT] a.      Issues for V4.01_WD01 in New or Open state Note: we will only discuss these issues shortly to get an overview of upcoming topics                                   i.     OData Batch Processing Format 1.      ODATA-480 $batch: remove restriction "within the same change set " for Content-ID referencing                                    ii.     OData CSDL 1.      ODATA-557 Allow exponential notation for Edm.Decimal 2.      ODATA-747 Allow IEEE 754 constants [-]INF and NaN also for Edm.Decimal 3.      ODATA-516 Add super type Edm.AnyPath for Edm.PropertyPath, Edm.NavigationPropertyPath, and Edm.AnnotationPath 4.      ODATA-560 Allow arbitrary properties in referential constraints 5.      ODATA-618 Allow using term names in positions that allow type names 6.      ODATA-735 Enhance the CSDL for instance annotations 7.      ODATA-786 Extend definition of edm:Path _expression_ 8.      ODATA-811 Define propagation and (partial) overriding of annotations 9.      ODATA-674 Specify navigation property binding combined with containment 10.   ODATA-817 Add client-side function odata.matchesRegularExpression 11.   ODATA-631 Allow expressing that a term can be applied any collection and is not restricted to entity sets                                   iii.     OData JSON Format 1.      ODATA-561 odata.type shouldn't require "#" 2.      ODATA-630 Consider making odata the default namespace for annotations 3.      ODATA-814 Don't need TargetId in a deleted link for a to 0..1 relationship 4.      ODATA-838 Allow inclusion of "untyped JSON" into JSON requests and responses 5.      ODATA-656 Requesting clarity on payload ordering constraints for clients                                   iv.     OData Protocol 1.      ODATA-541 Allow the If-Match header to reference the ETag that resulted from an earlier operation in a batch request 2.      ODATA-613 Allow POST to entity sets using the delta-response format 3.      ODATA-614 Allow $expand, $select, ... with POST/PATCH/PUT in combination with return=representation to specify the response shape 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 6.      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 7.      ODATA-666 Define Deep Update and Deep Upsert operations 8.      ODATA-809 Define non-message format for final response of async request 9.      ODATA-812 Allow omitting namespaces for unambiguous functions/actions 10.   ODATA-824 Header Content-Transfer-Encoding not used in HTTP 11.   ODATA-827 introduce $compute query option                                    v.     OData URL Conventions 1.      ODATA-556 Add "in" operator as syntactic sugar for a chain of "or" expressions 2.      ODATA-836 Allow applying actions to a filtered collection of entities 3.      ODATA-572 Clarify that eq, ne can be used with complex type 4.      ODATA-820 Allow indexing into collections 5.      ODATA-834 Make type prefix optional for enumeration literals in URLs 6.      ODATA-763 Allowing implicit aliasing of parameters (public comment c201412e00001) 7.      ODATA-799 Define Key-As-Segment URL convention for resource paths                                   vi.     OData Vocabularies 1.      ODATA-696 Support "interfaces" for casting entities to multiple different types 2.      ODATA-816 Add Capability term for filter _expression_ restrictions   6.         Next meeting [9:50am PT] a.      Thursday September 17, 2015 during 8-10am PT?   7.         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      


  • 2.  RE: [odata] Agenda for OData TC meeting on 2015-09-10

    Posted 09-09-2015 10:35
    Update: added Jira issues 494, 571, 664, 763, 786, 812, 813.   From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf Sent: Dienstag, 8. September 2015 18:11 To: odata@lists.oasis-open.org Subject: [odata] Agenda for OData TC meeting on 2015-09-10   Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday September 10, 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=39115   2.         Approve agenda [8:05am PT]   3.         Approve minutes from previous meeting(s) [8:10am PT] a.      Minutes from September 03, 2015 TC meeting: https://www.oasis-open.org/committees/download.php/56430/odata-meeting-103_on-20150903-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.         Process issues [Issues list: https://issues.oasis-open.org/issues/?jql=project%20%3D%20ODATA ] [8:20am PT] a.      Issues for V4.01_WD01 in New or Open state Note: we will only discuss these issues shortly to get an overview of upcoming topics                                   i.     OData Batch Processing Format 1.      ODATA-480 $batch: remove restriction "within the same change set " for Content-ID referencing                                    ii.     OData CSDL 1.      ODATA-557 Allow exponential notation for Edm.Decimal 2.      ODATA-747 Allow IEEE 754 constants [-]INF and NaN also for Edm.Decimal 3.      ODATA-516 Add super type Edm.AnyPath for Edm.PropertyPath, Edm.NavigationPropertyPath, and Edm.AnnotationPath 4.      ODATA-560 Allow arbitrary properties in referential constraints 5.      ODATA-618 Allow using term names in positions that allow type names 6.      ODATA-735 Enhance the CSDL for instance annotations 7.      ODATA-786 Extend definition of edm:Path _expression_ 8.      ODATA-811 Define propagation and (partial) overriding of annotations 9.      ODATA-674 Specify navigation property binding combined with containment 10.   ODATA-817 Add client-side function odata.matchesRegularExpression 11.   ODATA-631 Allow expressing that a term can be applied any collection and is not restricted to entity sets 12.   ODATA-494 Add possibility to "extend" enumeration types with additional values 13.   ODATA-786 Extend definition of edm:Path _expression_                                   iii.     OData JSON Format 1.      ODATA-561 odata.type shouldn't require "#" 2.      ODATA-630 Consider making odata the default namespace for annotations 3.      ODATA-814 Don't need TargetId in a deleted link for a to 0..1 relationship 4.      ODATA-838 Allow inclusion of "untyped JSON" into JSON requests and responses 5.      ODATA-656 Requesting clarity on payload ordering constraints for clients 6.      ODATA-813 Allow no metadata for non-OData clients                                   iv.     OData Protocol 1.      ODATA-541 Allow the If-Match header to reference the ETag that resulted from an earlier operation in a batch request 2.      ODATA-613 Allow POST to entity sets using the delta-response format 3.      ODATA-614 Allow $expand, $select, ... with POST/PATCH/PUT in combination with return=representation to specify the response shape 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 6.      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 7.      ODATA-666 Define Deep Update and Deep Upsert operations 8.      ODATA-809 Define non-message format for final response of async request 9.      ODATA-812 Allow omitting namespaces for unambiguous functions/actions 10.   ODATA-824 Header Content-Transfer-Encoding not used in HTTP 11.   ODATA-827 introduce $compute query option                                    v.     OData URL Conventions 1.      ODATA-556 Add "in" operator as syntactic sugar for a chain of "or" expressions 2.      ODATA-836 Allow applying actions to a filtered collection of entities 3.      ODATA-572 Clarify that eq, ne can be used with complex type 4.      ODATA-820 Allow indexing into collections 5.      ODATA-834 Make type prefix optional for enumeration literals in URLs 6.      ODATA-763 Allowing implicit aliasing of parameters (public comment c201412e00001) 7.      ODATA-799 Define Key-As-Segment URL convention for resource paths 8.      ODATA-664 Consider supporting parameterless function imports with no parens                                   vi.     OData Vocabularies 1.      ODATA-696 Support "interfaces" for casting entities to multiple different types 2.      ODATA-816 Add Capability term for filter _expression_ restrictions 3.      ODATA-571 Add annotation for properties that are (not) part of the default selection if no $select is specified   6.         Next meeting [9:50am PT] a.      Thursday September 17, 2015 during 8-10am PT?   7.         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