I would like to add OData-532 and OData-533 to the list of topics to discuss.
Note ODATA-479, ODATA-480, ODATA-482, and ODATA-516
target ODATA 4.1, and should be moved out of the agenda for this week.
Also, the titles of ODATA-491, ODATA-476, ODATA_497, have changed to reflect updated proposals.
Finally, I would propose we move ODATA-466 earlier in the agenda.
I have marked the agenda  below with the proposed changes.
From: email@example.com [mailto:firstname.lastname@example.org]
On Behalf Of Ram Jeyaraman (MS OPEN TECH)
Sent: Wednesday, September 25, 2013 5:53 PM
Subject: [odata] [Revision 1] Agenda for OData TC meeting 2013.09.26
Here  is revision 1 to the draft agenda for the OData TC (Technical Committee) meeting
scheduled on Thursday September 26, 2013 during 8-10am PT.
For additional information, such as dial-in details and chat room, refer to . For TC timeline, see . Feel free to suggest additions or modifications.
Revision 1 changes:
Section 5: Added discussion item relating to Barbara’s resignation as TC co-Chair
Section 6: Added ODATA-528, ODATA-530, and ODATA-531, and removed some duplicates
Section 7: Added discussion on revised TC timeline and immediate next steps
 Agenda for 2013.09.26 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 19, 2013 TC meeting:
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 Sept 26, 2013
Barbara’s resignation as TC co-Chair (ref:
https://lists.oasis-open.org/archives/odata/201309/msg00200.html) [8:20am PT]
Our sincere thanks to Barbara for leading this TC and for getting us to where we are today!
Let’s discuss the next steps for filling the co-Chair role and the election process.
Process issues [Issues list:
https://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10103] [8:30am PT]
Issues for v4.0_CS02 in New or Open state
i. OData CSDL, OData Protocol
Language-dependency of key property values [Open]
ii. OData ATOM Format, OData JSON Format, OData Protocol
Explicitly state how dynamic properties are represented if they are not defined on an entity [Open]
Define server-driven paging for collection-valued resources
iii. OData URL Conventions
Clarify that type-cast segments are required for properties of derived types in system query options [Open]
iv. OData ABNF Construction Rules, OData Protocol
properties in [propertyList] of context URL may be qualified with type
Remove typed null literals
$entity should require cast segment in order to apply $select/$expand
v. OData ABNF Construction Rules, OData URL Conventions
Remove type prefix and single quotes for URL literals of types Date, DateTimeOffset, Guid, and TimeOfDay
vi. OData ATOM Format, Vocabularies
Remove Org.OData.Atom vocabulary
vii. OData ATOM Format, OData CSDL, OData JSON Format, OData Protocol
Relative URLs in OData and the ability to put OData services behind an HTTP proxy
Clarify whether collections can contain null values
viii. OData CSDL
Special handling of derived types in the dynamic _expression_ edm:Record. Why?
Add super type Edm.AnyPath for Edm.PropertyPath, Edm.NavigationPropertyPath, and Edm.AnnotationPath
Use NavProp@<annotation-name> to reference annotations applied to a NavProp
Remove ReturnType attribute from Action and Function element
Allow NavigationPropertyPath and PropertyPath expressions to end in annotations of appropriate type
Annotation/Navigation/Path expressions: allow paths to continue after multi-valued navigation to e.g. drill into complex properties
Require function/action overloads to differ by ordered set of parameter types
ODATA-533: Restrict key property aliases to key properties nested in complex properties
ix. OData JSON Format
Instance annotations should be prefixed with "@"
x. OData Protocol
Allow Content-ID referencing in request bodies for inserting links to newly created entities
$batch: remove restriction "within the same change set " for Content-ID referencing
Clarify format for values of Content-ID header in $batch parts [Open]
How do clients construct links from the context url for complex types?
Clarify Referential Constraints have UpdateRule=Cascade semantics [Open]
xi. OData ATOM Format, OData JSON Format, OData CSDL, OData URL Conventions
Edm.Binary should be base64-encoded (as with OData V3), not base16-encoded (as per current ABNF) [Open]
Allow specifying support for cross-joins
Navigable capability term should apply to entityset, not navigationproperty directly
Simplify OptimisticConcurrency in Core vocabulary
xiii. OData ATOM Format, OData CSDL, OData JSON Format, OData Protocol, OData URL Conventions
Include all section levels in table of contents, provide anchors for all document sections
xiv. OData ATOM Format, OData JSON Format, OData Protocol, OData URL Conventions
Allow inlining stream properties
v4.0_CS02 issues in Applied state
Clarify that the has operator returns null if either operand is null.
Section 188.8.131.52 Operator Precedence: operators use wrong capitalization in precedence table
Example 44: compare Price to a number instead of a string
14.5.14: add example for specifying a value for a navigation property in a <Record> _expression_
Delete leftover "respectively" from 6th paragraph of [JSON] Section 5, Service Document
Editorial; text appears twice in section 11.2.6 of [Protocol]
Error in ABNF grammar: Edm prefix required for built-in primitive types
Fix use of hash (#) for category term attribute in Atom
has operator is missing from the operator precedence table
Error with m:type in Example 31 of Atom
Adapt outdated action/function overload resolution rules in Part 1 to current rules in Part 3
Capabilities vocabulary: add term for SearchRestrictions
Add example for „has" operator to section 184.108.40.206.10
Clarify that dynamic properties can be used in all system query options
Document that the value "%" is used for annotating percentages with Measures.Unit
Harmonize description of function overload advertisement in Atom and JSON
Property names must also be a valid XML Names (NCName)
Clarify behavior of /$value requests to properties of type Edm.Binary or Edm.Geo*
Define explicit concepts in ABNF for referenced sets of rules
Review revised TC timeline (see  below) and immediate next steps [9:50am PT]
Oct 1st, 2013: Do we need an additional meeting on Tuesday next week to address any remaining issues for v4.0_CS02?
Oct 3rd, 2013: Approve CSD03?
Oct 10-24, 2013: 3rd public review?
Next meeting [9:55am PT]
October 3, 2013 during 8-10am PT?
AOB and wrap up [9:58am PT]
Conference call details: