OData meeting #25, Thursday, 14 Feb 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)
    Dale Moberg (Axway Software)
    Erik de Voogd (SDL)
    Gerald Krause (SAP AG)
    Hubert Heijkers (IBM)
    Jeffrey Turpin (Axway Software)
    John Willson (Individual)
    Ken Baclawski (Northeastern University)
    Martin Zurmuehl (SAP AG)
    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)
    Ted Jones (Red Hat)

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–02–07 Meeting#24

Meeting minutes approved with no objections.

4 Review of Action Items (AI) and Progress

Context:

See the “List of Open Action Items Before the Meeting” section in the appendix.

4.1 Action items due by 2013–02–14 (end of day)

4.1.1 AI#0028

AI#0028
“Introduce fix target versions 4.0, minor and next major into JIRA” [owner: Ram Jeyaraman] is Ongoing (Note: Due 2013–02–14)

Discussion:

Stefan:

I move to call the OASIS OData Work Products as version 4.0 (instead of version 1.0) and call the next major revision as version 5.0 and next minor revision as version 4.1 . Nuno seconds.

No further discussion. No objections. The motion passes.

Note:

AI#0028
“Introduce fix target versions 4.0, minor and next major into JIRA” [owner: Ram Jeyaraman] is Ongoing (Note: Due 2013–02–21)

4.2 Action items NOT due by 2013–02–14 (end of day) but MAY be ready for closure

None.

5 Review of Issues List (IL) and Progress

Notes:

Discussion:

5.1 Issues in Applied state

All accept to follow the grouping and sequence for processing of applied issues that Mike suggested in his mail “RE: Agenda for OData TC meeting 2013.02.14”.

5.1.1 Already reviewed and approved for all components but OData Protocol

Discussion:

John:

I move to close the issues ODATA–11, 13, 14, 24, 32, 38, 73, 107, 114 and 132 as applied. Stefan seconds.

No further discussion. No objections. The motion passes.

5.1.1.1 ODATA–107
ODATA–107
“Should OData support a ‘clock time’ (xs:time) datatype?” [components: CSDL, ABNF Construction Rules, URL Conventions] is Applied.

Note:

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

ODATA–107
“Should OData support a ‘clock time’ (xs:time) datatype?” [components: CSDL, ABNF Construction Rules, URL Conventions] is Closed with no objections.

5.1.1.2 ODATA–14

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

Note:

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

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

5.1.1.3 ODATA–13

ODATA–13
“A function that returns the current date and time is needed” [component: URL Conventions] is Applied.

Note:

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

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

5.1.1.4 ODATA–11

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

Note:

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

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

5.1.1.5 ODATA–73

ODATA–73
“Retrieve the count of related entities together with the base entity” [component: URL Conventions] is Applied.

Note:

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

ODATA–73
“Retrieve the count of related entities together with the base entity” [component: URL Conventions] is Closed with no objections.

5.1.1.6 ODATA–38

ODATA–38
“Recursive $expand and $select” [component: URL Conventions] is Applied.

Note:

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

ODATA–38
“Recursive $expand and $select” [component: URL Conventions] is Closed with no objections.

5.1.1.7 ODATA–32

ODATA–32
“Allow filtering of expanded to-many navigation properties” [component: URL Conventions] is Applied.

Note:

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

ODATA–32
“Allow filtering of expanded to-many navigation properties” [component: URL Conventions] is Closed with no objections.

5.1.1.8 ODATA–132

ODATA–132
“Support /$count in $filter and $orderby” [components: URL Conventions, ABNF Construction Rules] is Applied.

Note:

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

ODATA–132
“Support /$count in $filter and $orderby” [components: URL Conventions, ABNF Construction Rules] is Closed with no objections.

5.1.1.9 ODATA–114

ODATA–114
“Allow /$count path suffix also for collection properties” [components: URL Conventions, ABNF Construction Rules] is Applied.

Note:

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

ODATA–114
“Allow /$count path suffix also for collection properties” [components: URL Conventions, ABNF Construction Rules] is Closed with no objections.

5.1.1.10 ODATA–24

ODATA–24
“Simplify how Relationships are expressed in CSDL” [component: CSDL] is Applied.

Note:

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

ODATA–24
“Simplify how Relationships are expressed in CSDL” [component: CSDL] is Closed with no objections.

