Here [1] is revision 1 to the draft agenda for the OData TC (Technical Committee) meeting
scheduled on Thursday September 19, 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.
Revision 1 changes:
·
Section 6: Added a discussion item about producing revised Committee Specification
·
Section 7: Grouped issues by components, removed issues for v4.1 and v5.0, and added errata issues in Applied state
Thanks.
[1] Agenda for 2013.09.19 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 September 12, 2013 TC meeting:
https://www.oasis-open.org/committees/download.php/50677/odata-meeting-51_on-20130912-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 Sept 19, 2013
i. None
5.
OData Extension for Data Aggregation [8:16am PT]
a.
Currently in first public review ending 19th September 2013. No public comments yet.
6.
Should we produce a revised Committee Specification to address key errata and technical issues? [8:20 PT]
7.
Process issues [Issues list:
https://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10103] [8:30am PT]
a.
Issues for v4.0_Errata1
i. OData CSDL, OData Protocol
1.
ODATA-491:
Explicitly state that key property values MUST be language-independent [Open]
ii. OData ATOM Format, OData JSON Format
1.
ODATA-473:
Harmonize description of function overload advertisement in Atom and JSON [New]
iii. OData ATOM Format, OData JSON Format, OData Protocol
1.
ODATA-472:
Explicitly state how dynamic properties are represented if they are not defined on an entity [New]
iv. OData ATOM Format, OData CSDL
1.
ODATA-471:
Property names must also be a valid XML Names (NCName) [New]
v. OData URL Conventions
1.
ODATA-515:
Section 5.1.1.9 Operator Precedence: operators use wrong capitalization in precedence table
[New]
2.
ODATA-514:
Example 44: compare Price to a number instead of a string
[New]
3.
ODATA-492:
Add example for „has" operator to section 5.1.1.1.10 [Open]
4.
ODATA-477:
Clarify that dynamic properties can be used in all system query options [New]
5.
ODATA-476:
Clarify that type-cast segments are NOT required for properties of derived types in system query options [New]
6.
ODATA-493:
Capabilities vocabulary: add term for SearchRestrictions [Open]
7.
ODATA-475:
Document that the value "%" is used for annotating percentages with Measures.Unit [New]
vi. OData CSDL
1.
ODATA-513:
Special handling of derived types in the dynamic _expression_ edm:Record. Why?
[New]
2.
ODATA-512:
14.5.14: add example for specifying a value for a navigation property in a <Record> _expression_
[New]
vii. OData JSON Format
1.
ODATA-508:
Delete leftover "respectively" from 6th paragraph of [JSON] Section 5, Service Document
[New]
2.
ODATA-487:
Clarify where relative URLs follow the rules in section 4.3 and where they follow different rules [Open]
viii. OData Protocol
1.
ODATA-507:
Editorial; text appears twice in section 11.2.6 of [Protocol]
[New]
2.
ODATA-490:
Clarify Referential Constraints have UpdateRule=Cascade semantics [Open]
3.
ODATA-478:
Clarify format for values of Content-ID header in $batch parts [New]
4.
ODATA-474:
Add example for POST/PUT/PATCH/DELETE on function result [New]
5.
ODATA-470:
Clarify behavior of /$value requests to properties of type Edm.Binary or Edm.Geo* [New]
ix. OData ABNF Construction Rules
1.
ODATA-503:
Error in ABNF grammer: Edm prefix required for built-in primitive types
[New]
x. OData ATOM Format, OData Protocol
1.
ODATA-502:
Fix use of hash (#) for category term attribute in Atom
[New]
b.
v4.0_Errata1 issues in Applied state
i. OData ABNF Construction Rules
1.
ODATA-506:
Rule day does not allow the values 10 and 20
2.
ODATA-504:
Comment in line 456 should refer to rule lambdaVariableExpr
ii. OData CSDL
1.
ODATA-511:
13.6 and 13.6.2: "bound" should hyperlink to section 12.2.3 instead of 12.1.3
2.
ODATA-510:
Example 78: replace IsBindable with IsBound
3.
ODATA-509:
14.1: Superfluous period at end of second sentence
4.
ODATA-499:
7.1.3 Nullable should refer to NavigationProperty, not Property
5.
ODATA-495:
Clarify that Edm.Double and Edm.Single are 64-bit and 32-bit IEEE754 floating-point numbers
6.
ODATA-489:
Clarify wording for OnDelete
7.
ODATA-488:
Restrict values of edm:Bool in edm.xsd to lower-case "true" and "false"
8.
ODATA-486:
Missing <Record> wrapper in three examples
9.
ODATA-485:
Add example for UrlRef _expression_ that contains a literal string that is a URL
10.
ODATA-484:
Remove reference to "fixed-length or variable-length" primitive values
11.
ODATA-469:
Type of Extends attribute in edm.xsd must be TQualifiedName instead of TSimpleIdentifier
8.
Next meeting [8:58am PT]
a.
September 26, 2013 during 8-9am PT?
9.
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/49178/TC%20Timeline%205.htm