OData meeting #29, Thursday, 14 Mar 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 Ram Jeyaraman

1 Roll call

1.1 Members Present:

    Andrew Eisenberg (IBM)
    Barbara Hartel (SAP AG)
    Dale Moberg (Axway Software)
    Diane Downie (Citrix Systems)
    Erik de Voogd (SDL)
    Gerald Krause (SAP AG)
    Hubert Heijkers (IBM)
    John Willson (Individual)
    Ken Baclawski (Northeastern University)
    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)
    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–03–07 Meeting#28

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

None.

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

None.

5 Specification Editors for Work Product

Context:

Current editors as documented in the latest revisions of the work products:

Discussion:

6 Review of Issues List (IL) and Progress

Notes:

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

6.1.1 OData Protocol

6.1.1.1 ODATA–37
ODATA–37:
“UPSERT: allow PUT and PATCH to the URL of a not yet existing entity to create this entity ” [component: OData Protocol] is Open.

Ralf:

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

No further discussion. No objections. The motion passes.

ODATA–37:
“UPSERT: allow PUT and PATCH to the URL of a not yet existing entity to create this entity ” [component: OData Protocol] is Resolved with no objections.
6.1.1.2 ODATA–42
ODATA–42:
“8.2.5 If-None-Match: clarify use of If-None-Match in data modification or action requests” [component: OData Protocol] is Open.

Ralf:

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

No further discussion. No objections. The motion passes.

ODATA–42:
“8.2.5 If-None-Match: clarify use of If-None-Match in data modification or action requests” [component: OData Protocol] is Resolved with no objections.
6.1.1.3 ODATA–246
ODATA–246:
“IDs should be dereferenceable URIs” [component: OData Protocol] is New.

Hubert:

I move to resolve ODATA–246 as proposed. John seconds.

No further discussion. No objections. The motion passes.

ODATA–246:
“IDs should be dereferenceable URIs” [component: OData Protocol] is Resolved with no objections.

6.2 Issues in Proposed state (carried over from Feb 28, 2013 TC meeting)

6.2.1 OData CSDL

6.2.1.1 ODATA–275
ODATA–275:
“Clarify that binding parameters for actions and functions cannot be nullable” [component: OData CSDL] is Open.

Mike:

I move we resolve ODATA–275 as modified by clarifying that binding parameters may be nullable. Andrew seconds.

No further discussion. No objections. The motion passes.

ODATA–275:
“Clarify that binding parameters for actions and functions cannot be nullable” [component: OData CSDL] is Resolved as noted in the motion with no objections.
6.2.1.2 ODATA–256
ODATA–256:
“Simplify numeric data types” [component: OData CSDL] is New.

Stefan:

I move to close ODATA–256 without action. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–256:
“Simplify numeric data types” [component: OData CSDL] is Closed as noted in the motion with no objections.

6.3 Issues in Proposed state (carried over from March 7, 2013 TC meeting)

6.3.1 OData CSDL, OData Protocol

6.3.1.1 ODATA–270
ODATA–270:
“Collections of Edm.PrimitiveType are problematic in JSON” [components: OData Protocol, OData CSDL] is Open.

Mike:

I move we resolve ODATA–270 as proposed. John seconds.

No further discussion. No objections. The motion passes.

ODATA–270:
“Collections of Edm.PrimitiveType are problematic in JSON” [components: OData Protocol, OData CSDL] is Resolved with no objections.

6.3.2 OData ABNF Construction Rules, OData Protocol, OData URL Conventions

6.3.2.1 ODATA–177
ODATA–177:
“Allow entities to be members of multiple entity sets” [component: OData Protocol] is Open.

Discussion:

Ralf:

I move to close ODATA–177 without action. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–177:
“Allow entities to be members of multiple entity sets” [component: OData Protocol] is Closed with no objections.
6.3.2.2 ODATA–139
ODATA–139:
“New system query option $search for free-text search within an entity set” [components: OData Protocol, OData ABNF Construction Rules, OData URL Conventions] is Resolved.

Discussion:

Steafn:

I move to resolve ODATA–139 as described in the updated proposal with possible implications for the related $search issues like ODATA–222 i.e. “free-text search within a property” and ODATA–228 “Specify $search for free-text search within a OData Service and specify $search for free-text search within an entityContainer”. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–139:
“New system query option $search for free-text search within an entity set” [components: OData Protocol, OData ABNF Construction Rules, OData URL Conventions] is Resolved as noted in the motion with no objections.

6.3.3 OData JSON Format, OData Protocol

6.3.3.1 ODATA–283
ODATA–283:
“Accept-Charset HTTP Request Header and charset content-type parameter” [components: OData Protocol, OData JSON Format] is Open.

Discussion:

No further discussion. No objections.

ODATA–283:
“Accept-Charset HTTP Request Header and charset content-type parameter” [components: OData Protocol, OData JSON Format] is Open with no objections.

6.3.4 OData ATOM Format, OData JSON Format

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

Ralf:

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

No further discussion. No objections. The motion passes.

ODATA–68:
“Describe representation of ReferenceTypes in responses” [components: OData CSDL, OData ATOM Format, OData JSON Format] is Resolved with no objections.

6.4 Issues in Proposed state (since March 7, 2013 TC meeting)

6.4.1 OData CSDL

6.4.1.1 ODATA–277
ODATA–277:
“Remove Collation attribute” [component: OData CSDL] is New.

Discussion:

Ralf:

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

No further discussion. No objections. The motion passes.

ODATA–277:
“Remove Collation attribute” [component: OData CSDL] is Resolved with no objections.
6.4.1.2 ODATA–288
ODATA–288:
“Change default decimal Scale to variable” [component: OData CSDL] is New.

Discussion:

Hubert:

I move to resolve ODATA–288 as per the amended proposal by Ralf and as updated in JIRA. Martin seconds.

No further discussion. No objections. The motion passes.

ODATA–288:
“Change default decimal Scale to variable” [component: OData CSDL] is Resolved as noted in the motion with no objections.
6.4.1.3 ODATA–124
ODATA–124:
“For round-tripping values, what precision must agents support for DateTime(Offset), and are leap seconds permitted?” [component: OData CSDL] is New.

Stefan:

I move to resolve ODATA–124 as proposed. Andrew seconds.

No further discussion. No objections. The motion passes.

ODATA–124:
“For round-tripping values, what precision must agents support for DateTime(Offset), and are leap seconds permitted?” [component: OData CSDL] is Resolved with no objections.

6.4.2 OData URL Conventions

6.4.2.1 ODATA–285
ODATA–285:
“Section 4.7: explicitly mention which property types allow appending /$value” [component: OData URL Conventions] is New.

Stefan:

I move to resolve ODATA–285 as proposed. Ralf seconds.

No further discussion. No objections. The motion passes.

ODATA–285:
“Section 4.7: explicitly mention which property types allow appending /$value” [component: OData URL Conventions] is Resolved with no objections.

6.4.3 Vocabularies

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

Discussion:

Martin:

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

No further discussion. No objections. The motion passes.

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

6.4.4 OData CSDL, OData Protocol

6.4.4.1 ODATA–292
ODATA–292:
“Questions on POST, PATCH and merge/replace semantics with related entities in composite relationships” [component: OData Protocol] is New.

Mike:

I move we resolve ODATA–292 with the two clarifications proposed. Hubert seconds.

No further discussion. No objections. The motion passes.

ODATA–292:
“Questions on POST, PATCH and merge/replace semantics with related entities in composite relationships” [component: OData Protocol] is Resolved as noted in the motion with no objections.

6.4.5 OData Protocol

6.4.5.1 ODATA–293
ODATA–293:
“Clarify protocol or JSON spec: are servers REQUIRED to support JSON format?” [components: OData Protocol, OData JSON Format] is New.

Discussion:

Hubert:

I move to resolve ODATA–293 with no action as proposed. Mike seconds.

No further discussion. No objections. The motion passes.

ODATA–293:
“Clarify protocol or JSON spec: are servers REQUIRED to support JSON format?” [components: OData Protocol, OData JSON Format] is Closed as noted in the motion with no objections.

6.5 Issues in Applied state (carried over from Feb 28, 2013)

Discussion:

Stefan:

I move to close ODATA–214, ODATA–179, ODATA–215, ODATA–251, ODATA–250, ODATA–178, ODATA–147 and ODATA–146 as applied. Mike seconds.

No further discussion. No objections. The motion passes.

6.5.1 OData ABNF Construction Rules, OData ATOM Format, OData CSDL, OData JSON Format, OData Protocol, OData URL Conventions

6.5.1.1 ODATA–214
ODATA–214:
“Find consensus on ‘Additional artifacts’-section of multi component Work Products (and implement accordingly) ” [components: OData ATOM Format, OData ABNF Construction Rules, OData JSON Format, OData CSDL, OData URL Conventions, OData Protocol] is Applied.

Note:

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

ODATA–214:
“Find consensus on ‘Additional artifacts’-section of multi component Work Products (and implement accordingly) ” [components: OData ATOM Format, OData ABNF Construction Rules, OData JSON Format, OData CSDL, OData URL Conventions, OData Protocol] is Closed with no objections.
6.5.1.2 ODATA–179
ODATA–179:
“Adapt OData inter document references to new work product structuring of core” [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 [6.5])

ODATA–179:
“Adapt OData inter document references to new work product structuring of core” [components: OData CSDL, OData ATOM Format, OData Protocol, OData JSON Format, OData URL Conventions] is Closed with no objections.

6.5.2 OData ABNF Construction Rules, OData URL Conventions

6.5.2.1 ODATA–215
ODATA–215:
“Remove hour(), minute() and second() query functions and add corresponding overloads to the hours(), minutes(), and seconds() functions” [components: OData URL Conventions, OData ABNF Construction Rules] is Applied.

Note:

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

ODATA–215:
“Remove hour(), minute() and second() query functions and add corresponding overloads to the hours(), minutes(), and seconds() functions” [components: OData URL Conventions, OData ABNF Construction Rules] is Closed with no objections.

6.5.3 OData ATOM Format

6.5.3.1 ODATA–251
ODATA–251:
“Clarify, within [ATOM], that complex types can be annotated” [component: OData ATOM Format] is Applied.

Note:

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

ODATA–251:
“Clarify, within [ATOM], that complex types can be annotated” [component: OData ATOM Format] is Closed with no objections.
6.5.3.2 ODATA–250
ODATA–250:
“For instance annotations in Atom, ‘Annotation’ element, ‘Type’, ‘Term’ and ‘Target’ attributes should be lower case” [component: OData ATOM Format] is Applied.

Note:

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

ODATA–250:
“For instance annotations in Atom, ‘Annotation’ element, ‘Type’, ‘Term’ and ‘Target’ attributes should be lower case” [component: OData ATOM Format] is Closed with no objections.
6.5.3.3 ODATA–178
ODATA–178:
“Enhance abstract, distinguish its content from 1st paragraph of introduction and edit the payload object listing in 2nd para of 1 Introduction” [component: OData ATOM Format] is Applied.

Note:

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

ODATA–178:
“Enhance abstract, distinguish its content from 1st paragraph of introduction and edit the payload object listing in 2nd para of 1 Introduction” [component: OData ATOM Format] is Closed with no objections.
6.5.3.4 ODATA–147
ODATA–147:
“Add example for $inlinecount representation” [component: OData ATOM Format] is Applied.

Note:

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

ODATA–147:
“Add example for $inlinecount representation” [component: OData ATOM Format] is Closed with no objections.
6.5.3.5 ODATA–146
ODATA–146:
“Add example for inlining expanded entities” [component: OData ATOM Format] is Applied.

Note:

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

ODATA–146:
“Add example for inlining expanded entities” [component: OData ATOM Format] is Closed with no objections.

6.5.4 OData CSDL

Discussion:

Stefan:

I move to close ODATA–273, ODATA–272, ODATA–268, ODATA–237, ODATA–76 and ODATA–269 as applied. Mike seconds.

No further discussion. No objections. The motion passes.

6.5.4.1 ODATA–273
ODATA–273:
“Clarify whether derived types MUST introduce new properties” [component: OData CSDL] is Applied.

Note:

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

ODATA–273:
“Clarify whether derived types MUST introduce new properties” [component: OData CSDL] is Closed with no objections.
6.5.4.2 ODATA–272
ODATA–272:
“Remove FixedLength facet” [component: OData CSDL] is Applied.

