OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [Revision 1] Agenda for OData TC meeting 2013.05.30

Here [1] is revision 1 of the draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday May 30, 2013 during 8-10am PT. For additional information, such as dial-in details and chat room, refer to [2]. For TC timeline, see [3].


Revision 1 changes:

·         Added more issues to section 6b per suggestion from Ralf.


Feel free to suggest additions or modifications.


[1] Agenda for 2013.05.30 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 May 23, 2013 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/49325/odata-meeting-38_on-20130523-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 May 30, 2013

                                                         i.            None

b.      Action items NOT due by May 30, 2013 but MAY be ready for closure

                                                         i.            Any?


5.       Preparing towards Committee Specification Draft 02

a.       Reminder – as discussed earlier, please file significant technical issues by June 2nd.


6.       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 Proposed state (may need deeper discussion) (carried over from May 9, 2013)

                                                         i.            OData Protocol

1.       ODATA-262: Specify how OData services can be protected against cross-site request forgery (CSRF or XSRF) [Open]

                                                       ii.            OData Protocol, OData URL Conventions

1.       ODATA-314: CLONE - Please clarify the meaning of filter functions applied to DateTimeOffset values [Open]

                                                      iii.            OData JSON Format

1.       ODATA-316: Allow omitting properties with null or default values from responses [Open]


b.      Issues in Proposed state since May 23, 2013

                                                         i.            Vocabularies

1.       ODATA-410: Consider moving terms OptimisticConcurrencyControl and AcceptableMediaTypes from Core to Capabilities

                                                       ii.            OData CSDL

1.       ODATA-411: Reconsider placement and semantics of OnDelete element

2.       ODATA-418 EntitySet attribute or NavigationPropertyBinding child elements for Named Entities (edm:Entity)

3.       ODATA-287: Consider adding a primitive type that corresponds with JSR 310 (JDK 1.8 time API) ZonedDateTime

4.       ODATA-220: Please consider the restoration of DateTime (without offset)

                                                      iii.            OData ATOM Format, OData JSON Format, OData Protocol

1.       ODATA-412: Consistent representation of empty values

2.       ODATA-422: Add metadata URL to representations of entity references, define format for collections of references

                                                     iv.            OData ABNF Construction Rules, OData Protocol, OData URL Conventions

1.       ODATA-414: Fix syntax for deleting links to support containment

                                                       v.            OData Protocol

1.       ODATA-420 Response codes 404 and 405: MUST instead of SHOULD

                                                     vi.            OData ATOM Format, OData JSON Format, OData URL Conventions

1.       ODATA-417 Define content negotiation and default format for paths ending in /$value, /$count, /$metadata and /$batch

                                                    vii.            OData JSON Format, OData Protocol

1.       ODATA-421 Remove odata.kind from JSON and add metadata URL templates for link, deletedLink, and deletedEntity

                                                  viii.            OData CSDL, OData URL Conventions

1.       ODATA-413: Replace conformance clauses in URL and CSDL with references to Protocol


c.       Issues in Applied state

1.       ODATA-401: Replace "substringof" canonical function with "contains"

2.       ODATA-400: Allow JSON values also in common expressions, not only in parameter aliases

3.       ODATA-398: Define canonical function as a path segment that allows retrieving an entity by its id

4.       ODATA-394: ODATA-228
https://tools.oasis-open.org/issues/images/icons/link_out_bot.gifIntroduce path segment /$all for search on service and entity container level

5.       ODATA-393: ODATA-375
https://tools.oasis-open.org/issues/images/icons/link_out_bot.gifAllow querying collections of primitive type instances similar to other collections

6.       ODATA-165: Support Cross-joins

7.       ODATA-407: Navigation Properties in Complex Types (public comment c201305e00012)

8.       ODATA-389: JSON: use odata.kind values "Entity" and "deletedEntity", Atom: use metadata:link and metadata:deleted-link

9.       ODATA-388: Remove "when" from OData-specific items in delta responses

10.   ODATA-384: Normative text needs to be typographically distinct from examples

11.   ODATA-383: Number all examples in all documents

12.   ODATA-380: Insert a section in protocol (and similar in JSON and ATOM) named 'Security Considerations' (before 'Conformance')

13.   ODATA-379: Ensure consistency and clear description in specification of $count for 'Delta Responses' (public comment c201305e00000)

14.   ODATA-378: Support relative IRIs for ids in JSON

15.   ODATA-351: Define ID, ReadLink and EditLink in Part 1: Protocol, define representation in Atom and JSON

16.   ODATA-346: Order of child elements of <edm:Collection> MUST be preserved

17.   ODATA-153: Atom: Add examples for all request and response types using a consistent sample OData service

18.   ODATA-102: Representing Actions/Functions Bound to Multiple Entities

19.   ODATA-406: Attribute ContainsTarget (public comment c201305e00009)

20.   ODATA-397: Lazy loading of Annotations: Add optional Attribute "TargetNamespace" to edmx:IncludeAnnotations element

21.   ODATA-396: Partner attribute of edm:NavigationProperty is a property path, not a SimpleIdentifier

22.   ODATA-395: Simplify rule for implicit values of enumeration members

23.   ODATA-387: Replace (at least) the second example in Section 13 of the CSDL document (public comment c201305e00002)

24.   ODATA-373: Add boolean expressions that can be used in <edm:If>

25.   ODATA-370: Disallow Nullable facet for collection-valued properties

26.   ODATA-365: Rename edm:AssertType to edm:Cast and clarify behavior of edm:Cast and cast()

27.   ODATA-364: Explicitly state that the restriction that a property MUST NOT have the same name as its containing type only applies to directly declared properties

28.   ODATA-126: Metadata as an OData service

29.   ODATA-390: Additional description of use of GeoJSON in OData JSON.

30.   ODATA-376: Navigation link representation for navigation properties of complex type instances

31.   ODATA-152: JSON: Add examples for all request and response types using a consistent sample OData service

32.   ODATA-409: conflicts with conformance for intermediate and advanced OData

33.   ODATA-408: 11.2.3 OData services MAY/SHOULD/MUST expose their data model

34.   ODATA-403: Mechanism to advertise conformance level of OData services

35.   ODATA-402: Require services to support $expand on navigation properties

36.   ODATA-399: Describe expected life cycle management of next-links inside Server-Driven Paging

37.   ODATA-385: Overview wording suggestion

38.   ODATA-371: Clearly describe behavior of PUT for structural and navigation properties

39.   ODATA-369: POST to navigation link with binding information leading to a different "parent" is invalid

40.   ODATA-368: Deep insert: if server responds with 201 Created it MUST respond with at least the expansion depth of the insert operation

41.   ODATA-367: Explicitly state that server MAY expand results beyond what's requested with $expand

42.   ODATA-366: Clarify whether server-generated properties can be omitted in POST, even if they are not nullable

43.   ODATA-295: Services should be able to "advertise" what form of change tracking they support

44.   ODATA-290: Check the use of SHOULD vs. MUST in Protocol spec

45.   ODATA-392: Expanded Navigation Properties should be implicitly added to $select

46.   ODATA-375: Allow querying collections of complex type instances similar to querying collections of entities

47.   ODATA-404: Make Capabilities vocabulary a part of OData 4.0


6.       Next meetings [9:58am PT]

a.       June 6, 2013 8-10am PT?

b.      June 13-14, 2013 5th face-to-face TC meeting Redmond, WA: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=34201


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/49178/TC%20Timeline%205.htm  


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]