OData meeting #54, Tuesday, 01 Oct 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)
    Gerald Krause (SAP AG)
    Hubert Heijkers (IBM)
    John Willson (Individual)
    Ken Baclawski (Northeastern University)
    Martin Zurmuehl (SAP AG)
    Matthew Borges (SAP AG) a.k.a. Matt
    Mike 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)

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–26 Meeting#53

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–10–01 (end of day)

None.

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

None.

5 Review of Issues List (IL) and Progress

Notes:

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

5.1.1 OData Protocol

5.1.1.1 ODATA–490
ODATA–490:
“Clarify Referential Constraints have UpdateRule=Cascade semantics” [component: OData Protocol] is Open.

Discussion:

Hubert:

I move to resolve OData–490 as proposed. Matt seconds.

No further discussion. No objections. The motion passes.

ODATA–490:
“Clarify Referential Constraints have UpdateRule=Cascade semantics” [component: OData Protocol] is Resolved as updated during the meeting with no objections.

5.1.2 Vocabularies

5.1.2.1 ODATA–531
ODATA–531:
“Simplify OptimisticConcurrency in Core vocabulary” [component: Vocabularies] is New.

Discussion:

Mike:

I move to resolve OData–531 as proposed. Ralf seconds.

No further discussion. No objections. The motion passes.

ODATA–531:
“Simplify OptimisticConcurrency in Core vocabulary” [component: Vocabularies] is Resolved with no objections.
5.1.2.2 ODATA–534
ODATA–534:
“Tag type definition in Core should have default boolean value = true” [component: Vocabularies] is Open.

Discussion:

Mike:

I move to close OData–534 with no action. Ralf seconds.

No further discussion. No objections. The motion passes.

ODATA–534:
“Tag type definition in Core should have default boolean value = true” [component: Vocabularies] is Closed with no objections.

5.1.3 OData ATOM Format, OData CSDL, OData JSON Format, OData Protocol

5.1.3.1 ODATA–527
ODATA–527:
“Relative URLs in OData and the ability to put OData services behind an HTTP proxy” [components: OData CSDL, OData ATOM Format, OData Protocol, OData JSON Format] is Open.

Discussion:

No further discussion. No objections.

ODATA–527:
“Relative URLs in OData and the ability to put OData services behind an HTTP proxy” [components: OData CSDL, OData ATOM Format, OData Protocol, OData JSON Format] is Open with no objections.

5.1.4 OData Protocol

5.1.4.1 ODATA–523
ODATA–523:
“How do clients construct links from the context url for complex types?” [component: OData Protocol] is Open.

Discussion:

No further discussion. No objections.

ODATA–523:
“How do clients construct links from the context url for complex types?” [component: OData Protocol] is Open with no objections.

5.1.5 OData CSDL

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

Discussion:

No further discussion. No objections.

ODATA–513:
“Special handling of derived types in the dynamic expression edm:Record. Why?” [component: OData CSDL] is Open with no objections.
5.1.5.2 ODATA–535
ODATA–535:
“Define specialization for terms” [component: OData CSDL] is Open.

Discussion:

No further discussion. No objections.

ODATA–535:
“Define specialization for terms” [component: OData CSDL] is Open with no objections.

5.1.6 Any other issues for v4.0_CS02

#####5.1.6.1 ODATA–538
ODATA–538:
“Clarify treatment of odata.type with derived types and odata.context for delta responses for odata.metadata=none” [component: OData JSON Format] is New.

Discussion:

No further discussion. No objections.

ODATA–538:
“Clarify treatment of odata.type with derived types and odata.context for delta responses for odata.metadata=none” [component: OData JSON Format] is Open with no objections.
#####5.1.6.2 ODATA–539
ODATA–539:
“Delta response encoding is unnecessarily verbose and change type is missing when odata.metadata=none” [components: OData JSON Format, OData ATOM Format, OData Protocol] is New.

Discussion:

No further discussion. No objections.

ODATA–539:
“Delta response encoding is unnecessarily verbose and change type is missing when odata.metadata=none” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Open with no objections.
#####5.1.6.1 ODATA–536
ODATA–536:
“Treatment of circular references when using $levels” [components: OData URL Conventions, OData Protocol] is New.

Discussion:

Ralf:

I move to resolve OData-xxx as proposed. Stefan seconds.

No further discussion. No objections. The motion passes.

