OData meeting #35, Thursday, 02 MAY 2013, 0800 - 1000 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 Barbara Hartel and Ram Jeyaraman

Acting Chair: Barbara Hartel

1 Roll call

1.1 Members Present:

    Anila Kumar GVN (CA Technologies)
    Barbara Hartel (SAP AG)
    Dale Moberg (Axway Software)
    Diane Downie (Citrix Systems)
    Edmond Bourne (BlackBerry)
    Gerald Krause (SAP AG)
    Hubert Heijkers (IBM)
    John Willson (Individual)
    Martin Zurmuehl (SAP AG)
    Matthew Borges (SAP AG)
    Michael Pizzo (Microsoft) a.k.a. Mike
    Patrick Durusau (Individual)
    Ralf Handl (SAP AG)
    Ram Jeyaraman (Microsoft)
    Robert Richards (Mashery)
    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–04–25/26 Meeting#34 F2F

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–05–02 (end of day)

None.

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

None.

5 Review of Issues List (IL) and Progress

Notes:

5.1 Issues in Applied state, editors will give information only for issues where they had problems with applying

Discussion:

Stefan:

I move to close ODATA–34, ODATA–48, ODATA–144, ODATA–192, ODATA–223, ODATA–224, ODATA–239, ODATA–240, ODATA–286, ODATA–298, ODATA–323, ODATA–326, ODATA–330, ODATA–331, ODATA–332, ODATA–334, ODATA–335, ODATA–336, ODATA–337, ODATA–339, ODATA–340, ODATA–341, ODATA–342, ODATA–343, ODATA–345, ODATA–347, ODATA–350, ODATA–352, ODATA–353, ODATA–354, ODATA–355, ODATA–356, ODATA–357, ODATA–358, ODATA–359, ODATA–360, ODATA–361, and ODATA–363 as applied. Martin seconds.

No further discussion. No objections. The motion passes.

5.1.1 ODATA–34

ODATA–34:
“Control verbosity of $metadata response: include annotations or documentation” [component: OData Protocol] is Applied.

Note:

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

ODATA–34:
“Control verbosity of $metadata response: include annotations or documentation” [component: OData Protocol] is Closed with no objections.

5.1.2 ODATA–48

ODATA–48:
“Consistent typographical conventions for OData specifications” [components: OData Extension for Temporal Data, OData Extension for JSON Data, OData Extension for XML Data] is Applied.

Note:

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

ODATA–48:
“Consistent typographical conventions for OData specifications” [components: OData Extension for Temporal Data, OData Extension for JSON Data, OData Extension for XML Data] is Closed with no objections.

5.1.3 ODATA–144

ODATA–144:
“‘Scoping’ syntax for $aggregate” [component: OData Extension for Data Aggregation] is Applied.

Note:

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

ODATA–144:
“‘Scoping’ syntax for $aggregate” [component: OData Extension for Data Aggregation] is Closed with no objections.

5.1.4 ODATA–192

ODATA–192:
“Define vocabulary term as a replacement for StoreGeneratedPattern attribute” [component: Vocabularies] is Applied.

Note:

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

ODATA–192:
“Define vocabulary term as a replacement for StoreGeneratedPattern attribute” [component: Vocabularies] is Closed with no objections.

5.1.5 ODATA–223

ODATA–223:
“Specify Service behavior for not implemented functionality” [components: OData Batch Processing Format, OData ATOM Format, OData Extension for Data Aggregation, OData CSDL, OData Extension for Temporal Data, OData Extension for JSON Data, OData JSON Format, OData Extension for XML Data, OData URL Conventions, OData Protocol] is Applied.

Note:

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

ODATA–223:
“Specify Service behavior for not implemented functionality” [components: OData Batch Processing Format, OData ATOM Format, OData Extension for Data Aggregation, OData CSDL, OData Extension for Temporal Data, OData Extension for JSON Data, OData JSON Format, OData Extension for XML Data, OData URL Conventions, OData Protocol] is Closed with no objections.

5.1.6 ODATA–224

ODATA–224:
“Fill out Capabilities sections of an OData Service” [components: OData URL Conventions, OData ATOM Format, OData ABNF Construction Rules, OData CSDL, OData Batch Processing Format, OData Extension for JSON Data, OData Extension for Data Aggregation, OData Extension for XML Data, OData Extension for Temporal Data, OData Protocol, OData JSON Format] is Applied.

