OData meeting #27, Thursday, 28 Feb 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

1 Roll call

1.1 Members Present:

    Andrew Eisenberg (IBM)
    Anila Kumar GVN (CA Technologies)
    Barbara Hartel (SAP AG)
    Dale Moberg (Axway Software)
    Gerald Krause (SAP AG)
    Hubert Heijkers (IBM)
    Jeffrey Turpin (Axway Software)
    John Willson (Individual)
    Ken Baclawski (Northeastern University)
    Martin Zurmuehl (SAP AG)
    Michael Pizzo (Microsoft) a.k.a. Mike
    Ralf Handl (SAP AG)
    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–21 Meeting#26

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

None.

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

None.

5 Review of Issues List (IL) and Progress

Notes:

5.1 Issues in Proposed state (carried over from Feb 21, 2013 TC meeting)

5.1.1 OData ABNF Construction Rules, OData URL Conventions

5.1.1.1 ODATA–263
ODATA–263:
“Remove $select=*” [components: OData URL Conventions, OData ABNF Construction Rules] is New.

Discussion:

No further discussion. No objections.

ODATA–263:
“Remove $select=*” [components: OData URL Conventions, OData ABNF Construction Rules] is Open with no objections.

5.1.2 OData ATOM Format, OData JSON Format

5.1.2.1 ODATA–68
ODATA–68:
“Describe representation of ReferenceTypes in responses” [components: OData JSON Format, OData ATOM Format] is New.

Discussion:

No further discussion. No objections.

ODATA–68:
“Describe representation of ReferenceTypes in responses” [components: OData JSON Format, OData ATOM Format] is Open with no objections.
5.1.2.2 ODATA–265
ODATA–265:
“Allow omitting key properties from PUT and PATCH request bodies and from nested entities in deep-insert requests” [components: OData JSON Format, OData ATOM Format] is New.

Ralf:

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

No further discussion. No objections. The motion passes.

ODATA–265:
“Allow omitting key properties from PUT and PATCH request bodies and from nested entities in deep-insert requests” [components: OData JSON Format, OData ATOM Format] is Resolved with no objections.

5.1.3 OData ATOM Format

5.1.3.1 ODATA–200
ODATA–200:
“Remove metadata:type attribute from example in section 5.1” [component: OData ATOM Format] is New.

Mike:

I move to propose we resolve ODATA–200 by clarifying that absence of metadata:type for primitive values is equivalent to metadata:type=string. Ralf seconds.

No further discussion. No objections. The motion passes.

ODATA–200:
“Remove metadata:type attribute from example in section 5.1” [component: OData ATOM Format] is Resolved as noted in the motion with no objections.

5.1.4 OData CSDL

5.1.4.1 ODATA–43
ODATA–43:
“No indicator for optimistic concurrency control on EntityType or EntitySet level” [component: OData CSDL] is New.

Ralf:

I move to resolve ODATA–43 as proposed with the change to use a new Behavior vocabulary and also remove the ConcurrencyMode facet attribute. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–43:
“No indicator for optimistic concurrency control on EntityType or EntitySet level” [component: OData CSDL] is Resolved as noted in the motion with no objections.
5.1.4.2 ODATA–173
ODATA–173:
“Define Action values for OnDelete element” [component: OData CSDL] is Open.

Ralf:

I move to resolve ODATA–173 as proposed. Stefan seconds.

No further discussion. No objections. The motion passes.

ODATA–173:
“Define Action values for OnDelete element” [component: OData CSDL] is Resolved with no objections.
5.1.4.3 ODATA–201
ODATA–201:
“Allow specifying a list of acceptable media types for media entities and named resource properties” [component: OData CSDL] is New.

Discussion:

Ralf:

I move to resolve ODATA–201 as proposed with the following changes: A) Put the term in the Core vocabulary, B) Let it apply to EntityType and Property and C) Add Core.MediaType term of type String that applies to binary properties. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–201:
“Allow specifying a list of acceptable media types for media entities and named resource properties” [component: OData CSDL] is Resolved as noted in the motion with no objections.
5.1.4.4 ODATA–234
ODATA–234:
“Merge Reference and AnnotationReference element” [component: OData CSDL] is Open.

Discussion:

Ralf:

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

No further discussion. No objections. The motion passes.

ODATA–234:
“Merge Reference and AnnotationReference element” [component: OData CSDL] is Resolved with no objections.
5.1.4.5 ODATA–236
ODATA–236:
“Define maximum length of namespace names and simple identifiers” [component: OData CSDL] is New.

Discussion:

Mike:

I move we define a max identifier length of 128 and a max namespace name of 511 characters. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–236:
“Define maximum length of namespace names and simple identifiers” [component: OData CSDL] is Resolved as noted in the motion with no objections.
5.1.4.6 ODATA–242
ODATA–242:
“Allow Path expressions also for annotations targeting an entity container” [component: OData CSDL] is New.

Ralf:

I move to resolve ODATA–242 as proposed. Hubert seconds.

No further discussion. No objections. The motion passes.

ODATA–242:
“Allow Path expressions also for annotations targeting an entity container” [component: OData CSDL] is Resolved with no objections.
5.1.4.7 ODATA–257
ODATA–257:
“Define standard client-side function for filling URL templates (RFC6570)” [component: OData CSDL] is New.

Discussion:

Ralf:

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

No further discussion. No objections. The motion passes.

ODATA–257:
“Define standard client-side function for filling URL templates (RFC6570)” [component: OData CSDL] is Resolved with no objections.
5.1.4.8 ODATA–278
ODATA–278:
“Introduce vocabulary expression edm:Url” [component: OData CSDL] is New.

Martin:

I move to resolve ODATA–278 as proposed. Hubert seconds.

Discussion of the motion:

No further discussion. No objections. The motion passes.

ODATA–278:
“Introduce vocabulary expression edm:Url” [component: OData CSDL] is Resolved with no objections.

5.1.5 OData Protocol

5.1.5.1 ODATA–262
ODATA–262:
“Specify how OData services can be protected against cross-site request forgery (CSRF or XSRF)” [component: OData Protocol] is New.

Discussion:

No further discussion. No objections.

ODATA–262:
“Specify how OData services can be protected against cross-site request forgery (CSRF or XSRF)” [component: OData Protocol] is Open with no objections.
5.1.5.1.1 End of Issue Processing

Note:

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

6 Next Meeting

6.1 Next weekly TC meeting will be 2013–03–07 during 8–10am PT.

Agreed.

7 AOB

None.

Meeting adjourned on 1000 PT

Appendices

List of Open Action Items Before the Meeting

Retrieval time stamp: 2013-02-28 09:55 +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

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.