ODATA–536:
“Treatment of circular references when using $levels” [components: OData URL Conventions, OData Protocol] is Resolved with no objections.

5.2 v4.0_CS02 issues in Applied state

Discussion:

Mike:

I move we accept the changes to ODATA–466 as applied by allowing the padding characters and disallowing white space within encoded values. John seconds.

No further discussion. No objections. The motion passes.

Additional Discussion:

Stefan:

I move to close ODATA–540, ODATA–533, ODATA–530, ODATA–528, ODATA–526, ODATA–525, ODATA–524, ODATA–522, ODATA–521, ODATA–520, ODATA–519, ODATA–518, ODATA–517, ODATA–515, ODATA–514, ODATA–512, ODATA–508, ODATA–507, ODATA–505, ODATA–503, ODATA–502, ODATA–501, ODATA–500, ODATA–498, ODATA–497, ODATA–496, ODATA–493, ODATA–492, ODATA–491, ODATA–487, ODATA–483, ODATA–481, ODATA–478, ODATA–477, ODATA–476, ODATA–475, ODATA–474, ODATA–473, ODATA–472, ODATA–471, ODATA–470, ODATA–468, and DATA–466 as applied. Mike seconds.

No further discussion. No objections. The motion passes.

5.2.1 ODATA–540

ODATA–540:
“Explicitly state that the Context URL locates (a specific portion of) the metadata document” [component: OData Protocol] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–540:
“Explicitly state that the Context URL locates (a specific portion of) the metadata document” [component: OData Protocol] is Closed with no objections.

5.2.2 ODATA–537

ODATA–537:
“Ordering of navigationLink and associationLink annotations in JSON” [component: OData JSON Format] is Applied.

Note:

For details cf. 5.2 where the discussion is documented.

ODATA–537:
“Ordering of navigationLink and associationLink annotations in JSON” [component: OData JSON Format] is Resolved with no objections.

5.2.3 ODATA–533

ODATA–533:
“Restrict key property aliases to key properties nested in complex properties” [component: OData CSDL] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–533:
“Restrict key property aliases to key properties nested in complex properties” [component: OData CSDL] is Closed with no objections.

5.2.4 ODATA–532

ODATA–532:
“Clarify whether collections can contain null values” [components: OData CSDL, OData ATOM Format, OData Protocol, OData JSON Format] is Applied.

Note:

For details cf. 5.2 where the discussion is documented.

ODATA–532:
“Clarify whether collections can contain null values” [components: OData CSDL, OData ATOM Format, OData Protocol, OData JSON Format] is Resolved with no objections.

5.2.5 ODATA–530

ODATA–530:
“Navigable capability term should apply to entityset, not navigationproperty directly” [component: Vocabularies] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–530:
“Navigable capability term should apply to entityset, not navigationproperty directly” [component: Vocabularies] is Closed with no objections.

5.2.6 ODATA–528

ODATA–528:
“$entity should require cast segment in order to apply $select/$expand” [components: OData Protocol, OData ABNF Construction Rules] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–528:
“$entity should require cast segment in order to apply $select/$expand” [components: OData Protocol, OData ABNF Construction Rules] is Closed with no objections.

5.2.7 ODATA–526

ODATA–526:
“Allow specifying support for cross-joins” [component: Vocabularies] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–526:
“Allow specifying support for cross-joins” [component: Vocabularies] is Closed with no objections.

5.2.8 ODATA–525

ODATA–525:
“Remove Org.OData.Atom vocabulary” [components: Vocabularies, OData ATOM Format] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–525:
“Remove Org.OData.Atom vocabulary” [components: Vocabularies, OData ATOM Format] is Closed with no objections.

5.2.9 ODATA–524

ODATA–524:
“properties in [propertyList] of context URL may be qualified with type” [components: OData Protocol, OData ABNF Construction Rules] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–524:
“properties in [propertyList] of context URL may be qualified with type” [components: OData Protocol, OData ABNF Construction Rules] is Closed with no objections.

5.2.10 ODATA–522

ODATA–522:
“Clarify that the has operator returns null if either operand is null.” [component: OData URL Conventions] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–522:
“Clarify that the has operator returns null if either operand is null.” [component: OData URL Conventions] is Closed with no objections.

5.2.11 ODATA–521