Note:

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

ODATA–224:
“Fill out Capabilities sections of an OData Service” [components: OData URL Conventions, OData ATOM Format, OData ABNF Construction Rules, OData CSDL, OData Batch Processing Format, OData Extension for JSON Data, OData Extension for Data Aggregation, OData Extension for XML Data, OData Extension for Temporal Data, OData Protocol, OData JSON Format] is Closed with no objections.

5.1.7 ODATA–239

ODATA–239:
“Allowing expressions to be passed as parameters to (super) functions” [components: OData URL Conventions, OData ABNF Construction Rules] is Applied.

Note:

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

ODATA–239:
“Allowing expressions to be passed as parameters to (super) functions” [components: OData URL Conventions, OData ABNF Construction Rules] is Closed with no objections.

5.1.8 ODATA–240

ODATA–240:
“Better describe, and possible extend, expected behavior of dealing with async $batch requests” [component: OData Protocol] is Applied.

Note:

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

ODATA–240:
“Better describe, and possible extend, expected behavior of dealing with async $batch requests” [component: OData Protocol] is Closed with no objections.

5.1.9 ODATA–286

ODATA–286:
“Need clarity about JSON encoding of Single and Double (and the applicability or not of ABNF rules) particularly for NaN, INF and -INF” [component: OData JSON Format] is Applied.

Note:

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

ODATA–286:
“Need clarity about JSON encoding of Single and Double (and the applicability or not of ABNF rules) particularly for NaN, INF and -INF” [component: OData JSON Format] is Closed with no objections.

5.1.10 ODATA–298

ODATA–298:
“Clarify Requesting Changes to entity sets that include Stream properties” [component: OData Protocol] is Applied.

Note:

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

ODATA–298:
“Clarify Requesting Changes to entity sets that include Stream properties” [component: OData Protocol] is Closed with no objections.

5.1.11 ODATA–323

ODATA–323:
“InlineCount should just be boolean” [components: OData Protocol, OData ABNF Construction Rules] is Applied.

Note:

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

ODATA–323:
“InlineCount should just be boolean” [components: OData Protocol, OData ABNF Construction Rules] is Closed with no objections.

5.1.12 ODATA–326

ODATA–326:
“include-annotations should allow inclusion (or exclusion) of specific terms” [component: OData Protocol] is Applied.

Note:

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

ODATA–326:
“include-annotations should allow inclusion (or exclusion) of specific terms” [component: OData Protocol] is Closed with no objections.

5.1.13 ODATA–330

ODATA–330:
“Define whether null values come first or last with $orderby asc” [component: OData Protocol] is Applied.

Note:

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

ODATA–330:
“Define whether null values come first or last with $orderby asc” [component: OData Protocol] is Closed with no objections.

5.1.14 ODATA–331

ODATA–331:
“Ensure that high level grouping expressions like eg. ‘create operations’ are easily mapped to real actions (HTTP methods, OData expectations)” [component: OData Protocol] is Applied.

Note:

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

ODATA–331:
“Ensure that high level grouping expressions like eg. ‘create operations’ are easily mapped to real actions (HTTP methods, OData expectations)” [component: OData Protocol] is Closed with no objections.

5.1.15 ODATA–332

ODATA–332:
“Ensure comparability and emphasize differences in directly grokable way for all formats (currently only ATOM and JSON)” [components: OData Extension for JSON Data, OData ATOM Format] is Applied.

Note:

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

ODATA–332:
“Ensure comparability and emphasize differences in directly grokable way for all formats (currently only ATOM and JSON)” [components: OData Extension for JSON Data, OData ATOM Format] is Closed with no objections.

5.1.16 ODATA–334

ODATA–334:
“Integrate conformance concept with careful consideration of versioning semantics (into protocol work product)” [component: OData Protocol] is Applied.

Note:

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

ODATA–334:
“Integrate conformance concept with careful consideration of versioning semantics (into protocol work product)” [component: OData Protocol] is Closed with no objections.

5.1.17 ODATA–335

ODATA–335:
“Review results for OData ATOM Format Version 4.0” [component: OData ATOM Format] is Applied.

Note:

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

ODATA–335:
“Review results for OData ATOM Format Version 4.0” [component: OData ATOM Format] is Closed with no objections.

5.1.18 ODATA–336

