Agenda for OData TC meeting 2013.10.01

["Ram Jeyaraman (MS OPEN TECH)" <Ram.Jeyaraman@microsoft.com>]

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on *Tuesday* October 1, 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.

 

*Note: This is a special one-off meeting of the TC per the TC decision on Sept 26, 2013. Please make an effort to attend. At this meeting, we are aiming to wrap up all open issues targeted for Committee Specification Draft 03.*

Thanks.

 

[1] Agenda for 2013.10.01 OData TC meeting

 

1.       Roll call [8:00am PT]

 

2.       Approve agenda [8:05am PT]

 

3.       Approve minutes from previous meeting(s) [8:10am PT]

a.       Minutes from September 26, 2013 TC meeting: https://www.oasis-open.org/committees/download.php/50840/odata-meeting-53_on-20130926-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 by Oct 01, 2013

                                                               i.      None

 

5.       Process issues [Issues list: https://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10103] [8:30am PT]

a.       Issues for v4.0_CS02 in New or Open state

                                                               i.      OData ATOM Format, OData CSDL, OData JSON Format, OData Protocol

1.       ODATA-527: Relative URLs in OData and the ability to put OData services behind an HTTP proxy [Open]

                                                             ii.      OData CSDL

1.       ODATA-513: Special handling of derived types in the dynamic _expression_ edm:Record. Why? [Open]

2.       ODATA-535: Define specialization for terms [Open]

                                                            iii.      OData Protocol

1.       ODATA-523: How do clients construct links from the context url for complex types? [Open] [Close with no action?]

2.       ODATA-490: Clarify Referential Constraints have UpdateRule=Cascade semantics [Open]

                                                           iv.      Vocabularies

1.       ODATA-531: Simplify OptimisticConcurrency in Core vocabulary

2.       ODATA-534: Tag type definition in Core should have default boolean value = true

                                                             v.      Any other issues for v4.0_CS02?

b.      v4.0_CS02 issues in Applied state

                                                               i.      ODATA-537: Ordering of navigationLink and associationLink annotations in JSON

                                                             ii.      ODATA-533: Restrict key property aliases to key properties nested in complex properties

                                                            iii.      ODATA-532: Clarify whether collections can contain null values

                                                           iv.      ODATA-530: Navigable capability term should apply to entityset, not navigationproperty directly

                                                             v.      ODATA-528: $entity should require cast segment in order to apply $select/$expand

                                                           vi.      ODATA-526: Allow specifying support for cross-joins

                                                          vii.      ODATA-525: Remove Org.OData.Atom vocabulary

                                                        viii.      ODATA-524: properties in [propertyList] of context URL may be qualified with type

                                                           ix.      ODATA-522: Clarify that the has operator returns null if either operand is null.

                                                             x.      ODATA-521: Remove typed null literals

                                                           xi.      ODATA-520: Instance annotations should be prefixed with "@"

                                                          xii.      ODATA-519: Define server-driven paging for collection-valued resources

                                                        xiii.      ODATA-518: Use NavProp@<annotation-name> to reference annotations applied to a NavProp

                                                        xiv.      ODATA-517: Allow NavigationPropertyPath and PropertyPath expressions to end in annotations of appropriate type

                                                         xv.      ODATA-515: Section 5.1.1.9 Operator Precedence: operators use wrong capitalization in precedence table

                                                        xvi.      ODATA-514: Example 44: compare Price to a number instead of a string

                                                      xvii.      ODATA-512: 14.5.14: add example for specifying a value for a navigation property in a <Record> _expression_

                                                     xviii.      ODATA-508: Delete leftover "respectively" from 6th paragraph of [JSON] Section 5, Service Document

                                                        xix.      ODATA-507: Editorial; text appears twice in section 11.2.6 of [Protocol]

                                                         xx.      ODATA-505: Remove ReturnType attribute from Action and Function element

                                                        xxi.      ODATA-503: Error in ABNF grammar: Edm prefix required for built-in primitive types

                                                      xxii.      ODATA-502: Fix use of hash (#) for category term attribute in Atom

                                                     xxiii.      ODATA-501: has operator is missing from the operator precedence table

                                                    xxiv.      ODATA-500: Require function/action overloads to differ by ordered set of parameter types

                                                      xxv.      ODATA-498: Error with m:type in Example 31 of Atom

                                                    xxvi.      ODATA-497: Remove type prefix and single quotes for URL literals of types Date, DateTimeOffset, Guid, and TimeOfDay

                                                   xxvii.      ODATA-496: Adapt outdated action/function overload resolution rules in Part 1 to current rules in Part 3

                                                 xxviii.      ODATA-493: Capabilities vocabulary: add term for SearchRestrictions

                                                    xxix.      ODATA-492: Add example for „has" operator to section 5.1.1.1.10

                                                      xxx.      ODATA-491: Language-dependency of key property values

                                                    xxxi.      ODATA-487: Clarify where relative URLs follow the rules in section 4.3 and where they follow different rules

                                                   xxxii.      ODATA-483: Include all section levels in table of contents, provide anchors for all document sections

                                                 xxxiii.      ODATA-481: Annotation/Navigation/Path expressions: allow paths to continue after multi-valued navigation to e.g. drill into complex properties

                                                 xxxiv.      ODATA-478: Clarify format for values of Content-ID header in $batch parts

                                                  xxxv.      ODATA-477: Clarify that dynamic properties can be used in all system query options

                                                 xxxvi.      ODATA-476: Clarify that type-cast segments are required for properties of derived types in system query options

                                               xxxvii.      ODATA-475: Document that the value "%" is used for annotating percentages with Measures.Unit

                                              xxxviii.      ODATA-474: Add example for POST/PUT/PATCH/DELETE on function result

                                                 xxxix.      ODATA-473: Harmonize description of function overload advertisement in Atom and JSON

                                                           xl.      ODATA-472: Explicitly state how dynamic properties are represented if they are not defined on an entity

                                                          xli.      ODATA-471: Property names must also be a valid XML Names (NCName)

                                                        xlii.      ODATA-470: Clarify behavior of /$value requests to properties of type Edm.Binary or Edm.Geo*

                                                       xliii.      ODATA-468: Define explicit concepts in ABNF for referenced sets of rules

                                                      xliv.      ODATA-466: Edm.Binary should be base64-encoded (as with OData V3), not base16-encoded (as per current ABNF)

 

6.       Review revised TC timeline (see [3] below) and immediate next steps [9:50am PT]

a.       Oct 3^rd, 2013: Approve CSD03?

b.      Oct 10-24, 2013: 3^rd public review?

 

7.       Next meeting [9:55am PT]

a.       Thursday October 3, 2013 during 8-10am PT?

 

8.       AOB and wrap up [9:58am 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/download.php/50823/TC%20Timeline%206.htm