ODATA–521:
“Remove typed null literals” [components: OData Protocol, OData ABNF Construction Rules] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–521:
“Remove typed null literals” [components: OData Protocol, OData ABNF Construction Rules] is Closed with no objections.

5.2.12 ODATA–520

ODATA–520:
“Instance annotations should be prefixed with ‘@’” [component: OData JSON Format] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–520:
“Instance annotations should be prefixed with ‘@’” [component: OData JSON Format] is Closed with no objections.

5.2.13 ODATA–519

ODATA–519:
“Define server-driven paging for collection-valued resources” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–519:
“Define server-driven paging for collection-valued resources” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Closed with no objections.

5.2.14 ODATA–518

ODATA–518:
“Use NavProp@<annotation-name> to reference annotations applied to a NavProp” [component: OData CSDL] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–518:
“Use NavProp@<annotation-name> to reference annotations applied to a NavProp” [component: OData CSDL] is Closed with no objections.

5.2.15 ODATA–517

ODATA–517:
“Allow NavigationPropertyPath and PropertyPath expressions to end in annotations of appropriate type” [component: OData CSDL] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–517:
“Allow NavigationPropertyPath and PropertyPath expressions to end in annotations of appropriate type” [component: OData CSDL] is Closed with no objections.

5.2.16 ODATA–515

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

Note:

For details cf. 5.2 where the motion is documented.

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

5.2.17 ODATA–514

ODATA–514:
“Example 44: compare Price to a number instead of a string” [component: OData URL Conventions] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–514:
“Example 44: compare Price to a number instead of a string” [component: OData URL Conventions] is Closed with no objections.

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

Note:

For details cf. 5.2 where the motion is documented.

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

5.2.19 ODATA–508

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

Note:

For details cf. 5.2 where the motion is documented.

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

5.2.20 ODATA–507

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

Note:

For details cf. 5.2 where the motion is documented.

ODATA–507:
“Editorial; text appears twice in section 11.2.6 of [Protocol]” [component: OData Protocol] is Closed with no objections.

5.2.21 ODATA–505

ODATA–505:
“Remove ReturnType attribute from Action and Function element” [component: OData CSDL] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–505:
“Remove ReturnType attribute from Action and Function element” [component: OData CSDL] is Closed with no objections.

5.2.22 ODATA–503

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

Note:

For details cf. 5.2 where the motion is documented.

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

5.2.23 ODATA–502

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

Note:

For details cf. 5.2 where the motion is documented.

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

5.2.24 ODATA–501

ODATA–501:
“has operator is missing from the operator precedence table” [component: OData URL Conventions] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–501:
“has operator is missing from the operator precedence table” [component: OData URL Conventions] is Closed with no objections.

5.2.25 ODATA–500

ODATA–500:
“Require function/action overloads to differ by ordered set of parameter types” [component: OData CSDL] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–500:
“Require function/action overloads to differ by ordered set of parameter types” [component: OData CSDL] is Closed with no objections.

5.2.26 ODATA–498

ODATA–498:
“Error with m:type in Example 31 of Atom” [component: OData ATOM Format] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–498:
“Error with m:type in Example 31 of Atom” [component: OData ATOM Format] is Closed with no objections.

5.2.27 ODATA–497

ODATA–497:
“Remove type prefix and single quotes for URL literals of types Date, DateTimeOffset, Guid, and TimeOfDay” [components: OData URL Conventions, OData ABNF Construction Rules] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–497:
“Remove type prefix and single quotes for URL literals of types Date, DateTimeOffset, Guid, and TimeOfDay” [components: OData URL Conventions, OData ABNF Construction Rules] is Closed with no objections.

5.2.28 ODATA–496

ODATA–496:
“Adapt outdated action/function overload resolution rules in Part 1 to current rules in Part 3” [component: OData Protocol] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–496:
“Adapt outdated action/function overload resolution rules in Part 1 to current rules in Part 3” [component: OData Protocol] is Closed with no objections.

5.2.29 ODATA–493

ODATA–493:
“Capabilities vocabulary: add term for SearchRestrictions” [component: Vocabularies] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–493:
“Capabilities vocabulary: add term for SearchRestrictions” [component: Vocabularies] is Closed with no objections.

5.2.30 ODATA–492

ODATA–492:
“Add example for „has’ operator to section 5.1.1.1.10” [component: OData URL Conventions] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–492:
“Add example for „has’ operator to section 5.1.1.1.10” [component: OData URL Conventions] is Closed with no objections.

