RE: Agenda for OData TC meeting 2013.02.14

To assist in reviewing applied resolutions, it may be useful to note the following:

 

The application of the following issues in Section 5a) Issues in Applied State have previously been reviewed and approved for all
except OData Protocol v1.0:

ODATA-107:
Should OData support a "clock time" (xs:time) datatype?   

ODATA-14:
add Edm.Date to the OData primitive data types

ODATA-13:
A function that returns the current date and time is needed

ODATA-11:
date/time values without explicit time zones need further investigation

ODATA-73:
Retrieve the count of related entities together with the base entity

ODATA-38:
Recursive $expand and $select

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

ODATA-132:
Support /$count in $filter and $orderby

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

ODATA-24:
Simplify how Relationships are expressed in CSDL

 

It may be convenient to group together the following sets of changes:

 

                Model References Changes:

ODATA-193:
Allow function imports to return entities from a different service

ODATA-182:
Define the term "model"

ODATA-181:
Referencing/reusing a model element from a different schema does not require to "include" this schema via a Using element

ODATA-180:
Remove Extends attribute from EntityContainer element

 

                Annotations:

ODATA-226:
Clarify that the root of the Path attribute of a <PropertyValue> element is rooted at the containing entity

ODATA-109:
Define rules for specifying annotations within annotations

ODATA-108:
Define rules for the target of an annotation that supports implicit casting of relationships

ODATA-12:
create a data type for property names

ODATA-231:
Define how to specify enumeration values in annotations

ODATA-229:
Allow annotations to target all model elements

ODATA-227:
Support of symbolic names in annotations

ODATA-217:
property facets in ValueTerm element

ODATA-241:
Consistently require annotations to be placed at the end of the annotated CSDL element

 

The application of the following changes are relatively straight-forward:

ODATA-169:
Representation of named entities in the service document

ODATA-158:
OData ATOM format should require <category> element

ODATA-238:
Restrict values of the Qualifier attribute to QualifiedName values

ODATA-109:
Define rules for specifying annotations within annotations

ODATA-235:
Limit primitive types allowed as key parts to the "sufficiently discrete" types

ODATA-216:
Allow edm:Documentation element in edm:TypeDefinition and edm:Annotations element

ODATA-213:
Allow all dynamic expressions of the appropriate type within edm:Collection expressions

ODATA-197:
Define standard functions for edm:Apply element

ODATA-218:
Remove doubled last paragraph in section 8.5.2 The Preference-Applied Header

ODATA-187:
Need to remove references to associations and associationsets from protocol doc

ODATA-110:
Track Prefer Header in Http

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

ODATA-225:
Define Functions in Schema; reference in Container using FunctionImport.  

 

The following applied changes have more significant impact on the documents:

ODATA-205:
Merge TypeAnnotation and ValueAnnotation into Annotation

ODATA-25:
Support Obtaining Changes (Deltas) from a result.

ODATA-199:
$expand should be allowed to return only ids for already seen objects

ODATA-16:
Define an Edm.AnyType to allow functions to apply to entity sets of any entity type

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

 

 

From:  [mailto:]
On Behalf Of Ram Jeyaraman (MS OPEN TECH)

Sent: Wednesday, February 13, 2013 6:52 PM

To: 

Subject: [odata] Agenda for OData TC meeting 2013.02.14

 

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting
scheduled on Thursday February 14, 2013 during 8-9am 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.02.14 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 February 7, 2013 TC meeting:
https://www.oasis-open.org/committees/download.php/48174/odata-meeting-24_on-20130207-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 Feb 14, 2013

                                                        
i.            #0028:
Introduce fix target versions 4.0, minor and next major into JIRA [owner: Ram Jeyaraman]

b.     
Action items NOT due by Feb 14, 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 Applied state

                                                        
i.            OData ABNF Construction Rules v1.0, OData URL Conventions v1.0

1.      
ODATA-132:
Support /$count in $filter and $orderby

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

                                                      
ii.            OData ABNF Construction Rules v1.0, OData CSDL v1.0, OData URL Conventions v1.0

1.      
ODATA-107:
Should OData support a "clock time" (xs:time) datatype?

                                                     
iii.            OData ATOM Format v1.0, OData JSON Format v1.0

1.      
ODATA-199:
$expand should be allowed to return only ids for already seen objects

2.      
ODATA-169:
Representation of named entities in the service document

                                                    
iv.            OData ATOM Format v1.0

1.      
ODATA-158:
OData ATOM format should require <category> element

                                                      
v.            OData CSDL v1.0

1.      
ODATA-241:
Consistently require annotations to be placed at the end of the annotated CSDL element

2.      
ODATA-238:

ODATA-109: Restrict values of the Qualifier attribute to QualifiedName values

3.      
ODATA-235:
Limit primitive types allowed as key parts to the "sufficiently discrete" types

4.      
ODATA-231:
Define how to specify enumeration values in annotations

5.      
ODATA-229:
Allow annotations to target all model elements

6.      
ODATA-227:
Support of symbolic names in annotations

7.      
ODATA-226:
Clarify that the root of the Path attribute of a <PropertyValue> element is rooted at the containing entity

8.      
ODATA-225:
Define Functions in Schema; reference in Container using FunctionImport.

9.      
ODATA-217:
property facets in ValueTerm element

10.  
ODATA-216:
Allow edm:Documentation element in edm:TypeDefinition and edm:Annotations element

11.  
ODATA-213:
Allow all dynamic expressions of the appropriate type within edm:Collection expressions

