Hi Ram,
I propose the following issue grouping (triggered by Stefan’s mail):
7.a/b/c:
·
CSDL: 5, 58, 74 – approve edit
·
URL: 81, 82, 83 – approve edit
·
Rejected edits: 65, 92, 113 – approve edit so far and accept corrections proposed in comments as resolution for next edit
7.e:
·
ABNF: 114, 115, 116, 117
·
EDMX: 88, 125
·
CSDL: 75, 76, 85, 86, 87, 95, 106
·
JSON: 89, 93, 98, 99, 101, 102
Thanks in advance!
--Ralf
From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org]
On Behalf Of Ram Jeyaraman (MS OPEN TECH)
Sent: Wednesday, 19. September 2012 02:17
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting 2012.09.20
Here [1] is an agenda for the OData TC (Technical Committee) meeting
scheduled on Thursday September 20, 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.09.20 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 13, 2012 TC meeting:
https://www.oasis-open.org/apps/org/workgroup/odata/download.php/46944/odata_meeting-7_on-20120913_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 Sept 20, 2012
i. None
-
Action items NOT due by Sept 20, 2012 but MAY be ready for closure
i. Any?
5.
Next F2F? [8:20am PT]
- The week of Nov 5-9, 2012 has emerged as the preferred week for the next F2F. E-ballot results:
https://www.oasis-open.org/apps/org/workgroup/odata/ballot.php?id=2278.
- Confirm host for the next F2F
- Confirm venue and dates
- Specification organization
[8:25am PT]
- Proposal:
https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201209/msg00174.html
- Process issues [Issues list:
https://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10103] [8:30am PT]
a.
Applied resolutions
i. ODATA-39:
Make use of additional HTTP response code 428 Precondition Required defined in RFC6585
ii. ODATA-35:
10.2.3.2: replace "open properties" with "dynamic properties" in first sentence, mention them in "*" context
iii. ODATA-30:
Section 8.5.1 says "returns 404 No Content": must be "returns 204 No Content"
iv. ODATA-23:
Remove "MERGE", use "PATCH" instead
v. ODATA-22:
Issues with Prefer header
vi. ODATA-17:
Define which DataServiceVersion this specification defines: 3.0 or 4.0
vii. ODATA-5:
Allow Collection(ComplexType) and Collection(PrimitiveType) for Type attribute of ValueTerm
viii. ODATA-81:
Rewrite section 3 Service Root URL for clarity and readability
ix. ODATA-82:
Rewording of 4 Resource Path first paragraph
x. ODATA-83:
Rewording of 4 Resource Path second paragraph for clarity and readability
b.
Applied resolutions that may need further discussion
i. ODATA-65:
Remove the edm:Mode attribute
ii. ODATA-58: Informative
XSD for "metadata:" attributes (HasStream, DataServiceVersion, IsDefaultEntityContainer)
iii. ODATA-92:
3.1.1.2: specify behavior if action overloads exist
iv. ODATA-69:
Enumeration types missing in ABNF
v. ODATA-74:
Explicitly mention dynamic navigation properties
c.
Issues moved from New or Open to Applied since September 13, 2012
i. ODATA-113:
Remove legacy service operations from URL conventions and ABNF
ii. ODATA-66:
10.1 Collection Types: enumeration types are missing from list of types usable with attribute notation
d.
Issues in Open and Proposed state
i. ODATA-57:
Remove xs:any and xs:anyAttribute from Informative XSD
e.
Issues in New and Proposed state
i. ODATA-75:
Schemas can span across more than one CSDL document
ii. ODATA-76:
Edm.Decimal is a floating-point type
iii. ODATA-78:
Allow $select to project parts of complex properties
iv. ODATA-79:
PATCH for properties of complex properties
v. ODATA-80:
Add ABNF rules for requests and responses in JSON
vi. ODATA-85:
Move section 19 Informative XSD for CSDL into separate XML (text) file
vii. ODATA-86:
Allow TypeAnnotation only to target entity types and complex types
viii. ODATA-87:
Consider rewording 1 Introduction, second paragraph
ix. ODATA-88:
The term EDMX wrapper should be explicitly declared once.
x. ODATA-89:
Add normative reference to JSON definition
xi. ODATA-91:
2.1: explicitly state which format the server will return in response to each given set of headers
xii. ODATA-95:
ValueTerms should support a default value
xiii. ODATA-97:
10.4.2.4 Action Overload Resolution: resolution is done by binding parameter type
xiv. ODATA-98:
3.8 Representing Annotations: avoid the undefined terms "internally" and "externally"
xv. ODATA-99:
3.9 Advertisement for a Function or Action: add example and refer to ABNF rules
xvi. ODATA-101:
5.3 Representing a Property in a Response: the object wrapper should be named "d"
xvii. ODATA-102:
5.4.1/2 Representing Actions/Functions Bound to Multiple Entities: add examples
xviii. ODATA-106:
ValueTerms should support primitive types, complex types, and collections, but not entitytypes or collections of entitytypes
xix. ODATA-112:
DateTime[Offset]: allow 24:00[:00] in time part
xx. ODATA-114:
Allow /$count path suffix also for collection properties
xxi. ODATA-115:
Inconsistent use of WSP in system query options
xxii. ODATA-116:
ABNF rule for parameter alias
xxiii. ODATA-117:
Case-sensitivity of system query options
xxiv. ODATA-118:
XSD references Microsoft namespaces edm/annotation and codegeneration
xxv. ODATA-119:
Allow definition of "simple" types that fix values for facet attributes of primitive types
xxvi. ODATA-32:
Allow filtering of expanded to-many navigation properties
- Timeline and next steps [8:50am PT]
- Let’s review the projected timeline [3].
9.
Next meeting [8:56am PT]
-
Thursday September 27, 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
Based on the number of issues (120) and the time (roughly one month) it has taken to resolve about 30 issues, it seems that it would take at least another 3-4 months to process all remaining issues, including other issues that may be filed
in due course. Here is a rough draft of a timeline for producing the Committee Specification Draft 01 (CSD01) version of the OData core specifications:
·
October 20, 2012 (about 2 weeks before the next F2F in November)
o
TC completes end-to-end review of the specs and files away any remaining issues
·
Week of Nov 5-9, 2012
o
2nd F2F meeting (details TBD)
o
Discuss proposals and resolve issues
·
January 17, 2013
o
Committee Specification Draft 01 (CSD01) of core specifications reflecting disposition of all the issues
·
February 5-7, 2013 (tentative)
o
3rd F2F meeting? (details TBD)
o
Discuss and resolve any remaining issues
o
Take steps towards public review
o
Make progress on extension specifications
The timeline for OData extension specifications is TBD.