Agenda for OData TC meeting 2012.10.04

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

 

Thanks.

 

[1] Agenda for 2012.10.04 OData TC meeting

 

Roll call [8:00am PT]

Approve agenda [8:05am PT]

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

Minutes from September 27, 2012 TC meeting:
https://www.oasis-open.org/apps/org/workgroup/odata/download.php/47020/odata_meeting-9_on-20120927_minutes.html
         

 

Review action items [Action item list:

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

Action items due by Oct 4, 2012

                                                              
i.      None

Action items NOT due by Oct 4, 2012 but MAY be ready for closure

                                                              
i.      Any?

5.      
Next F2F [8:20am PT]

We will be meeting F2F during Nov 8-9, 2012 in Littleton, MA. Details are available at

https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=33706. To help with hosting the event, it would be useful to know how many will be attending in person; let’s discuss.

 

Process issues [Issues list:

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

a.      
Applied resolutions

                                                              
i.      ODATA-116:
ABNF rule for parameter alias

                                                            
ii.      ODATA-115:
Inconsistent use of WSP in system query options

                                                          
iii.      ODATA-114:
Allow /$count path suffix also for collection properties

                                                          
iv.      ODATA-106:
ValueTerms should support primitive types, complex types, and collections, but not entitytypes or collections of entitytypes

                                                            
v.      ODATA-101:
5.3 Representing a Property in a Response: the object wrapper should be named "d"

                                                          
vi.      ODATA-98:
3.8 Representing Annotations: avoid the undefined terms "internally" and "externally"

                                                         
vii.      ODATA-78:
Allow $select to project parts of complex properties

                                                       
viii.      ODATA-47:
Consistently format ABNF rules for human readability

                                                          
ix.      ODATA-46:
Inconsistent use of leading and trailing slashes in URI path parts

                                                            
x.      ODATA-45:
Inconsistent use of WSP in many ABNF rules

b.     
Issues in Open and Proposed state

                                                              
i.      ODATA-99:
3.9 Advertisement for a Function or Action: add example and refer to ABNF rules

                                                            
ii.      ODATA-66:
10.1 Collection Types: enumeration types are missing from list of types usable with attribute notation

                                                          
iii.      ODATA-112:
DateTime[Offset]: allow 24:00[:00] in time part [motion pending]

c.      
Issues in New and Proposed state

                                                              
i.      ODATA-102:
5.4.1/2 Representing Actions/Functions Bound to Multiple Entities: add examples

                                                            
ii.      ODATA-117:
Case-sensitivity of system query options

                                                          
iii.      ODATA-118:
XSD references Microsoft namespaces edm/annotation and codegeneration

                                                          
iv.      ODATA-119:
Allow definition of "simple" types that fix values for facet attributes of primitive types

                                                            
v.      ODATA-32:
Allow filtering of expanded to-many navigation properties

                                                          
vi.      ODATA-56:
metadata:IsDefaultEntityContainer is not defined

                                                         
vii.      ODATA-80:
Add ABNF rules for requests and responses in JSON

                                                       
viii.      ODATA-91:
2.1: explicitly state which format the server will return in response to each given set of headers

                                                          
ix.      ODATA-93:
3.4: add introductory paragraph

                                                            
x.      ODATA-125:
XML schema for Edmx wrapper constructs edmx:Edmx and edmx:DataServices

                                                          
xi.      ODATA-36:
Make $expand implicit if navigation properties are mentioned in $select or $aggregate

                                                         
xii.      ODATA-41:
Specify which URL formats are acceptable within $batch, and which to prefer

                                                       
xiii.      ODATA-52:
Section 3.5 Primitive Types list the primitive types, but doesn't define their meaning

                                                       
xiv.      ODATA-61:
Allow complex properties or components of complex properties as parts of a referential constraint

                                                         
xv.      ODATA-77:
Are Edm primitive type names case-insensitive?

                                                       
xvi.      ODATA-99:
3.9 Advertisement for a Function or Action: add example and refer to ABNF rules

                                                     
xvii.      ODATA-103:
5.4.1 Representing Actions Bound to Multiple Entities: specify treatment of action overloads

                                                    
xviii.      ODATA-126:
Metadata as an OData service

                                                       
xix.      ODATA-127:
Whitespace in URLs must be percent-encoded

                                                         
xx.      ODATA-128:
Restrict scheme in OData URIs to http and https

                                                       
xxi.      ODATA-129:
Explicitly mention dynamic navigation properties in [Core]

                                                     
xxii.      ODATA-130:
Describe canonical $metadata and $batch URLs in URL conventions

                                                    
xxiii.      ODATA-131:
Canonical URL for media resources

                                                    
xxiv.      ODATA-133:
Attributes defined on odata elements should be in empty namespace

                                                     
xxv.      ODATA-134:
Multiplicity of FunctionImport ReturnType element

                                                    
xxvi.      ODATA-135:
Instance Annotations in Atom should use metadata:Annotation element

 

Timeline and next steps [8:55am PT]

Let’s review the projected timeline [3].

 

8.      
Next meeting [8:56am PT]

Thursday October 11, 2012 8-9am PT?

AOB and wrap up [8:57am 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

 

Here is a rough draft of a timeline for the OData core specifications:

·      
October 20, 2012

o  
TC completes end-to-end review of the core specifications and files any remaining issues

·      
Nov 8-9, 2012 2nd F2F meeting (Littleton, MA)

o  
Discuss proposals and resolve issues

·      
Committee Specification Draft 01

·      
30-day public review

·      
Committee Specification Draft 02

·      
15-day public review

·      
Committee Specification

·      
Candidate OASIS Standard

·      
60-day public review

·      
OASIS Standard

 

The timeline for the OData extension specifications is TBD.