12.  
ODATA-205:
Merge TypeAnnotation and ValueAnnotation into Annotation

13.  
ODATA-197:
Define standard functions for edm:Apply element

14.  
ODATA-193:
Allow function imports to return entities from a different service

15.  
ODATA-182:
Define the term "model"

16.  
ODATA-181:
Referencing/reusing a model element from a different schema does not require to "include" this schema via a Using element

17.  
ODATA-180:
Remove Extends attribute from EntityContainer element

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

19.  
ODATA-109:
Define rules for specifying annotations within annotations

20.  
ODATA-108:
Define rules for the target of an annotation that supports implicit casting of relationships

21.  
ODATA-24:
Simplify how Relationships are expressed in CSDL

22.  
ODATA-16:
Define an Edm.AnyType to allow functions to apply to entity sets of any entity type

23.  
ODATA-12:
create a data type for property names

                                                    
vi.            OData CSDL v1.0, OData URL Conventions v1.0

1.      
ODATA-14:
add Edm.Date to the OData primitive data types

2.      
ODATA-11:
date/time values without explicit time zones need further investigation

                                                   
vii.            OData Protocol v1.0

1.      
ODATA-218:
Remove doubled last paragraph in section 8.5.2 The Preference-Applied Header

2.      
ODATA-187:
Need to remove references to associations and associationsets from protocol doc

3.      
ODATA-110:
Track Prefer Header in Http

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

5.      
ODATA-25:
Support Obtaining Changes (Deltas) from a result.

                                                 
viii.            OData URL Conventions v1.0

1.      
ODATA-73:
Retrieve the count of related entities together with the base entity

2.      
ODATA-38:
Recursive $expand and $select

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

4.      
ODATA-13:
A function that returns the current date and time is needed

b.     
Issues in Proposed state (carried over from Feb 7, 2013 TC meeting)

                                                        
i.            OData CSDL v1.0

1.      
ODATA-217:
property facets in ValueTerm element
[New]

2.      
ODATA-202:
Custom Mapping to Atom Elements not defined
[New]

                                                      
ii.            Atom & JSON

1.      
ODATA-212:
Define request body format for Actions in Atom and JSON format specifications
[New]

2.      
ODATA-221:
Flatten the message element in the JSON Error Represention (Section 4.18 Representing Errors in a Response)
[New]

c.      
Issues in Proposed state (since Feb 7, 2013)

                                                        
i.            OData Protocol v1.0

1.      
ODATA-253:
Clients should be prepared to handle unadvertised properties
[New]

2.      
ODATA-247:
More clearly define extensibility of Formats
[New]

3.      
ODATA-255:
Consider adding support for requesting flattened results
[New]

4.      
ODATA-243:
Add client preferences for server-driven paging
[New]

5.      
ODATA-261:
Improve section 10.2.3.8 The $format System Query Option
[New]

                                                      
ii.            OData CSDL v1.0

1.      
ODATA-269:
Separate Functions and Actions
[New]

2.      
ODATA-237:
Require type usage to always specify a qualified name for types other than the built-in primitive types [New]

3.      
ODATA-273:
Clarify whether derived types MUST introduce new properties [New]

4.      
ODATA-268:
Use http://docs.oasis-open.org/odata/ns/edm/4.0 as the EDM namespace URL [New]

5.      
ODATA-272:
FixedLength facet is Boolean [New]

6.      
ODATA-258:
Advertise parameter-less function imports in service document
[New]

7.      
ODATA-76: 
new boolean facet FixedScale or VariableScale to make clients aware of floating point semantics [Open]

                                                     
iii.            OData URL Conventions v1.0

1.      
ODATA-215:
Remove hour(), minute() and second() query functions and add corresponding overloads to the hours(), minutes(), and seconds() functions [New]

2.      
ODATA-122:
Please clarify the meaning of filter functions applied to DateTimeOffset values [New]

                                                    
iv.            OData JSON v1.0

1.      
ODATA-259:
Add Annotation Groups to JSON format
[New]

2.      
ODATA-249:
"Kind" property should be optional for EntitySets in JSON Service Documents
[New]

                                                      
v.            OData ATOM v1.0

1.      
ODATA-250:
For instance annotations in Atom, "Annotation" element, "Type", "Term" and "Target" attributes should be lower case
[New]

2.      
ODATA-251:
Clarify, within [ATOM], that complex types can be annotated
[New]

3.      
ODATA-252:
Clarify ordering of instance annotations in [ATOM] and [JSON] [New]

4.      
ODATA-254:
Selection of individual properties in [ATOM] should not include property name [New]

                                                    
vi.            OData ABNF Construction Rules v1.0, OData URL Conventions v1.0

1.      
ODATA-222:
free-text search within a property
[New]

                                                   
vii.            OData ABNF Construction Rules v1.0, OData Protocol v1.0, OData URL Conventions v1.0

1.      
ODATA-228:
Specify $search for free-text search within a OData Service and specify $search for free-text search within an entityContainer
[New]

 

6.      
Next F2F meeting [8:50am PT]

a.      
Determine location and venue based on poll results

                                                        
i.            Geographic location preference:

https://www.oasis-open.org/apps/org/workgroup/odata/ballot.php?id=2357

                                                      
ii.            Date preferences:

https://www.oasis-open.org/apps/org/workgroup/odata/ballot.php?id=2356 

 

7.      
Next meeting [8:55am PT]

a.      
Feb 21, 2013 during
8-9am PT?

b.     
Extend TC meetings by another ½ hour (to facilitate making progress on issues)?

 

8.      
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