5.1.2 Model References Changes

Discussion:

Ralf:

I move to close ODATA–180, 181, 182 and 193 as applied. Mike seconds.

No further discussion. No objections. The motion passes.

5.1.2.1 ODATA–193

ODATA–193
“Allow function imports to return entities from a different service” [component: CSDL] is Applied.

Note:

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

ODATA–193
“Allow function imports to return entities from a different service” [component: CSDL] is Closed with no objections.

5.1.2.2 ODATA–182

ODATA–182
“Define the term ‘model’” [component: CSDL] is Applied.

Note:

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

ODATA–182
“Define the term ‘model’” [component: CSDL] is Closed with no objections.

5.1.2.3 ODATA–181

ODATA–181
“Referencing/reusing a model element from a different schema does not require to ‘include’ this schema via a Using element” [component: CSDL] is Applied.

Note:

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

ODATA–181
“Referencing/reusing a model element from a different schema does not require to ‘include’ this schema via a Using element” [component: CSDL] is Closed with no objections.

5.1.2.4 ODATA–180

ODATA–180
“Remove Extends attribute from EntityContainer element” [component: CSDL] is Applied.

Note:

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

ODATA–180
“Remove Extends attribute from EntityContainer element” [component: CSDL] is Closed with no objections.

5.1.3 Annotations

Discussion:

Mike:

I move we approve the applied resolutions to ODATA–12, ODATA–108, ODATA–109, ODATA–217, ODATA–226, ODATA–227, ODATA–229, ODATA–231 and ODATA–241. Ralf seconds.

No further discussion. No objections. The motion passes.

5.1.3.1 ODATA–226

ODATA–226
“Clarify that the root of the Path attribute of a element is rooted at the containing entity ” [component: CSDL] is Applied.

Note:

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

ODATA–226
“Clarify that the root of the Path attribute of a element is rooted at the containing entity ” [component: CSDL] is Closed with no objections.

5.1.3.2 ODATA–109

ODATA–109
“Define rules for specifying annotations within annotations” [component: CSDL] is Applied.

Note:

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

ODATA–109
“Define rules for specifying annotations within annotations” [component: CSDL] is Closed with no objections.

5.1.3.3 ODATA–108

ODATA–108
“Define rules for the target of an annotation that supports implicit casting of relationships” [component: CSDL] is Applied.

Note:

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

ODATA–108
“Define rules for the target of an annotation that supports implicit casting of relationships” [component: CSDL] is Closed with no objections.

5.1.3.4 ODATA–12

ODATA–12
“create a data type for property names” [component: CSDL] is Applied.

Note:

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

ODATA–12
“create a data type for property names” [component: CSDL] is Closed with no objections.

5.1.3.5 ODATA–231

ODATA–231
“Define how to specify enumeration values in annotations” [component: CSDL] is Applied.

Note:

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

ODATA–231
“Define how to specify enumeration values in annotations” [component: CSDL] is Closed with no objections.

5.1.3.6 ODATA–229

ODATA–229
“Allow annotations to target all model elements” [component: CSDL] is Applied.

Note:

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

ODATA–229
“Allow annotations to target all model elements” [component: CSDL] is Closed with no objections.

5.1.3.7 ODATA–227

ODATA–227
“Support of symbolic names in annotations” [component: CSDL] is Applied.

Note:

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

ODATA–227
“Support of symbolic names in annotations” [component: CSDL] is Closed with no objections.

5.1.3.8 ODATA–217

ODATA–217
“property facets in ValueTerm element” [component: CSDL] is Applied.

Note:

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

ODATA–217
“property facets in ValueTerm element” [component: CSDL] is Closed with no objections.

5.1.3.9 ODATA–241

ODATA–241
“Consistently require annotations to be placed at the end of the annotated CSDL element” [component: CSDL] is Applied.

Note:

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

ODATA–241
“Consistently require annotations to be placed at the end of the annotated CSDL element” [component: CSDL] is Closed with no objections.

5.1.4 Application of relatively straight-forward changes

Discussion:

Stefan:

I move we close the issues ODATA–41, ODATA–158, ODATA–169, ODATA–187, ODATA–197, ODATA–213, ODATA–216, ODATA–218, ODATA–235 and ODATA–238 as applied. Ralf seconds.

