OData meeting #52, Monday, 19 Sep 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:

    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)
    Ken Baclawski (Northeastern University)
    Martin Zurmuehl (SAP AG)
    Michael Pizzo (Microsoft) a.k.a. Mike
    Ralf Handl (SAP AG)
    Ram Jeyaraman (Microsoft)
    Ron Dagostino (State Street Corp)
    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

Approved.

3 Approval of Minutes from Previous Meeting(s)

3.1 Approval of Minutes of 2013–09–12 Meeting#51

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–09–19 (end of day)

None.

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

None.

5 OData Extension for Data Aggregation

5.1 Currently in first public review ending 19th September 2013.

No public comments yet.

Discussion:

6 Should we produce a revised Committee Specification to address key errata and technical issues?

Context:

Proposal from Mike via E-Mail with subject Proposal for OData Committee Spec Draft #2 has been seconded by Hubert, Ralf and Stefan. Chet Ensign gave feedback on the analysis, stating this is correct and additionally hinted at the fact, that all statements of use (SoU) should target the correct CSD number. So when a CS02 comes to life, all relevant SoU should reference that CS02.

Discussion:

Stefan:

I move that we stop processing known editorial issues as errata and instead direct the editors to prepare new/clean versions of all five specifications (and any related components within the three work products) so they can remove most known defects from the current drafts, prepare even better drafts and the committee may use that as CS02. Martin seconds.

No further discussion. No objections. The motion passes.

Discussion:

Stefan:

I move that we stop processing known editorial issues as errata and instead direct the editors to prepare new/clean versions of all five specifications (and any related components within the three work products) so they can remove most known defects from the current drafts, prepare even better drafts and the committee may use that as CS02 (also including possibly normative changes also including possibly normative changes which will be decided in the next 2 hour long meeting 2013–09–26). Hubert seconds.

Discussion of motion:

No further discussion. No objections. The motion passes.

7 Review of Issues List (IL) and Progress

Notes:

7.1 Issues for v4.0_Errata1

7.1.1 OData CSDL, OData Protocol

7.1.1.1 ODATA–491
ODATA–491:
“Language-dependency of key property values” [components: OData Protocol, OData CSDL] is Open.

Discussion:

ODATA–491:
“Language-dependency of key property values” [components: OData Protocol, OData CSDL] is Open with no objections.

7.1.2 OData ATOM Format, OData JSON Format

7.1.2.1 ODATA–473
ODATA–473:
“Harmonize description of function overload advertisement in Atom and JSON” [components: OData JSON Format, OData ATOM Format] is New.

Discussion:

ODATA–473:
“Harmonize description of function overload advertisement in Atom and JSON” [components: OData JSON Format, OData ATOM Format] is New with no objections.

7.1.3 OData ATOM Format, OData JSON Format, OData Protocol

7.1.3.1 ODATA–472
ODATA–472:
“Explicitly state how dynamic properties are represented if they are not defined on an entity” [components: OData JSON Format, OData ATOM Format, OData Protocol] is New.

Discussion:

ODATA–472:
“Explicitly state how dynamic properties are represented if they are not defined on an entity” [components: OData JSON Format, OData ATOM Format, OData Protocol] is New with no objections.

7.1.4 OData ATOM Format, OData CSDL

7.1.4.1 ODATA–471
ODATA–471:
“Property names must also be a valid XML Names (NCName)” [components: OData CSDL, OData ATOM Format] is New.

Discussion:

ODATA–471:
“Property names must also be a valid XML Names (NCName)” [components: OData CSDL, OData ATOM Format] is New with no objections.

7.1.5 OData URL Conventions

7.1.5.1 ODATA–515
ODATA–515:
“Section 5.1.1.9 Operator Precedence: operators use wrong capitalization in precedence table” [component: OData URL Conventions] is New.

Discussion:

