Update: Agenda for OData TC meeting 2013.05.23

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting
scheduled on Thursday May 23, 2013 during 8-10am PT.
For additional information, such as dial-in details and chat room, refer to [2]. For TC timeline, see [3]. Feel free to suggest additions or modifications.

 

Thanks.

 

[1] 
Agenda for 2013.05.23 OData TC meeting

1.      
Roll call [8:00am PT]

 

2.      
Approve agenda [8:05am PT]

 

3.      
Approve minutes from previous meeting(s) [8:10am PT]

a.      
Minutes from May 16, 2013 TC meeting:

https://www.oasis-open.org/apps/org/workgroup/odata/download.php/49212/odata-meeting-37_on-20130516-minutes.html

 

4.      
Review action items [Action item list:

https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]

a.      
Action items due by May 23, 2013

                                                              
i.      None

b.     
Action items NOT due by May 23, 2013 but MAY be ready for closure

                                                              
i.      Any?

 

5.      
Process issues [Issues list:

https://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10103] [8:20am PT]

a.      
 Issues in Proposed state (carried over from 
May 16, 2013)

1.      
ODATA-391
Add query function defined(PropertyPath) to determine whether an instance has a property of that name

2.      
ODATA-394 Introduce path segment /$all for search on service and entity
 container level

3.      
ODATA-395 Simplify rule for implicit values of enumeration members

 

b.     
Editorial issues (carried over from 
May 16, 2013)

1.      
ODATA-386
odata-v4.0-csprd01-part1-protocol, 3 Data Model, appears to be an unnumbered list of definitions, with annotations
 defined in a separate subsection - suggest new format, etc.

2.      
ODATA-385
Overview wording suggestion

3.      
ODATA-384
Normative text needs to be typographically distinct from examples

4.      
ODATA-383
Examples, distinguishing from normative text

5.      
ODATA-382
Conformance clauses need to refer to sections defining aspects of conformance and do so uniformly

6.      
 ODATA-381
Hanging paragraphs - all current csprd01 documents

 

c.      
Issues in Proposed state (may need deeper discussion) (carried over from May 9, 2013)

                                                              
i.      OData Protocol

1.      
ODATA-262:
Specify how OData services can be protected against cross-site request forgery (CSRF or XSRF) [Open]

                                                            
ii.      OData Protocol, OData URL Conventions

1.      
ODATA-314:
CLONE - Please clarify the meaning of filter functions applied to DateTimeOffset values [Open]

                                                           
iii.      OData CSDL, OData Protocol, OData URL Conventions

1.      
ODATA-126:
Metadata as an OData service [Open]

                                                          
iv.      OData JSON Format

1.      
ODATA-316:
Allow omitting properties with null or default values from responses [Open]

                                                            
v.      OData CSDL

1.      
ODATA-295:
Services should be able to "advertise" what form of change tracking they support [New]

 

d.     
Issues in Proposed State since May 16, 2013

                                                              
i.      OData ABNF Construction Rules OData Protocol OData URL Conventions

1.      
ODATA-398
Define "GetByID" canonical function as a path segment

                                                            
ii.      OData CSDL

1.      
 ODATA-397
Lazy loading of Annotations: Add optional Attribute "TargetNamespace" to edmx:IncludeAnnotations element

                                                           
iii.      OData CSDL OData Protocol

1.      
ODATA-374
Returning heterogeneous types for a function call

 

e.     
Issues in Applied state

                                                              
i.      OData ABNF
Construction Rules OData URL Conventions

1.      
ODATA-393: Allow querying collections of primitive type
 instances similar to other collections

                                                            
ii.      OData ATOM Format OData CSDL OData JSON Format OData Protocol

1.      
ODATA-346: Order of child elements of <edm:Collection> MUST be preserved

                                                           
iii.      OData ATOM Format OData JSON Format OData Protocol

1.      
ODATA-351: Define ID, ReadLink and EditLink in Part 1: Protocol, define representation in Atom and JSON

2.      
ODATA-379: Ensure consistency and clear description in specification of $count for 'Delta Responses' (public comment c201305e00000)

3.      
ODATA-380: Insert a section in protocol (and similar in JSON and ATOM) named 'Security Considerations' (before 'Conformance')

                                                          
iv.      OData ATOM Format OData JSON Format

1.      
ODATA-389
JSON: use odata.kind values "Entity" and "deletedEntity", Atom: use metadata:link and metadata:deleted-link

2.      
ODATA-378
Support relative IRIs for ids in JSON

3.      
ODATA-102
Representing Actions/Functions Bound to Multiple Entities

4.      
ODATA-388: Remove "when" from OData-specific items in delta
 responses

                                                            
v.      OData CSDL

1.      
ODATA-373
Add boolean expressions that can be used in <edm:If>

2.      
ODATA-370
Disallow Nullable facet for collection-valued properties

3.      
ODATA-364: Explicitly state that the restriction that a
 property MUST NOT have the same name as its containing type only applies to directly declared properties

4.      
ODATA-387: Replace (at least) the second example in Section
 13 of the CSDL document (public comment c201305e00002)

5.      
ODATA-396: Partner attribute of edm:NavigationProperty is
 a property path, not a SimpleIdentifier

                                                          
vi.      OData CSDL OData URL Conventions

1.      
ODATA-365
Rename edm:AssertType to edm:Cast and clarify behavior of edm:Cast and cast()

                                                         
vii.      OData JSON Format

1.      
ODATA-376
Navigation link representation for navigation properties of complex type instances

2.      
ODATA-152
JSON: Add examples for all request and response types using a consistent sample OData service

3.      
ODATA-390: Additional description of use of GeoJSON in OData
 JSON.

                                                       
viii.      OData Protocol

1.      
ODATA-371
Clearly describe behavior of PUT for structural and navigation properties

2.      
ODATA-369
POST to navigation link with binding information leading to a different "parent" is invalid

3.      
ODATA-368
Deep insert: if server responds with 201 Created it MUST respond with at least the expansion depth of the insert operation

4.      
ODATA-367
Explicitly state that server MAY expand results beyond what's requested with $expand

5.      
ODATA-366
Clarify whether server-generated properties can be omitted in POST, even if they are not nullable

                                                          
ix.      OData URL Conventions

1.      
ODATA-375
Allow querying collections of complex type instances similar to querying collections of entities

2.      
ODATA-392: Expanded Navigation Properties should be implicitly
 added to $select

 

6.      
Next meeting [8:58am PT]

a.      
May 30, 2013 during 8-10am PT

 

7.      
AOB and wrap up [8:59am PT]

 

[2] 
References

·        
Conference call details:

https://www.oasis-open.org/apps/org/workgroup/odata/download.php/46401/TC%20meeting%20dial-in%20details.htm

·        
Chat room:
http://webconf.soaphub.org/conf/room/odatatc

 

[3] Timeline

https://www.oasis-open.org/committees/download.php/48148/TC%20Timeline%203.htm