Here [1] is a draft agenda for the OData TC (Technical Committee) meeting
scheduled on Thursday September 27, 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.27 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 20, 2012 TC meeting:
https://www.oasis-open.org/apps/org/workgroup/odata/download.php/46960/odata_meeting-8_on-20120920_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 27, 2012
i. #0004:
Come up with estimate for first milestone for data aggregation extension [Ralf Handl]
ii. #0005:
Come up with a first milestone for the temporal extension [Andrew Eisenberg]
iii. #0006:
Come up with estimate for first milestone for XML data extension [Andrew Eisenberg]
iv. #0007:
Come up with estimate for first milestone for JSON data extension [Susan Malaika]
-
Action items NOT due by Sept 27, 2012 but MAY be ready for closure
i. Any?
5.
Next F2F [8:20am PT]
- At the previous meeting we confirmed that we will have a 2-day F2F meeting hosted by IBM at Littleton, MA during Nov 8-9, 2012. The exact address of the meeting location will be available
soon. A teleconferencing facility will be available for remote attendees. Any questions?
- Specification organization
[8:25am PT]
- Proposal:
https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201209/msg00197.html
- The TC admin is fine with the above proposal. If there is no objection, let’s approve this proposal.
- 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-113:
Remove legacy service operations from URL conventions and ABNF
ii. ODATA-95:
ValueTerms should support a default value
iii. ODATA-92:
3.1.1.2: specify behavior if action overloads exist
iv. ODATA-89:
Add normative reference to JSON definition
v. ODATA-87:
Consider rewording 1 Introduction, second paragraph
vi. ODATA-86:
Allow TypeAnnotation only to target entity types and complex types
vii. ODATA-75:
Schemas can span across more than one CSDL document
viii. ODATA-74:
Explicitly mention dynamic navigation properties
ix. ODATA-65:
Remove the edm:Mode attribute
b.
Issues in Open and Proposed state
i. ODATA-88:
The term EDMX wrapper should be explicitly declared once. (motion to resolve pending)
c.
Issues in New and Proposed state
i. ODATA-98:
3.8 Representing Annotations: avoid the undefined terms "internally" and "externally"
ii. ODATA-99:
3.9 Advertisement for a Function or Action: add example and refer to ABNF rules
iii. ODATA-101:
5.3 Representing a Property in a Response: the object wrapper should be named "d"
iv. ODATA-102:
5.4.1/2 Representing Actions/Functions Bound to Multiple Entities: add examples
v. ODATA-106:
ValueTerms should support primitive types, complex types, and collections, but not entitytypes or collections of entitytypes
vi. ODATA-112:
DateTime[Offset]: allow 24:00[:00] in time part
vii. ODATA-114:
Allow /$count path suffix also for collection properties
viii. ODATA-115:
Inconsistent use of WSP in system query options
ix. ODATA-116:
ABNF rule for parameter alias
x. ODATA-117:
Case-sensitivity of system query options
xi. ODATA-118:
XSD references Microsoft namespaces edm/annotation and codegeneration
xii. ODATA-119:
Allow definition of "simple" types that fix values for facet attributes of primitive types
xiii. ODATA-32:
Allow filtering of expanded to-many navigation properties
xiv. ODATA-56:
metadata:IsDefaultEntityContainer is not defined
xv. ODATA-80:
Add ABNF rules for requests and responses in JSON
xvi. ODATA-88:
The term EDMX wrapper should be explicitly declared once.
xvii. ODATA-91:
2.1: explicitly state which format the server will return in response to each given set of headers
xviii. ODATA-93:
3.4: add introductory paragraph
xix. ODATA-125:
XML schema for Edmx wrapper constructs edmx:Edmx and edmx:DataServices
- Timeline and next steps [8:53am PT]
- Let’s review the projected timeline [3].
9.
Next meeting [8:56am PT]
-
Thursday October 4, 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
Here is a rough draft of a timeline for the OData core specifications:
·
October 20, 2012
o
TC completes end-to-end review of the core specifications and files any remaining issues
·
Nov 8-9, 2012 2nd F2F meeting (Littleton, MA)
o
Discuss proposals and resolve issues
·
Committee Specification Draft 01
·
30-day public review
·
Committee Specification Draft 02
·
15-day public review
·
Committee Specification
·
Candidate OASIS Standard
·
60-day public review
·
OASIS Standard
The timeline for the OData extension specifications is TBD.