OData Conference Call #22, Thursday, 24 Jan 2013, 0800 - 0900 PT

Note: For explanations of conventions and other formal aspects common to OData TC meeting minutes which are used in this document please cf. “Formal Aspects of Meeting Minutes”.

Meeting chaired by Ram Jeyaraman

1. Roll call

1.1 Members Present:

    Andrew Eisenberg (IBM)
    Barbara Hartel (SAP AG)
    Colleen Evans (Microsoft)
    Dale Moberg (Axway Software)
    Diane Downie (Citrix Systems)
    Gerald Krause (SAP AG)
    Hubert Heijkers (IBM)
    John Willson (Individual)
    Ken Baclawski (Northeastern University)
    Matthew Borges (SAP AG)
    Michael Pizzo (Microsoft) a.k.a. Mike
    Nuno Linhares (SDL)
    Patrick Durusau (Individual)
    Ralf Handl (SAP AG)
    Ram Jeyaraman (Microsoft)
    Robert Richards (Mashery)
    Stan Mitranic (CA Technologies)
    Stefan Drees (Individual)
    Susan Malaika (IBM)

Quorum achieved. Details cf. normative attendance sheet for this meeting.

2. Approval of Agenda

Agenda approved as published.

3. Approval of Minutes from Previous Meeting(s)

3.1 Approval of Minutes of 2013–01–17 Meeting#21:

Meeting minutes approved with no objections.

4. Review of Action Items (AI) and Progress

List of ongoing actions before the meeting

Retrieval time stamp: 2013-01-24 14:15 +01:00.

AI#0005
“Come up with a first milestine for the temporal extension” [owner: Andrew Eisenberg] is Ongoing (Note: Due 2013–01–31)
AI#0006
“Come up with estimate for first milestone for XML data extension” [owner: Andrew Eisenberg] is Ongoing (Note: Due 2013–01–31)
AI#0007
“Come up with estimate for first milestone for JSON data extension” [owner: Susan Malaika] is Ongoing (Note: Due 2013–01–31)
AI#0018
“Prepare Working Draft 01 (WD01) version of OData Extension for Temporal Data” [owner: Andrew Eisenberg] is Ongoing
AI#0019
“Prepare Working Draft 01 (WD01) version of OData Extension for XML Data” [owner: Andrew Eisenberg] is Ongoing
AI#0020
“Prepare Working Draft 01 (WD01) version of OData Extension for JSON Data” [owner: Susan Malaika] is Ongoing

4.1 Action items due by 2013–01–24 (end of day)

None.

4.2 Action items NOT due by 2013–01–24 but MAY be ready for closure

None.

5 Review of Issues List (IL) and Progress

5.1 Issues in Applied state

5.1.1 OData URL Conventions

5.1.1.1 ODATA–183
ODATA–183
“The same navigation property should not be specified in multiple $expands” [component: OData URL Conventions] is Applied.

Ralf:

I move to close ODATA–183 as applied. Stefan seconds.

No further discussion. No objections. The motion passes.

ODATA–183
“The same navigation property should not be specified in multiple $expands” [component: OData URL Conventions] is Closed with no objections.
5.1.1.2 ODATA–84
ODATA–84
“Define which system query options should be supported per URL pattern” [component: OData URL Conventions] is Applied.

Ralf:

I move to close ODATA–84 as applied. Andrew seconds.

No further discussion. No objections. The motion passes.

ODATA–84
“Define which system query options should be supported per URL pattern” [component: OData URL Conventions] is Closed with no objections.
5.1.1.3 ODATA–71
ODATA–71
“Improve addition and subtraction Arithmetic Operators to handle time-related data types” [component: OData URL Conventions] is Applied.

Ralf:

I move to close ODATA–71 as applied. Andrew seconds.

No further discussion. No objections. The motion passes.

ODATA–71
“Improve addition and subtraction Arithmetic Operators to handle time-related data types” [component: OData URL Conventions] is Closed with no objections.
5.1.1.4 ODATA–13
ODATA–13
“A function that returns the current date and time is needed” [component: OData URL Conventions] is Applied.

Ralf:

I move to close ODATA–13 as applied. Andrew seconds.

No further discussion. No objections. The motion passes.

