OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Agenda for TC meeting 2016-07-07

Here [1] is the agenda for the OData TC (Technical Committee) meeting scheduled on Thursday July 07, 2016 during 6-10am Pacific Time. 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.




[1] Agenda


1)      Roll call [6:00am]

a)      Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41470


2)      Approve agenda [6:05am]


3)      Approve minutes from previous meeting(s) [6:10am]

a)      Minutes from June 23, 2016 TC meeting: https://www.oasis-open.org/committees/document.php?document_id=58414&wg_abbrev=odata


4)      Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am]

a)      Action items due

i)        #0036: Register the OData- headers and preferences with IANA (due July 31, 2016)


5)      V4.01 issues [7:00am]

a)      Issues for V4.01_WD01 in New or Open state

i)        Ripe for resolution

(1)    ODATA-545 Allow applying Capability terms CountRestrictions, TopSupported, SkipSupported etc. to all resources returning collections

(2)    ODATA-948 Versions of vocabularies and their relation with a version of the specification

(3)    ODATA-816 Add Capability term for filter _expression_ restrictions

(4)    ODATA-809 Define non-message format for final response of async request

(5)    ODATA-798 Semantic Key or Alternate Key for entity types

(6)    ODATA-938 In 4.01 decide if we can support invoking actions with no params with no body

(7)    ODATA-935 Allow singletons to be members of an entity set

(8)    ODATA-952 Replace multiple batch capability term with single "BatchSupport" term

(9)    ODATA-541 Allow the If-Match header to reference the ETag that resulted from an earlier operation in a batch request

(10)ODATA-923 $expand for $metadata to include referenced schemas

(11)ODATA-798 Semantic Key or Alternate Key for Entity Types


b)      OData Protocol

(1)    ODATA-919 Specify the result type for each operation based on operator types

(2)    ODATA-942 How should headers applied to a batch affect statements within a batch?


c)       Annotations

(1)    ODATA-571 Add annotation for properties that are (not) part of the default selection if no $select is specified

(2)    ODATA-735 Enhance the CSDL for instance annotations

(3)    ODATA-811 Define propagation and (partial) overriding of annotations

(4)    ODATA-859 Define term, semantics for inserting error information into a (mostly) successful response

(5)    ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)


d)      New Query Capabilities

(1)    ODATA-614 Allow $expand, $select, ... with POST/PATCH/PUT in combination with return=representation to specify the response shape

(2)    ODATA-827 introduce $compute query option

(3)    ODATA-933 Allow using instance annotations in $filter


e)      Set Operations

(1)    ODATA-836 Allow applying actions to a filtered collection of entities


f)       Enumerations

(1)    ODATA-849 Add possibility for enumeration types to "extend" another enumeration type

(2)    ODATA-494 Define inheritance for enumeration types

(3)    ODATA-874 Allow Edm.String as underlying type for enumeration types


g)      OData CSDL

(1)    ODATA-618 Allow using term names in positions that allow type names

(2)    ODATA-929 Nullable facet should default to false for collection types, rather than being unspecified

(3)    ODATA-674 Specify navigation property binding combined with containment *


h)      JSON Format

(1)    ODATA-868 Describe format for In-Stream errors

(2)    ODATA-557 Allow exponential notation for Edm.Decimal


i)        Interfaces

(1)    ODATA-619 Attach action and function signatures to terms, i.e. make a term definition an interface definition


6)      Next meeting [9:50am]

a)      Thursday July 14, 2016 8-10am PT – short meeting

b)      Thursday July 21, 2016 6-10am PT – again a longer meeting


7)      AOB and wrap up [9:55am]


[2] References


[3] Timeline





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]