ODATA–336:
“Be more generous on accepting values for the $format query option” [components: OData ATOM Format, OData ABNF Construction Rules, OData JSON Format] is Applied.

Note:

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

ODATA–336:
“Be more generous on accepting values for the $format query option” [components: OData ATOM Format, OData ABNF Construction Rules, OData JSON Format] is Closed with no objections.

5.1.19 ODATA–337

ODATA–337:
“Review results for OData JSON Format Version 4.0” [component: OData JSON Format] is Applied.

Note:

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

ODATA–337:
“Review results for OData JSON Format Version 4.0” [component: OData JSON Format] is Closed with no objections.

5.1.20 ODATA–339

ODATA–339:
“$inlinecount and $count, do we need both? Could we use $count in select clause as well?” [components: OData Protocol, OData ABNF Construction Rules] is Applied.

Note:

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

ODATA–339:
“$inlinecount and $count, do we need both? Could we use $count in select clause as well?” [components: OData Protocol, OData ABNF Construction Rules] is Closed with no objections.

5.1.21 ODATA–340

ODATA–340:
“How to retrieve both the entity references as well as the count of a collection referenced by a navigation property?” [component: OData Protocol] is Applied.

Note:

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

ODATA–340:
“How to retrieve both the entity references as well as the count of a collection referenced by a navigation property?” [component: OData Protocol] is Closed with no objections.

5.1.22 ODATA–341

ODATA–341:
“Can we get rid of the optional trailing ‘L’/’l’ for int64 numbers” [component: OData ABNF Construction Rules] is Applied.

Note:

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

ODATA–341:
“Can we get rid of the optional trailing ‘L’/’l’ for int64 numbers” [component: OData ABNF Construction Rules] is Closed with no objections.

5.1.23 ODATA–342

ODATA–342:
“Can we relax the requirement of int64 numbers being represented as strings in the JSON Format for integer numbers that don’t lose precision in ECMAScript when represented as numbers?” [component: OData JSON Format] is Applied.

Note:

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

ODATA–342:
“Can we relax the requirement of int64 numbers being represented as strings in the JSON Format for integer numbers that don’t lose precision in ECMAScript when represented as numbers?” [component: OData JSON Format] is Closed with no objections.

5.1.24 ODATA–343

ODATA–343:
“Ensure consistent placement and delegation of descritions for presentations of primitive values” [components: OData ATOM Format, OData ABNF Construction Rules, OData JSON Format, OData CSDL] is Applied.

Note:

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

ODATA–343:
“Ensure consistent placement and delegation of descritions for presentations of primitive values” [components: OData ATOM Format, OData ABNF Construction Rules, OData JSON Format, OData CSDL] is Closed with no objections.

5.1.25 ODATA–345

ODATA–345:
“Specify which nested query options can be used when expanding only references, and adapt syntax” [components: OData Protocol, OData ABNF Construction Rules, OData URL Conventions] is Applied.

Note:

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

ODATA–345:
“Specify which nested query options can be used when expanding only references, and adapt syntax” [components: OData Protocol, OData ABNF Construction Rules, OData URL Conventions] is Closed with no objections.

5.1.26 ODATA–347

ODATA–347:
“RFC and W3C citation content and formats in odata-atom-format-v4.0-wd01–2013–03–19-with-comments, odata-json-format-v4.0-wd01–2013–03–19-with-comments and odata-core-v4.0-wd01-part1-protocol–2013–4–5-with-comments” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Applied.

Note:

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

ODATA–347:
“RFC and W3C citation content and formats in odata-atom-format-v4.0-wd01–2013–03–19-with-comments, odata-json-format-v4.0-wd01–2013–03–19-with-comments and odata-core-v4.0-wd01-part1-protocol–2013–4–5-with-comments” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Closed with no objections.

5.1.27 ODATA–350

ODATA–350:
“Clearly describe the service documents role, expected usage and responsibility in comparison with $metadata” [components: OData CSDL, OData ATOM Format, OData Protocol, OData JSON Format, OData URL Conventions] is Applied.

Note:

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

ODATA–350:
“Clearly describe the service documents role, expected usage and responsibility in comparison with $metadata” [components: OData CSDL, OData ATOM Format, OData Protocol, OData JSON Format, OData URL Conventions] is Closed with no objections.

5.1.28 ODATA–352

ODATA–352:
“Part II: Review results for OData JSON Format Version 4.0 ” [component: OData JSON Format] is Applied.