ODATA–13
“A function that returns the current date and time is needed” [component: OData URL Conventions] is Closed with no objections.

5.1.2 OData ATOM Format

Discussion:

5.1.2.1 ODATA–107
ODATA–107
“Should OData support a ‘clock time’ (xs:time) datatype?” [component: OData ABNF Construction Rules] is Proposed.

Discussion:

Mike:

I move we accept the proposed resolution for ODATA–107 as follows: 1) We define a new Edm.Duration type which is formatted as xs:dayTimeDuration (Ralf already applied this by adding Edm.DayTimeDuration; we would just rename this to the (simpler) “Edm.Duration”). 2) We remove Edm.Time from the OASIS specification and mark it in the URL grammar as reserved for compatibility with previous implementations (existing implementations can use it as a synonym for the new Edm.Duration). 3) We add a new Edm.TimeOfDay which is xs:time without explicit time zone offset and without the 24:00:00 value. Hubert seconds.

Discussion:

No further discussion. No objections. The motion passes.

ODATA–107
“Should OData support a ‘clock time’ (xs:time) datatype?” [component: OData ABNF Construction Rules] is Resolved as noted in the motion with no objections.
5.1.2.2 ODATA–136
ODATA–136
“Correct definition of Edm.Time in ATOM” [component: OData ATOM Format] is Applied.

Mike:

I move we close ODATA–136 as it is now superceded by the approved ODATA–107. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–136
“Correct definition of Edm.Time in ATOM” [component: OData ATOM Format] is Closed as noted in the motion with no objections.

5.1.3 OData CSDL, OData URL Conventions

5.1.3.1 ODATA–14
ODATA–14
“add Edm.Date to the OData primitive data types” [components: OData CSDL, OData URL Conventions] is Applied.

Ralf:

I move to close ODATA–14 as applied. Andrew seconds.

No further discussion. No objections. The motion passes.

ODATA–14
“add Edm.Date to the OData primitive data types” [components: OData CSDL, OData URL Conventions] is Closed with no objections.
5.1.3.2 ODATA–11
ODATA–11
“date/time values without explicit time zones need further investigation” [components: OData CSDL, OData URL Conventions] is Applied.

Discussion:

ODATA–11
“date/time values without explicit time zones need further investigation” [components: OData CSDL, OData URL Conventions] is Resolved with no objections.

5.2 Editorial issues

5.2.1 OData Delta Queries

Discussion:

Stefan:

I move to open the issues ODATA–206, ODATA–207, ODATA–208, ODATA–209, ODATA–210 and ODATA–211 as group and at once resolve the proposed resolutions as applied, thus promoting the status to Closed for every issue in that group. Mike seconds.

No further discussion. No objections. The motion passes.

5.2.1.1 ODATA–206
ODATA–206
“Rephrasing of section Delta Links in ODQP proposal page 1/2” [component: OData Delta Queries] is New.

Note:

Issue state has been progressed by grouping motion (cf. section [5.2.1])

ODATA–206
“Rephrasing of section Delta Links in ODQP proposal page 1/2” [component: OData Delta Queries] is Closed as noted in the motion in section 5.2.1 with no objections.
5.2.1.2 ODATA–207
ODATA–207
“Rephrasing of section Requesting Delta Links in ODQP proposal page 2” [component: OData Delta Queries] is New.

Note:

Issue state has been progressed by grouping motion (cf. section [5.2.1])

ODATA–207
“Rephrasing of section Requesting Delta Links in ODQP proposal page 2” [component: OData Delta Queries] is Closed as noted in the motion in section 5.2.1 with no objections.
5.2.1.3 ODATA–208
ODATA–208
“Enhancement of ‘flat heterogeneous’ structure definition and reference thereof in section Delta Responses inside ODQP proposal pages 3/4 (and later)” [component: OData Delta Queries] is New.

Note:

Issue state has been progressed by grouping motion (cf. section [5.2.1])

ODATA–208
“Enhancement of ‘flat heterogeneous’ structure definition and reference thereof in section Delta Responses inside ODQP proposal pages 3/4 (and later)” [component: OData Delta Queries] is Closed as noted in the motion in section 5.2.1 with no objections.
5.2.1.4 ODATA–209
ODATA–209
“Replace the term store by service and reduce number of triggerpoints in diagrams in section Client Interaction inside ODQP proposal pages 5/6” [component: OData Delta Queries] is New.