Note:

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

ODATA–272:
“Remove FixedLength facet” [component: OData CSDL] is Closed with no objections.
6.5.4.3 ODATA–268
ODATA–268:
“Use http://docs.oasis-open.org/odata/ns/edm as the EDM namespace URL” [component: OData CSDL] is Applied.

Note:

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

ODATA–268:
“Use http://docs.oasis-open.org/odata/ns/edm as the EDM namespace URL” [component: OData CSDL] is Closed with no objections.
6.5.4.4 ODATA–237
ODATA–237:
“Require type usage to always specify a qualified name for types other than the built-in primitive types” [component: OData CSDL] is Applied.

Note:

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

ODATA–237:
“Require type usage to always specify a qualified name for types other than the built-in primitive types” [component: OData CSDL] is Closed with no objections.
6.5.4.5 ODATA–76
ODATA–76:
“Edm.Decimal is a floating-point type” [component: OData CSDL] is Applied.

Note:

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

ODATA–76:
“Edm.Decimal is a floating-point type” [component: OData CSDL] is Closed with no objections.

6.5.5 OData CSDL, OData Protocol

6.5.5.1 ODATA–269
ODATA–269:
“Separate Functions and Actions” [components: OData Protocol, OData CSDL] is Applied.

Note:

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

ODATA–269:
“Separate Functions and Actions” [components: OData Protocol, OData CSDL] is Closed with no objections.

6.5.6 OData JSON Format

Stefan:

I move to close ODATA–249, ODATA–110, ODATA–129, ODATA–261 and ODATA–103 as applied. Ralf seconds.

No further discussion. No objections. The motion passes.

6.5.6.1 ODATA–249
ODATA–249:
“‘Kind’ property should be optional for EntitySets in JSON Service Documents” [component: OData JSON Format] is Applied.

Note:

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

ODATA–249:
“‘Kind’ property should be optional for EntitySets in JSON Service Documents” [component: OData JSON Format] is Closed with no objections.

6.5.7 OData Protocol

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

Note:

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

ODATA–110:
“Track Prefer Header in Http” [component: OData Protocol] is Closed with no objections.
6.5.7.2 ODATA–129
ODATA–129:
“Explicitly mention dynamic navigation properties in [Core]” [component: OData Protocol] is Applied.

Note:

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

ODATA–129:
“Explicitly mention dynamic navigation properties in [Core]” [component: OData Protocol] is Closed with no objections.
6.5.7.3 ODATA–261
ODATA–261:
“Improve section 10.2.3.8 The $format System Query Option” [component: OData Protocol] is Applied.

Note:

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

ODATA–261:
“Improve section 10.2.3.8 The $format System Query Option” [component: OData Protocol] is Closed with no objections.
6.5.7.4 ODATA–103
ODATA–103:
“5.4.1 Representing Actions Bound to Multiple Entities: specify treatment of action overloads” [component: OData Protocol] is Applied.

Note:

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

ODATA–103:
“5.4.1 Representing Actions Bound to Multiple Entities: specify treatment of action overloads” [component: OData Protocol] is Closed with no objections.

6.5.8 OData URL Conventions

Stefan:

I move to close ODATA–142, ODATA–140, ODATA–203, ODATA–104, ODATA–72 and ODATA–122 as applied. Hubert seconds.

No further discussion. No objections. The motion passes.

6.5.8.1 ODATA–142
ODATA–142:
“Define URL functions geo.distance, geo.length, geo.intersects, and gettotaloffsetminutes” [component: OData URL Conventions] is Applied.

Note:

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

ODATA–142:
“Define URL functions geo.distance, geo.length, geo.intersects, and gettotaloffsetminutes” [component: OData URL Conventions] is Closed with no objections.
6.5.8.2 ODATA–140
ODATA–140:
“Describe rules for accessing derived entity and complex types in URLs” [component: OData URL Conventions] is Applied.

Note:

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

ODATA–140:
“Describe rules for accessing derived entity and complex types in URLs” [component: OData URL Conventions] is Closed with no objections.
6.5.8.3 ODATA–203
ODATA–203:
“Specify Operator Precedence more clearly” [component: OData URL Conventions] is Applied.

