Hi Barbara,
Please add
ODATA-455
Make EntityContainer a Singleton in MetadataService
To topic 5. b.
Thanks in advance!
--Ralf
From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org]
On Behalf Of Hartel, Barbara
Sent: Wednesday, 19. June 2013 19:43
To: Hartel, Barbara; odata@lists.oasis-open.org
Subject: [odata] Update: Agenda for OData TC meeting 2013.06.20
Now with working links. Sorry for the inconvenience.
Best regards, Barbara
----
Here [1] is a draft agenda for the OData TC (Technical Committee) meeting
scheduled on Thursday June 20, 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.
The documents including the applied issues will be available very soon. Please wait for the document update before reviewing the applied issues.
Thanks.
[1] Agenda for 2013.06.20 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 June 13/14, 2013 TC meeting:
https://www.oasis-open.org/apps/org/workgroup/odata/download.php/49557/odata-meeting-41_on-20130613_14-F2F-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 June 20, 2013
i. None
b.
Action items NOT due by June 20, 2013 but MAY be ready for closure
i. Any?
5.
Process issues [Issues list:
https://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10103] [8:20am PT]
a.
Issues in Applied state
1. ODATA-166 Inconsistent lifted operators for $filter, OData URL Conventions
2. ODATA-262 Specify how OData services can be protected against cross-site request forgery (CSRF
or XSRF), Securing Open Data
3. ODATA-289 Callback for notification after async invocation of Create, Update, Delete and Service
Operations, OData Protocol Vocabularies
4. ODATA-291 Consider adding a mechanism for idempotence with POST, Idempotence
5. ODATA-294 Clarifications needed for Filter System Query Option: Operators and Functions, OData
URL Conventions
6. ODATA-314 Please clarify the meaning of filter functions applied to DateTimeOffset values, OData
Protocol OData URL Conventions
7. ODATA-316 Services select a default set of properties in absence of $select, OData Protocol
8. ODATA-317 Allow multiple reads in the same transaction, OData Batch Processing Format
9. ODATA-377 Fix broken links in CSD01 documents, OData ATOM Format OData JSON Format OData Protocol
10. ODATA-381
Hanging paragraphs - all current csprd01 documents, OData ATOM Format OData CSDL OData JSON Format OData Protocol OData URL Conventions
11. ODATA-391
Add query function isdefined(PropertyPath) to determine whether an instance has a property of that name, OData Extension for Data Aggregation
12. ODATA-413
Replace conformance clauses in URL and CSDL with references to Protocol, OData CSDL OData URL Conventions
13. ODATA-416 Non-normative text in conformance 13.1 of part 1, OData Protocol
14. ODATA-419 Specify ETag handling more precisely, OData Protocol
15. ODATA-423 Rename edm:Entity to edm:Singleton, OData ATOM Format OData CSDL OData JSON Format OData
Protocol OData URL Conventions
16. ODATA-425 Clarify rules around parameter overloads and return types, OData ABNF Construction Rules
OData CSDL OData Protocol OData URL Conventions
17. ODATA-426 Metadata URL for nested objects can be relative to metadata URL of enclosing object,
OData JSON Format
18. ODATA-427 Consider Providing More Information For Changed Links In a Delta Response, OData Protocol
19. ODATA-428 Introduce dynamic _expression_ AnnotationPath and accompanying abstract type Edm.AnnotationPath,
OData CSDL
20. ODATA-430 Add term Core.ResourcePath to describe unconventional resource paths in CSDL, OData
CSDL OData URL Conventions Vocabularies
21. ODATA-431 Add $expand=*, $expand=*/$ref, $expand=*($levels=...) for expanding all navigation properties,
OData URL Conventions
22. ODATA-433 Rollback requirement that services support $expand, OData Protocol
23. ODATA-434 Introduce path segment for cross-joins on entity-container level, OData ABNF Construction
Rules OData URL Conventions
24. ODATA-435 Simplify URL syntax and CSDL by restricting services to exactly one entity container,
OData ABNF Construction Rules OData ATOM Format OData CSDL OData JSON Format OData Protocol OData URL Conventions
25. ODATA-436 Allow annotating edm:Annotation element, disallow annotating edm:Collection element,
OData CSDL
26. ODATA-437 Describe path syntax for edm:Annotations/@Target, OData CSDL
27. ODATA-438 Rename edm:Url to edm:UrlRef, OData CSDL
28. ODATA-439 Complete Context URL patterns, OData ABNF Construction Rules OData Protocol
29. ODATA-440 Specify response for function or action that returns a single null value, OData Protocol
30. ODATA-441 Specify canonical form of entity-id, OData Protocol OData URL Conventions
31. ODATA-442 Adapt metadata service, OData CSDL
32. ODATA-443 Last page of delta response MUST contain a delta link, OData Protocol
33. ODATA-444 Representation of entity references, OData ATOM Format OData JSON Format
34. ODATA-445 odata.type relative to odata.type in surrounding entities, OData JSON Format
35. ODATA-446 Rename Named Stream to Stream Property, OData ABNF Construction Rules OData ATOM Format
OData CSDL OData JSON Format OData Protocol OData URL Conventions Vocabularies
36. ODATA-447 Rename Metadata URL to Context, OData ATOM Format
37. ODATA-448 Add Nullable facet to edm:ReturnType, OData CSDL
38. ODATA-449 Clarify restrictions for action/function overloads, rename IsBindable to IsBound, OData
ABNF Construction Rules OData ATOM Format OData CSDL OData JSON Format OData Protocol OData URL Conventions
39. ODATA-450 ordering of association link , navigation link, expanded nav prop, OData ATOM Format
OData JSON Format
40. ODATA-451 Provide section that clearly indicates what system query options are allowed on the
various combinations of URL type and HTTP method (public comment c201306e00012), OData URL Conventions
41. ODATA-452 Services should be allowed to filter changes based on selected fields, OData Protocol
b.
Issues in Proposed state
1. ODATA-453 deal with KEY function, OData ABNF Construction Rules [Open]
2. ODATA-386 odata-v4.0-csprd01-part1-protocol, 3 Data Model, appears to be an unnumbered list
of definitions, with annotations defined in a separate subsection - suggest new format, etc., OData Protocol [Open]
3. ODATA-454 Need a way to specify a property is unavailable, OData ATOM Format OData JSON Format
Vocabularies [New]
6.
Next meeting [9:58am PT]
a.
June 24, 2013 during 12:30-01:30pm PT (extraordinary meeting to approve CSD02)
7.
AOB and wrap up [9: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/48148/TC%20Timeline%203.htm