5.2.31 ODATA–491

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

Note:

For details cf. 5.2 where the motion is documented.

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

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

Note:

For details cf. 5.2 where the motion is documented.

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

5.2.33 ODATA–483

ODATA–483:
“Include all section levels in table of contents, provide anchors for all document sections” [components: OData CSDL, OData ATOM Format, OData Extension for JSON Data, OData Extension for Data Aggregation, OData JSON Format, OData Extension for Temporal Data, OData URL Conventions, OData Protocol] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–483:
“Include all section levels in table of contents, provide anchors for all document sections” [components: OData CSDL, OData ATOM Format, OData Extension for JSON Data, OData Extension for Data Aggregation, OData JSON Format, OData Extension for Temporal Data, OData URL Conventions, OData Protocol] is Closed with no objections.

5.2.34 ODATA–481

ODATA–481:
“Annotation/Navigation/Path expressions: allow paths to continue after multi-valued navigation to e.g. drill into complex properties” [component: OData CSDL] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–481:
“Annotation/Navigation/Path expressions: allow paths to continue after multi-valued navigation to e.g. drill into complex properties” [component: OData CSDL] is Closed with no objections.

5.2.35 ODATA–478

ODATA–478:
“Clarify format for values of Content-ID header in $batch parts” [component: OData Protocol] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–478:
“Clarify format for values of Content-ID header in $batch parts” [component: OData Protocol] is Closed with no objections.

5.2.36 ODATA–477

ODATA–477:
“Clarify that dynamic properties can be used in all system query options” [component: OData URL Conventions] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–477:
“Clarify that dynamic properties can be used in all system query options” [component: OData URL Conventions] is Closed with no objections.

5.2.37 ODATA–476

ODATA–476:
“Clarify that type-cast segments are required for properties of derived types in system query options” [component: OData URL Conventions] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–476:
“Clarify that type-cast segments are required for properties of derived types in system query options” [component: OData URL Conventions] is Closed with no objections.

5.2.38 ODATA–475

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

Note:

For details cf. 5.2 where the motion is documented.

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

5.2.39 ODATA–474

ODATA–474:
“Add example for POST/PUT/PATCH/DELETE on function result” [component: OData Protocol] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–474:
“Add example for POST/PUT/PATCH/DELETE on function result” [component: OData Protocol] is Closed with no objections.

5.2.40 ODATA–473

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

Note:

For details cf. 5.2 where the motion is documented.

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

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

Note:

For details cf. 5.2 where the motion is documented.

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 Closed with no objections.

5.2.42 ODATA–471

ODATA–471:
“Property names must also be a valid XML Names (NCName)” [component: OData CSDL] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–471:
“Property names must also be a valid XML Names (NCName)” [component: OData CSDL] is Closed with no objections.

5.2.43 ODATA–470

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

Note:

For details cf. 5.2 where the motion is documented.

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

5.2.44 ODATA–468

ODATA–468:
“Define explicit concepts in ABNF for referenced sets of rules” [components: OData CSDL, OData ABNF Construction Rules] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–468:
“Define explicit concepts in ABNF for referenced sets of rules” [components: OData CSDL, OData ABNF Construction Rules] is Closed with no objections.

5.2.45 ODATA–466

ODATA–466:
“Edm.Binary should be base64-encoded (as with OData V3), not base16-encoded (as per current ABNF)” [components: OData ATOM Format, OData ABNF Construction Rules, OData JSON Format, OData CSDL, OData URL Conventions] is Applied.

Note:

For details cf. 5.2 where the motion is documented.

ODATA–466:
“Edm.Binary should be base64-encoded (as with OData V3), not base16-encoded (as per current ABNF)” [components: OData ATOM Format, OData ABNF Construction Rules, OData JSON Format, OData CSDL, OData URL Conventions] is Closed with no objections.
5.2.45.1 End of Issue Processing

Note:

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

6 Review revised TC timeline and immediate next steps

6.1 Oct 3rd, 2013:

Approve CSD03?

6.2 Oct 10–24, 2013:

3rd public review?

7 Next meetings

7.1 October 3, 2013 during 8–10am PT

Agreed.

8 AOB

None.

Meeting adjourned on 0944 PT

List of Open Action Items Before the Meeting

Retrieval time stamp: 2013-10-01 16:55 +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 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.