Note:

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

ODATA–203:
“Specify Operator Precedence more clearly” [component: OData URL Conventions] is Closed with no objections.
6.5.8.4 ODATA–104
ODATA–104:
“Consider supporting nullable complex typed properties” [component: OData URL Conventions] is Applied.

Note:

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

ODATA–104:
“Consider supporting nullable complex typed properties” [component: OData URL Conventions] is Closed with no objections.
6.5.8.5 ODATA–72
ODATA–72:
“Describe any() and all() lambda filter expressions ” [component: OData URL Conventions] is Applied.

Note:

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

ODATA–72:
“Describe any() and all() lambda filter expressions ” [component: OData URL Conventions] is Closed with no objections.
6.5.8.6 ODATA–122
ODATA–122:
“Please clarify the meaning of filter functions applied to DateTimeOffset values” [component: OData URL Conventions] is Applied.

Note:

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

ODATA–122:
“Please clarify the meaning of filter functions applied to DateTimeOffset values” [component: OData URL Conventions] is Closed with no objections.

6.6 Issues in Applied state (carried over from March 7, 2013)

6.6.1 OData CSDL

Stefan:

I move to close ODATA–278, ODATA–242, ODATA–236, ODATA–234, ODATA–173 and ODATA–257 as applied. Ralf seconds.

No further discussion. No objections. The motion passes.

6.6.1.1 ODATA–278
ODATA–278:
“Introduce vocabulary expression edm:Url” [component: OData CSDL] is Applied.

Note:

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

ODATA–278:
“Introduce vocabulary expression edm:Url” [component: OData CSDL] is Closed with no objections.
6.6.1.2 ODATA–242
ODATA–242:
“Allow Path expressions also for annotations targeting an entity container” [component: OData CSDL] is Applied.

Note:

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

ODATA–242:
“Allow Path expressions also for annotations targeting an entity container” [component: OData CSDL] is Closed with no objections.
6.6.1.3 ODATA–236
ODATA–236:
“Define maximum length of namespace names and simple identifiers” [component: OData CSDL] is Applied.

Note:

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

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

Note:

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

ODATA–234:
“Merge Reference and AnnotationReference element” [component: OData CSDL] is Closed with no objections.
6.6.1.5 ODATA–173
ODATA–173:
“Define Action values for OnDelete element” [component: OData CSDL] is Applied.

Note:

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

ODATA–173:
“Define Action values for OnDelete element” [component: OData CSDL] is Closed with no objections.
6.6.1.6 ODATA–257
ODATA–257:
“Define standard client-side function for filling URL templates (RFC6570)” [component: OData CSDL] is Applied.

Note:

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

ODATA–257:
“Define standard client-side function for filling URL templates (RFC6570)” [component: OData CSDL] is Closed with no objections.

6.6.2 OData CSDL, Vocabularies

Stefan:

I move to close ODATA–201, ODATA–43, ODATA–253, ODATA–20, ODATA–200, ODATA–254 and ODATA–252 as applied. John seconds.

No further discussion. No objections. The motion passes.

6.6.2.1 ODATA–201
ODATA–201:
“Allow specifying a list of acceptable media types for media entities and named resource properties” [components: Vocabularies, OData CSDL] is Applied.

Note:

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

ODATA–201:
“Allow specifying a list of acceptable media types for media entities and named resource properties” [components: Vocabularies, OData CSDL] is Closed with no objections.

6.6.3 OData CSDL, OData Protocol, Vocabularies

6.6.3.1 ODATA–43
ODATA–43:
“No indicator for optimistic concurrency control on EntityType or EntitySet level” [components: OData Protocol, OData CSDL, Vocabularies] is Applied.

Note:

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

ODATA–43:
“No indicator for optimistic concurrency control on EntityType or EntitySet level” [components: OData Protocol, OData CSDL, Vocabularies] is Closed with no objections.

6.6.4 OData Protocol, Vocabularies

6.6.4.1 ODATA–253
ODATA–253:
“Clients should be prepared to handle unadvertised properties” [components: Vocabularies, OData Protocol] is Applied.

Note:

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

ODATA–253:
“Clients should be prepared to handle unadvertised properties” [components: Vocabularies, OData Protocol] is Closed with no objections.