ODATA–515:
“Section 5.1.1.9 Operator Precedence: operators use wrong capitalization in precedence table” [component: OData URL Conventions] is New with no objections.
7.1.5.2 ODATA–514
ODATA–514:
“Example 44: compare Price to a number instead of a string” [component: OData URL Conventions] is New.

Discussion:

ODATA–514:
“Example 44: compare Price to a number instead of a string” [component: OData URL Conventions] is New with no objections.
7.1.5.3 ODATA–492
ODATA–492:
“Add example for ‘has’ operator to section 5.1.1.1.10” [component: OData URL Conventions] is Open.

Discussion:

ODATA–492:
“Add example for ‘has’ operator to section 5.1.1.1.10” [component: OData URL Conventions] is Open with no objections.
7.1.5.4 ODATA–477
ODATA–477:
“Clarify that dynamic properties can be used in all system query options” [component: OData URL Conventions] is New.

Discussion:

ODATA–477:
“Clarify that dynamic properties can be used in all system query options” [component: OData URL Conventions] is New with no objections.
7.1.5.5 ODATA–476
ODATA–476:
“Clarify that type-cast segments are NOT required for properties of derived types in system query options” [component: OData URL Conventions] is New.

Discussion:

ODATA–476:
“Clarify that type-cast segments are NOT required for properties of derived types in system query options” [component: OData URL Conventions] is New with no objections.
7.1.5.6 ODATA–493
ODATA–493:
“Capabilities vocabulary: add term for SearchRestrictions” [component: Vocabularies] is Open.

Discussion:

ODATA–493:
“Capabilities vocabulary: add term for SearchRestrictions” [component: Vocabularies] is Open with no objections.
7.1.5.7 ODATA–475
ODATA–475:
“Document that the value ‘%’ is used for annotating percentages with Measures.Unit” [component: Vocabularies] is New.

Discussion:

ODATA–475:
“Document that the value ‘%’ is used for annotating percentages with Measures.Unit” [component: Vocabularies] is New with no objections.

7.1.6 OData CSDL

7.1.6.1 ODATA–513
ODATA–513:
“Special handling of derived types in the dynamic expression edm:Record. Why?” [component: OData CSDL] is New.

Discussion:

ODATA–513:
“Special handling of derived types in the dynamic expression edm:Record. Why?” [component: OData CSDL] is New with no objections.
7.1.6.2 ODATA–512
ODATA–512:
“14.5.14: add example for specifying a value for a navigation property in a <Record> expression” [component: OData CSDL] is New.

Discussion:

ODATA–512:
“14.5.14: add example for specifying a value for a navigation property in a <Record> expression” [component: OData CSDL] is New with no objections.

7.1.7 OData JSON Format

7.1.7.1 ODATA–508
ODATA–508:
“Delete leftover ‘respectively’ from 6th paragraph of [JSON] Section 5, Service Document” [component: OData JSON Format] is New.

Discussion:

ODATA–508:
“Delete leftover ‘respectively’ from 6th paragraph of [JSON] Section 5, Service Document” [component: OData JSON Format] is New with no objections.
7.1.7.2 ODATA–487
ODATA–487:
“Clarify where relative URLs follow the rules in section 4.3 and where they follow different rules” [component: OData JSON Format] is Open.

Discussion:

ODATA–487:
“Clarify where relative URLs follow the rules in section 4.3 and where they follow different rules” [component: OData JSON Format] is Open with no objections.

7.1.8 OData Protocol

7.1.8.1 ODATA–507
ODATA–507:
“Editorial; text appears twice in section 11.2.6 of [Protocol]” [component: OData Protocol] is New.

Discussion:

ODATA–507:
“Editorial; text appears twice in section 11.2.6 of [Protocol]” [component: OData Protocol] is New with no objections.
7.1.8.2 ODATA–490
ODATA–490:
“Clarify Referential Constraints have UpdateRule=Cascade semantics” [component: OData Protocol] is Open.

Discussion:

ODATA–490:
“Clarify Referential Constraints have UpdateRule=Cascade semantics” [component: OData Protocol] is Open with no objections.
7.1.8.3 ODATA–478
ODATA–478:
“Clarify format for values of Content-ID header in $batch parts” [component: OData Protocol] is New.

Discussion:

ODATA–478:
“Clarify format for values of Content-ID header in $batch parts” [component: OData Protocol] is New with no objections.
7.1.8.4 ODATA–474
ODATA–474:
“Add example for POST/PUT/PATCH/DELETE on function result” [component: OData Protocol] is New.

Discussion:

ODATA–474:
“Add example for POST/PUT/PATCH/DELETE on function result” [component: OData Protocol] is New with no objections.
7.1.8.5 ODATA–470
ODATA–470:
“Clarify behavior of /$value requests to properties of type Edm.Binary or Edm.Geo*” [component: OData Protocol] is New.

Discussion:

ODATA–470:
“Clarify behavior of /$value requests to properties of type Edm.Binary or Edm.Geo*” [component: OData Protocol] is New with no objections.

7.1.9 OData ABNF Construction Rules

7.1.9.1 ODATA–503
ODATA–503:
“Error in ABNF grammer: Edm prefix required for built-in primitive types” [component: OData ABNF Construction Rules] is New.

Discussion:

ODATA–503:
“Error in ABNF grammer: Edm prefix required for built-in primitive types” [component: OData ABNF Construction Rules] is New with no objections.

7.1.10 OData ATOM Format, OData Protocol

7.1.10.1 ODATA–502
ODATA–502:
Fix use of hash (#) for category term attribute in Atom" [components: OData Protocol, OData ATOM Format] is New.

Discussion:

ODATA–502:
Fix use of hash (#) for category term attribute in Atom" [components: OData Protocol, OData ATOM Format] is New with no objections.

7.2 v4.0_Errata1 issues in Applied state

Stefan

I move to close ODATA–511, ODATA–510, ODATA–509, ODATA–506, ODATA–504, ODATA–499, ODATA–495, ODATA–489, ODATA–488, ODATA–486, ODATA–485, ODATA–484, and ODATA–469 as applied. Mike seconds.

No further discussion. No objections. The motion passes.

7.2.1 OData ABNF Construction Rules

Note:

For details on processing of issues in below subsections cf. 7.2 where the motion is documented.

7.2.1.1 ODATA–506
ODATA–506:
“Rule day does not allow the values 10 and 20” [component: OData ABNF Construction Rules] is Applied.

Note:

For details cf. 7.2 where the motion is documented.

ODATA–506:
“Rule day does not allow the values 10 and 20” [component: OData ABNF Construction Rules] is Closed with no objections.
7.2.1.2 ODATA–504
ODATA–504:
“Comment in line 456 should refer to rule lambdaVariableExpr” [component: OData ABNF Construction Rules] is Applied.

Note:

For details cf. 7.2 where the motion is documented.

ODATA–504:
“Comment in line 456 should refer to rule lambdaVariableExpr” [component: OData ABNF Construction Rules] is Closed with no objections.

7.2.2 OData CSDL

Note:

For details on processing of issues in below subsections cf. 7.2 where the motion is documented.

7.2.2.1 ODATA–511
ODATA–511:
“13.6 and 13.6.2: ‘bound’ should hyperlink to section 12.2.3 instead of 12.1.3” [component: OData CSDL] is Applied.

Note:

For details cf. 7.2 where the motion is documented.

ODATA–511:
“13.6 and 13.6.2: ‘bound’ should hyperlink to section 12.2.3 instead of 12.1.3” [component: OData CSDL] is Closed with no objections.
7.2.2.2 ODATA–510
ODATA–510:
“Example 78: replace IsBindable with IsBound” [component: OData CSDL] is Applied.

Note:

For details cf. 7.2 where the motion is documented.

ODATA–510:
“Example 78: replace IsBindable with IsBound” [component: OData CSDL] is Closed with no objections.
7.2.2.3 ODATA–509
ODATA–509:
“14.1: Superfluous period at end of second sentence” [component: OData CSDL] is Applied.

Note:

For details cf. 7.2 where the motion is documented.

ODATA–509:
“14.1: Superfluous period at end of second sentence” [component: OData CSDL] is Closed with no objections.
7.2.2.4 ODATA–499
ODATA–499:
“7.1.3 Nullable should refer to NavigationProperty, not Property” [component: OData CSDL] is Applied.

Note:

For details cf. 7.2 where the motion is documented.

ODATA–499:
“7.1.3 Nullable should refer to NavigationProperty, not Property” [component: OData CSDL] is Closed with no objections.
7.2.2.5 ODATA–495
ODATA–495:
“Clarify that Edm.Double and Edm.Single are 64-bit and 32-bit IEEE754 floating-point numbers” [component: OData CSDL] is Applied.

Note:

For details cf. 7.2 where the motion is documented.

ODATA–495:
“Clarify that Edm.Double and Edm.Single are 64-bit and 32-bit IEEE754 floating-point numbers” [component: OData CSDL] is Closed with no objections.
7.2.2.6 ODATA–489
ODATA–489:
“Clarify wording for OnDelete” [component: OData CSDL] is Applied.

Note:

For details cf. 7.2 where the motion is documented.

ODATA–489:
“Clarify wording for OnDelete” [component: OData CSDL] is Closed with no objections.
7.2.2.7 ODATA–488
  1. ODATA–488: Restrict values of edm:Bool in edm.xsd to lower-case “true” and “false”
ODATA–488:
“Restrict values of edm:Bool in edm.xsd to lower-case ‘true’ and ‘false’ ” [component: OData CSDL] is Applied.

Note:

For details cf. 7.2 where the motion is documented.

ODATA–488:
“Restrict values of edm:Bool in edm.xsd to lower-case ‘true’ and ‘false’ ” [component: OData CSDL] is Closed with no objections.
7.2.2.8 ODATA–486
ODATA–486:
“Missing <Record> wrapper in three examples” [component: OData CSDL] is Applied.

Note:

For details cf. 7.2 where the motion is documented.

ODATA–486:
“Missing <Record> wrapper in three examples” [component: OData CSDL] is Closed with no objections.
7.2.2.9 ODATA–485
ODATA–485:
“Add example for UrlRef expression that contains a literal string that is a URL” [component: OData CSDL] is Applied.

Note:

For details cf. 7.2 where the motion is documented.

ODATA–485:
“Add example for UrlRef expression that contains a literal string that is a URL” [component: OData CSDL] is Closed with no objections.
7.2.2.10 ODATA–484
ODATA–484:
“Remove reference to ‘fixed-length or variable-length’ primitive values” [component: OData CSDL] is Applied.

Note:

For details cf. 7.2 where the motion is documented.

ODATA–484:
“Remove reference to ‘fixed-length or variable-length’ primitive values” [component: OData CSDL] is Closed with no objections.
7.2.2.11 ODATA–469
ODATA–469:
“Type of Extends attribute in edm.xsd must be TQualifiedName instead of TSimpleIdentifier” [component: OData CSDL] is Applied.

Note:

For details cf. 7.2 where the motion is documented.

ODATA–469:
“Type of Extends attribute in edm.xsd must be TQualifiedName instead of TSimpleIdentifier” [component: OData CSDL] is Closed with no objections.

8 Next meeting

8.1 September 26, 2013 during 8–10am PT

Agreed. All will try to allocate two hours time for this meeting.

9 AOB

9.1 Heading levels and table of content

Discussion:

Meeting adjourned on 0901 PT

List of Open Action Items Before the Meeting

Retrieval time stamp: 2013-09-19 15:26 +02:00.

None.

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 7. 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.