Note:

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

ODATA–352:
“Part II: Review results for OData JSON Format Version 4.0 ” [component: OData JSON Format] is Closed with no objections.

5.1.29 ODATA–353

ODATA–353:
“Remove <CollectionType> and <TypeRef> elements” [component: OData CSDL] is Applied.

Note:

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

ODATA–353:
“Remove <CollectionType> and <TypeRef> elements” [component: OData CSDL] is Closed with no objections.

5.1.30 ODATA–354

ODATA–354:
“Make Edm. prefix required when referring to built-in types” [component: OData CSDL] is Applied.

Note:

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

ODATA–354:
“Make Edm. prefix required when referring to built-in types” [component: OData CSDL] is Closed with no objections.

5.1.31 ODATA–355

ODATA–355:
“Define how property paths are represented in key part of URL” [components: OData CSDL, OData ABNF Construction Rules, OData URL Conventions] is Applied.

Note:

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

ODATA–355:
“Define how property paths are represented in key part of URL” [components: OData CSDL, OData ABNF Construction Rules, OData URL Conventions] is Closed with no objections.

5.1.32 ODATA–356

ODATA–356:
“Review the changes in the latest version of Working Drafts” [components: OData Batch Processing Format, OData ATOM Format, OData JSON Format, OData CSDL, OData URL Conventions, OData Protocol, Vocabularies] is Applied.

Note:

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

ODATA–356:
“Review the changes in the latest version of Working Drafts” [components: OData Batch Processing Format, OData ATOM Format, OData JSON Format, OData CSDL, OData URL Conventions, OData Protocol, Vocabularies] is Closed with no objections.

5.1.33 ODATA–357

ODATA–357:
“Use GeoJSON in JSON and GML in Atom to represent geo types” [components: OData JSON Format, OData ATOM Format] is Applied.

Note:

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

ODATA–357:
“Use GeoJSON in JSON and GML in Atom to represent geo types” [components: OData JSON Format, OData ATOM Format] is Closed with no objections.

5.1.34 ODATA–358

ODATA–358:
“Second parameter of the canonical search function should not allow search expressions” [component: OData URL Conventions] is Applied.

Note:

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

ODATA–358:
“Second parameter of the canonical search function should not allow search expressions” [component: OData URL Conventions] is Closed with no objections.

5.1.35 ODATA–359

ODATA–359:
“Allow only true and false as boolean values, remove values 1 and 0, make values case-sensitive, all-lowercase” [component: OData ABNF Construction Rules] is Applied.

Note:

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

ODATA–359:
“Allow only true and false as boolean values, remove values 1 and 0, make values case-sensitive, all-lowercase” [component: OData ABNF Construction Rules] is Closed with no objections.

5.1.36 ODATA–360

ODATA–360:
“Remove edm:documentation element from [CSDL]” [component: OData CSDL] is Applied.

Note:

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

ODATA–360:
“Remove edm:documentation element from [CSDL]” [component: OData CSDL] is Closed with no objections.

5.1.37 ODATA–361

ODATA–361:
“Remove requirement that annotations come after all defined properties in CSDL” [component: OData CSDL] is Applied.

Note:

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

ODATA–361:
“Remove requirement that annotations come after all defined properties in CSDL” [component: OData CSDL] is Closed with no objections.

5.1.38 ODATA–363

ODATA–363:
“specifiying selected properties in metadataurl is broken” [component: OData Protocol] is Applied.

Note:

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

ODATA–363:
“specifiying selected properties in metadataurl is broken” [component: OData Protocol] is Closed with no objections.

5.2 Issues in Proposed state

None

5.2.1 End of Issue Processing

Note:

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

6 Specification review

Note:

A link to an online meeting (to collectively review documents) will be provided in the chat room during the meeting.

6.1 OData Extension for Data Aggregation Version 4.0

Context:

Latest revision OData Extension for Data Aggregation Version 4.0 has been uploaded into Kavi as the corresponding presentation OData-TC 2013–05–02 Data Aggregation.pptx.

Discussion:

7 Next Meeting

7.1 Next TC meeting is conference call on May 9, 2013 during 0800–1000 PT

Agreed

8 AOB

None.

Meeting adjourned on 1001 PT

Appendices

List of Open Action Items Before the Meeting

Retrieval time stamp: 2013-05-01 09:22 +02: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

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.