6.6.5 OData ATOM Format

6.6.5.1 ODATA–20
ODATA–20:
“Feedback to document revision” [component: OData ATOM Format] is Applied.

Note:

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

ODATA–20:
“Feedback to document revision” [component: OData ATOM Format] is Closed with no objections.
6.6.5.2 ODATA–200
ODATA–200:
“Handling of metadata:type attribute” [component: OData ATOM Format] is Applied.

Note:

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

ODATA–200:
“Handling of metadata:type attribute” [component: OData ATOM Format] is Closed with no objections.
6.6.5.3 ODATA–254
ODATA–254:
“Selection of individual properties in [ATOM] should not include property name” [component: OData ATOM Format] is Applied.

Note:

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

ODATA–254:
“Selection of individual properties in [ATOM] should not include property name” [component: OData ATOM Format] is Closed with no objections.
6.6.5.4 ODATA–252
ODATA–252:
“Clarify ordering of instance annotations in [ATOM] and [JSON]” [component: OData ATOM Format] is Applied.

Note:

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

ODATA–252:
“Clarify ordering of instance annotations in [ATOM] and [JSON]” [component: OData ATOM Format] is Closed with no objections.

6.6.6 OData Protocol

Stefan:

I move to close ODATA–233, ODATA–157, ODATA–121, ODATA–265, ODATA–247 and ODATA–258 as applied. Mike seconds.

No further discussion. No objections. The motion passes.

6.6.6.1 ODATA–233
ODATA–233:
“Change $batch response code from 202 Accepted to 200 OK” [component: OData Protocol] is Applied.

Note:

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

ODATA–233:
“Change $batch response code from 202 Accepted to 200 OK” [component: OData Protocol] is Closed with no objections.
6.6.6.2 ODATA–157
ODATA–157:
“Specify how client correlates requests within a changeset with responses” [component: OData Protocol] is Applied.

Note:

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

ODATA–157:
“Specify how client correlates requests within a changeset with responses” [component: OData Protocol] is Closed with no objections.
6.6.6.3 ODATA–121
ODATA–121:
“Please clarify whether agents handling DateTimeOffset must preserve the UTC offset” [component: OData Protocol] is Applied.

Note:

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

ODATA–121:
“Please clarify whether agents handling DateTimeOffset must preserve the UTC offset” [component: OData Protocol] is Closed with no objections.
6.6.6.4 ODATA–265
ODATA–265:
“Allow omitting key properties from PUT and PATCH request bodies and from nested entities in deep-insert requests” [component: OData Protocol] is Applied.

Note:

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

ODATA–265:
“Allow omitting key properties from PUT and PATCH request bodies and from nested entities in deep-insert requests” [component: OData Protocol] is Closed with no objections.

6.6.7 OData ATOM Format, OData CSDL, OData JSON Format

6.6.7.1 ODATA–258
ODATA–258:
“Advertise function imports in service document” [components: OData CSDL, OData ATOM Format, OData JSON Format] is Applied.

Note:

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

ODATA–258:
“Advertise function imports in service document” [components: OData CSDL, OData ATOM Format, OData JSON Format] is Closed with no objections.

6.6.8 OData ATOM Format, OData JSON Format, OData Protocol

6.6.8.1 ODATA–247
ODATA–247:
“More clearly define extensibility of Formats” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Applied.

Note:

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

ODATA–247:
“More clearly define extensibility of Formats” [components: OData JSON Format, OData ATOM Format, OData Protocol] is Closed with no objections.
6.w.x.y.z End of Issue Processing

All take the opportunity to thank Ralf for the huge amount of work he put into the revisions of the work products he prepared and delivered.

Note:

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

7 Specification Reviews

7.1 Review Request for next weeks

Discussion:

8 Next Meetings

8.1 Next weekly TC meeting will be 2013–03–21 during 8–10am PT.

Agreed.

8.2 TC meeting on 2013–03–28 during 8–10am PT.

Discussion:

9 AOB

None.

Meeting adjourned on 1000 PT

Appendices

List of Open Action Items Before the Meeting

Retrieval time stamp: 2013-03-14 10:15 +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 6. 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.