No further discussion. No objections. The motion passes.

Note:

5.1.4.1 ODATA–169

ODATA–169
“Representation of named entities in the service document” [components: JSON Format, ATOM Format] is Applied.

Note:

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

ODATA–169
“Representation of named entities in the service document” [components: JSON Format, ATOM Format] is Closed with no objections.

5.1.4.2 ODATA–158

ODATA–158
“OData ATOM format should require element” [component: ATOM Format] is Applied.

Note:

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

ODATA–158
“OData ATOM format should require element” [component: ATOM Format] is Closed with no objections.

5.1.4.3 ODATA–238

ODATA–238
“Restrict values of the Qualifier attribute to QualifiedName values” [component: CSDL] is Applied.

Note:

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

ODATA–238
“Restrict values of the Qualifier attribute to QualifiedName values” [component: CSDL] is Closed with no objections.

5.1.4.4 ODATA–235

ODATA–235
“Limit primitive types allowed as key parts to the ‘sufficiently discrete’ types” [component: CSDL] is Applied.

Note:

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

ODATA–235
“Limit primitive types allowed as key parts to the ‘sufficiently discrete’ types” [component: CSDL] is Closed with no objections.

5.1.4.5 ODATA–216

ODATA–216
“Allow edm:Documentation element in edm:TypeDefinition and edm:Annotations element” [component: CSDL] is Applied.

Note:

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

ODATA–216
“Allow edm:Documentation element in edm:TypeDefinition and edm:Annotations element” [component: CSDL] is Closed with no objections.

5.1.4.6 ODATA–213

ODATA–213
“Allow all dynamic expressions of the appropriate type within edm:Collection expressions” [component: CSDL] is Applied.

Note:

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

ODATA–213
“Allow all dynamic expressions of the appropriate type within edm:Collection expressions” [component: CSDL] is Closed with no objections.

5.1.4.7 ODATA–197

ODATA–197
“Define standard functions for edm:Apply element” [component: CSDL] is Applied.

Note:

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

ODATA–197
“Define standard functions for edm:Apply element” [component: CSDL] is Closed with no objections.

5.1.4.8 ODATA–218

ODATA–218
“Remove doubled last paragraph in section 8.5.2 The Preference-Applied Header” [component: Protocol] is Applied.

Note:

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

ODATA–218
“Remove doubled last paragraph in section 8.5.2 The Preference-Applied Header” [component: Protocol] is Closed with no objections.

5.1.4.9 ODATA–187

ODATA–187
“Need to remove references to associations and associationsets from protocol doc” [component: Protocol] is Applied.

Note:

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

ODATA–187
“Need to remove references to associations and associationsets from protocol doc” [component: Protocol] is Closed with no objections.

5.1.4.10 ODATA–110

ODATA–110
“Track Prefer Header in Http” [component: Protocol] is Applied.

Note:

Issue state has not been progressed as noted in discussion before grouping motion (cf. section [5.1.4])

5.1.4.11 ODATA–41

ODATA–41
“Specify which URL formats are acceptable within $batch, and which to prefer” [component: Protocol] is Applied.

Note:

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

ODATA–41
“Specify which URL formats are acceptable within $batch, and which to prefer” [component: Protocol] is Closed with no objections.

5.1.4.12 ODATA–225

ODATA–225
“Define Functions in Schema; reference in Container using FunctionImport.” [components: CSDL, ABNF Construction Rules] is Applied.

Note:

Issue state has not been progressed as noted in discussion before grouping motion (cf. section [5.1.4])

5.1.5 Applied changes with more significant impact on the documents

5.1.5.1 ODATA–205

ODATA–205
“Merge TypeAnnotation and ValueAnnotation into Annotation” [component: CSDL] is Applied.

Mike:

I move we close issue ODATA–205 as applied. Ralf seconds.

No further discussion. No objections. The motion passes.

ODATA–205
“Merge TypeAnnotation and ValueAnnotation into Annotation” [component: CSDL] is Closed with no objections.

5.1.5.2 ODATA–25

ODATA–25
“Support Obtaining Changes (Deltas) from a result.” [component: Protocol] is Applied.

Discussion:

Ralf:

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

No further discussion. No objections. The motion passes.

ODATA–25
“Support Obtaining Changes (Deltas) from a result.” [component: Protocol] is Closed with no objections.

5.1.5.3 ODATA–199

ODATA–199
“$expand should be allowed to return only ids for already seen objects” [components: JSON Format, ATOM Format] is Applied.

Ralf:

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

No further discussion. No objections. The motion passes.

ODATA–199
“$expand should be allowed to return only ids for already seen objects” [components: JSON Format, ATOM Format] is Closed with no objections.

5.1.5.4 ODATA–16

ODATA–16
“Define an Edm.AnyType to allow functions to apply to entity sets of any entity type” [component: CSDL] is Applied.

Ralf:

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

No further discussion. No objections. The motion passes.

ODATA–16
“Define an Edm.AnyType to allow functions to apply to entity sets of any entity type” [component: CSDL] is Closed with no objections.

5.1.5.5 ODATA–119

ODATA–119
“Allow definition of ‘simple’ types that fix values for facet attributes of primitive types” [component: CSDL] is Applied.

Ralf:

I move to close ODATA–119 as applied. Mike seconds.

No further discussion. No objections. The motion passes.

ODATA–119
“Allow definition of ‘simple’ types that fix values for facet attributes of primitive types” [component: CSDL] is Closed with no objections.

5.2 Issues in Proposed state (carried over from Feb 7, 2013 TC meeting)

5.2.1 OData CSDL

5.2.1.1 ODATA–202

ODATA–202
“Custom Mapping to Atom Elements not defined” [component: ATOM Format] is New.

Mike:

I move we resolve ODATA–202 by removing the dangling reference to Custom mapping to ATOM, as proposed. Stefan seconds.

No further discussion. No objections. The motion passes.

ODATA–202
“Custom Mapping to Atom Elements not defined” [component: ATOM Format] is Proposed as noted in the motion with no objections.

5.2.2 OData Atom, OData JSON

5.2.2.1 ODATA–212

ODATA–212
“Define request body format for Actions in Atom and JSON format specifications” [components: JSON Format, ATOM Format, Protocol] is New.

Ralf:

I move to resolve ODATA–212 as proposed. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–212
“Define request body format for Actions in Atom and JSON format specifications” [components: JSON Format, ATOM Format, Protocol] is Proposed with no objections.

5.2.2.2 ODATA–221

ODATA–221
“Flatten the message element in the JSON Error Represention (Section 4.18 Representing Errors in a Response)” [component: JSON Format] is New.

Discussion:

Stefan:

I move to accept ODATA–221 as proposed including removal of any special references to xml:lang inside the OData ATOM work product. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–221
“Flatten the message element in the JSON Error Represention (Section 4.18 Representing Errors in a Response)” [component: JSON Format] is Proposed as noted in the motion with no objections.
5.2.2.2.1 End of Issue Processing

Note:

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

6 Next Face to Face Meeting

6.1 Determine location and venue based on poll results

6.1.1 Geographic location preference

Context:

Ballot “Choose a geographic location for the 4th TC F2F meeting”.

Discussion:

6.1.2 Date preferences

Context:

Ballot “Select dates for the 4th F2F meeting”.

Discussion:

7 Next Meeting

7.1 Next weekly TC meeting will be 2013–02–21 during 8–9am PT.

Agreed.

7.2 Meeting duration

Shall the TC meetings be extended by another half hour (to facilitate making progress on issues)?

Discussion:

8 AOB

None.

Meeting adjourned on 0900 PT

Appendices

List of Open Action Items Before the Meeting

Retrieval time stamp: 2013-02-14 14:09 +01:00.

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
AI#0028
“Introduce fix target versions 4.0, minor and next major into JIRA” [owner: Ram Jeyaraman] is Ongoing (Note: Due 2013–02–14)

Note: The actual action item processing is documented in section 4 and subsections thereof.

Index of Issues Processed During the Meeting

Note: The actual issue processing is documented in sections 5. The below index has two main parts: First come the public comments (if any), second the JIRA issues. Each list of issues is sorted by ascending issue number. Noted are the ID, the summary and the reference to the relevant subsection where the issue progression has been documented:

Public Comments:

None.

JIRA Issues:

Timeline Reference

Note: Please cf. the current revision of the TC timeline.