Here [1] is revision 1 of the draft agenda for the OData TC (Technical Committee) meeting
scheduled on *Tuesday* October 1, 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.
*Note:
This is a special one-off meeting of the TC per the TC decision on Sept 26, 2013. Please make an effort to attend. At this meeting, we are aiming to wrap up all open issues targeted for Committee Specification Draft 03.*
Revision 1 changes:
·
Reordered issues in section 5a and added some more issues that are ready for discussion
·
Added ODATA-540 to Applied list of issues in section 5b
Thanks.
[1] Agenda for 2013.10.01 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 26, 2013 TC meeting:
https://www.oasis-open.org/committees/download.php/50840/odata-meeting-53_on-20130926-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 Oct 01, 2013
i. None
5.
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_CS02 in New or Open state
i. OData Protocol
1.
ODATA-490:
Clarify Referential Constraints have UpdateRule=Cascade semantics [Open]
ii. Vocabularies
1.
ODATA-531:
Simplify OptimisticConcurrency in Core vocabulary
2.
ODATA-534:
Tag type definition in Core should have default boolean value = true
iii. OData ATOM Format, OData CSDL, OData JSON Format, OData Protocol
1.
ODATA-527:
Relative URLs in OData and the ability to put OData services behind an HTTP proxy [Open]
iv. OData Protocol
1.
ODATA-523:
How do clients construct links from the context url for complex types? [Open] [Close with no action?]
v. OData CSDL
1.
ODATA-513:
Special handling of derived types in the dynamic _expression_ edm:Record. Why?
[Open]
2.
ODATA-535:
Define specialization for terms [Open]
vi. Any other issues for v4.0_CS02?
1.
ODATA-538 Clarify treatment of odata.type with derived types and odata.context for delta responses for odata.metadata=none
2.
ODATA-539 Delta response encoding is unnecessarily verbose and change type is missing when odata.metadata=none
3.
ODATA-536 Treatment of circular references when using $levels
b.
v4.0_CS02 issues in Applied state
i. ODATA-540:
Explicitly state that the Context URL locates (a specific portion of) the metadata document
ii. ODATA-537:
Ordering of navigationLink and associationLink annotations in JSON
iii. ODATA-533:
Restrict key property aliases to key properties nested in complex properties
iv. ODATA-532:
Clarify whether collections can contain null values
v. ODATA-530:
Navigable capability term should apply to entityset, not navigationproperty directly
vi. ODATA-528:
$entity should require cast segment in order to apply $select/$expand
vii. ODATA-526:
Allow specifying support for cross-joins
viii. ODATA-525:
Remove Org.OData.Atom vocabulary
ix. ODATA-524:
properties in [propertyList] of context URL may be qualified with type
x. ODATA-522:
Clarify that the has operator returns null if either operand is null.
xi. ODATA-521:
Remove typed null literals
xii. ODATA-520:
Instance annotations should be prefixed with "@"
xiii. ODATA-519:
Define server-driven paging for collection-valued resources
xiv. ODATA-518:
Use NavProp@<annotation-name> to reference annotations applied to a NavProp
xv. ODATA-517:
Allow NavigationPropertyPath and PropertyPath expressions to end in annotations of appropriate type
xvi. ODATA-515:
Section 5.1.1.9 Operator Precedence: operators use wrong capitalization in precedence table
xvii. ODATA-514:
Example 44: compare Price to a number instead of a string
xviii. ODATA-512:
14.5.14: add example for specifying a value for a navigation property in a <Record> _expression_
xix. ODATA-508:
Delete leftover "respectively" from 6th paragraph of [JSON] Section 5, Service Document
xx. ODATA-507:
Editorial; text appears twice in section 11.2.6 of [Protocol]
xxi. ODATA-505:
Remove ReturnType attribute from Action and Function element
xxii. ODATA-503:
Error in ABNF grammar: Edm prefix required for built-in primitive types
xxiii. ODATA-502:
Fix use of hash (#) for category term attribute in Atom
xxiv. ODATA-501:
has operator is missing from the operator precedence table
xxv. ODATA-500:
Require function/action overloads to differ by ordered set of parameter types
xxvi. ODATA-498:
Error with m:type in Example 31 of Atom
xxvii. ODATA-497:
Remove type prefix and single quotes for URL literals of types Date, DateTimeOffset, Guid, and TimeOfDay
xxviii. ODATA-496:
Adapt outdated action/function overload resolution rules in Part 1 to current rules in Part 3
xxix. ODATA-493:
Capabilities vocabulary: add term for SearchRestrictions
xxx. ODATA-492:
Add example for „has" operator to section 5.1.1.1.10
xxxi. ODATA-491:
Language-dependency of key property values
xxxii. ODATA-487:
Clarify where relative URLs follow the rules in section 4.3 and where they follow different rules
xxxiii. ODATA-483:
Include all section levels in table of contents, provide anchors for all document sections
xxxiv. ODATA-481:
Annotation/Navigation/Path expressions: allow paths to continue after multi-valued navigation to e.g. drill into complex properties
xxxv. ODATA-478:
Clarify format for values of Content-ID header in $batch parts
xxxvi. ODATA-477:
Clarify that dynamic properties can be used in all system query options
xxxvii. ODATA-476:
Clarify that type-cast segments are required for properties of derived types in system query options
xxxviii. ODATA-475:
Document that the value "%" is used for annotating percentages with Measures.Unit
xxxix. ODATA-474:
Add example for POST/PUT/PATCH/DELETE on function result
xl. ODATA-473:
Harmonize description of function overload advertisement in Atom and JSON
xli. ODATA-472:
Explicitly state how dynamic properties are represented if they are not defined on an entity
xlii. ODATA-471:
Property names must also be a valid XML Names (NCName)
xliii. ODATA-470:
Clarify behavior of /$value requests to properties of type Edm.Binary or Edm.Geo*
xliv. ODATA-468:
Define explicit concepts in ABNF for referenced sets of rules
xlv. ODATA-466:
Edm.Binary should be base64-encoded (as with OData V3), not base16-encoded (as per current ABNF)
6.
Review revised TC timeline (see [3] below) and immediate next steps [9:50am PT]
a.
Oct 3rd, 2013: Approve CSD03?
b.
Oct 10-24, 2013: 3rd public review?
7.
Next meeting [9:55am PT]
a.
Thursday October 3, 2013 during
8-10am PT?
8.
AOB and wrap up [9:58am 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/50823/TC%20Timeline%206.htm