Note:

Issue state has been progressed by grouping motion (cf. section [5.2.1])

ODATA–209
“Replace the term store by service and reduce number of triggerpoints in diagrams in section Client Interaction inside ODQP proposal pages 5/6” [component: OData Delta Queries] is Closed as noted in the motion in section 5.2.1 with no objections.
5.2.1.5 ODATA–210
ODATA–210
“Declare OData object/concept name for tombstone before its usage in Result Maintenance and ATOM format describing sections inside ODQP proposal pages 6 and later” [component: OData Delta Queries] is New.

Note:

Issue state has been progressed by grouping motion (cf. section [5.2.1])

ODATA–210
“Declare OData object/concept name for tombstone before its usage in Result Maintenance and ATOM format describing sections inside ODQP proposal pages 6 and later” [component: OData Delta Queries] is Closed as noted in the motion in section 5.2.1 with no objections.
5.2.1.6 ODATA–211
ODATA–211
“Correct the sample inside section ‘JSON DeltaQuery Result Example’ inside ODQP proposal pages 9/10” [component: OData Delta Queries] is New.

Note:

Issue state has been progressed by grouping motion (cf. section [5.2.1])

ODATA–211
“Correct the sample inside section ‘JSON DeltaQuery Result Example’ inside ODQP proposal pages 9/10” [component: OData Delta Queries] is Closed as noted in the motion in section 5.2.1 with no objections.

5.3 Issues in Proposed state (carried over from Jan 10, 2013 TC meeting)

5.3.1 OData CSDL

5.3.1.1 ODATA–194
ODATA–194
“Inside section 4.1.1 The Version Attribute, the version defined by this spec should be 4.0 and not 1.0 for the EDMX wrapper” [component: OData CSDL] is New.

Mike:

I move we resolve ODATA–194 as proposed. Ralf seconds.

No further discussion. No objections. The motion passes.

ODATA–194
“Inside section 4.1.1 The Version Attribute, the version defined by this spec should be 4.0 and not 1.0 for the EDMX wrapper” [component: OData CSDL] is Resolved with no objections.

5.3.2 OData ABNF Construction Rules

5.3.2.1 ODATA–96
ODATA–96
“Need to define semantics, serialization format, etc. for Enums” [component: OData ABNF Construction Rules] is New.

Discussion:

Mike:

I move we accept the proposal for ODATA–96 as described. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–96
“Need to define semantics, serialization format, etc. for Enums” [component: OData ABNF Construction Rules] is Resolved with no objections.

5.3.3 OData URL Conventions

5.3.3.1 ODATA–142
ODATA–142
“Define URL functions geo.distance, geo.length, geo.intersects, and gettotaloffsetminutes” [component: OData URL Conventions] is New.

Ralf:

I move to resolve ODATA–142 as proposed. Mike seconds.

Discussion of the motion:

No further discussion. No objections. The motion passes.

ODATA–142
“Define URL functions geo.distance, geo.length, geo.intersects, and gettotaloffsetminutes” [component: OData URL Conventions] is Resolved with no objections.
5.3.3.2 ODATA–203
ODATA–203
“Specify Operator Precedence more clearly” [component: OData URL Conventions] is New.

Ralf:

I move ODATA–203 as proposed. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–203
“Specify Operator Precedence more clearly” [component: OData URL Conventions] is Resolved with no objections.

Note:

Time slot for issue processing gone. Skip all remaining agenda sub items of 5.

6 Next Meeting

6.1 2013-JAN–30 and 2013-JAN–31 Third F2F meeting 09am - 06pm CET

Context:

We will be meeting F2F during Jan 30–31, 2013 in Zürich, Switzerland. Details are available at https://www.oasis-open.org/committees/event.php?event_id=34020 for the first and http://www.oasis-open.org/committees/event.php?event_id=34021 for the second day.

Discussion:

7 AOB

None.

Meeting adjourned on 0900 PT.

Appendices

Timeline Reference

Draft timeline for OData core Work Products:

Draft timeline for extension Work Products: