[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Update: Agenda for OData TC F2F meeting (June 13 and 14, 2013)
Added issue ODATA-423,
ODATA-439, ODATA-440, ODATA-441, ODATA-442, ODATA-443, ODATA-444, ODATA-445. Best regards, Barbara ----- Here [1] is a draft agenda for the OData TC (Technical Committee) f2f meeting
scheduled on June 13/14, 2013 from 9am to 6pm 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.
Thanks. [1] Agenda OData TC F2F, June 2013
Day 1: June 13, 2013
09:00am – 10:30am
·
Roll call
·
Approve minutes from the previous meeting:
https://www.oasis-open.org/apps/org/workgroup/odata/download.php/49447/odata-meeting-40_on-20130606-minutes.html
·
Review agenda and make necessary adjustments
·
Close issues in applied state 10:30am – 10:45am
·
Break 10:45am – 12:00pm
·
Resolve issues 12:00pm – 01:00pm
·
Lunch break 01:00pm – 03:00pm
·
Resolve issues
03:00pm – 03:15pm
·
Break 03:15pm – 6:00pm
·
Resolve issue Issue List for Day 1
Issues in applied state
1.
ODATA-102
Representing Actions/Functions Bound to Multiple Entities, OData ATOM Format OData JSON Format
2.
ODATA-126
Metadata as an OData service, OData CSDL OData Protocol OData URL Conventions
3.
ODATA-152
JSON: Add examples for all request and response types using a consistent sample OData service, OData JSON Format
4.
ODATA-153
Atom: Add examples for all request and response types using a consistent sample OData service, OData ATOM Format
5.
ODATA-165
Support Cross-joins, OData ABNF Construction Rules OData URL Conventions
6.
ODATA-290
Check the use of SHOULD vs. MUST in Protocol spec, OData Protocol
7.
ODATA-295
Services should be able to "advertise" what form of change tracking they support, OData Protocol
8.
ODATA-346
Order of child elements of <edm:Collection> MUST be preserved, OData ATOM Format OData CSDL OData JSON Format OData Protocol
9.
ODATA-351
Define ID, ReadLink and EditLink in Part 1: Protocol, define representation in Atom and JSON, OData ATOM Format OData JSON Format OData Protocol
10.
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,
OData CSDL
11.
ODATA-365
Rename edm:AssertType to edm:Cast and clarify behavior of edm:Cast and cast(), OData CSDL OData URL Conventions
12.
ODATA-366
Clarify whether server-generated properties can be omitted in POST, even if they are not nullable, OData Protocol
13.
ODATA-367
Explicitly state that server MAY expand results beyond what's requested with $expand, OData Protocol
14.
ODATA-368
Deep insert: if server responds with 201 Created it MUST respond with at least the expansion depth of the insert operation, OData Protocol
15.
ODATA-369
POST to navigation link with binding information leading to a different "parent" is invalid, OData Protocol
16.
ODATA-370
Disallow Nullable facet for collection-valued properties, OData CSDL
17.
ODATA-371
Clearly describe behavior of PUT for structural and navigation properties, OData Protocol
18.
ODATA-373
Add boolean expressions that can be used in <edm:If>, OData CSDL
19.
ODATA-375
Allow querying collections of complex type instances similar to querying collections of entities, OData URL Conventions
20.
ODATA-376
Navigation link representation for navigation properties of complex type instances, OData JSON Format
21.
ODATA-378
Support relative IRIs for ids in JSON, OData ATOM Format OData JSON Format
22.
ODATA-380
Insert a section in protocol (and similar in JSON and ATOM) named 'Security Considerations' (before 'Conformance'), OData ATOM Format OData JSON Format
OData Protocol
23.
ODATA-382
Conformance clauses need to refer to sections defining aspects of conformance and do so uniformly, OData ATOM Format OData JSON Format OData Protocol
24.
ODATA-383
Number all examples in all documents, OData ATOM Format OData CSDL OData JSON Format OData Protocol OData URL Conventions
25.
ODATA-384
Normative text needs to be typographically distinct from examples, OData ATOM Format OData CSDL OData JSON Format OData Protocol OData URL Conventions
26.
ODATA-385
Overview wording suggestion, OData Protocol
27.
ODATA-388
Remove "when" from OData-specific items in delta responses, OData ATOM Format OData JSON Format
28.
ODATA-389
JSON: use odata.kind values "Entity" and "deletedEntity", Atom: use metadata:link and metadata:deleted-link, OData ATOM Format OData JSON Format
29.
ODATA-390
Additional description of use of GeoJSON in OData JSON., OData JSON Format
30.
ODATA-392
Expanded Navigation Properties should be implicitly added to $select, OData URL Conventions
31.
ODATA-393
ODATA-375 Allow querying collections of primitive type instances similar to other collections, OData ABNF Construction Rules OData URL Conventions
32.
ODATA-394
ODATA-228 Introduce path segment /$all for search on service and entity container level, OData ABNF Construction Rules OData URL Conventions
33.
ODATA-395
Simplify rule for implicit values of enumeration members, OData CSDL
34.
ODATA-396
Partner attribute of edm:NavigationProperty is a property path, not a SimpleIdentifier, OData CSDL
35.
ODATA-397
Lazy loading of Annotations: Add optional Attribute "TargetNamespace" to edmx:IncludeAnnotations element, OData CSDL
36.
ODATA-398
Define canonical function as a path segment that allows retrieving an entity by its id, OData ABNF Construction Rules OData Protocol OData URL Conventions
37.
ODATA-399
Describe expected life cycle management of next-links inside 11.2.4.7 Server-Driven Paging, OData Protocol
38.
ODATA-400
Allow JSON values also in common expressions, not only in parameter aliases, OData ABNF Construction Rules OData URL Conventions
39.
ODATA-401
Replace "substringof" canonical function with "contains", OData ABNF Construction Rules OData Protocol OData URL Conventions
40.
ODATA-402
Require services to support $expand on navigation properties, OData Protocol
41.
ODATA-403
Mechanism to advertise conformance level of OData services, OData Protocol
42.
ODATA-404
Make Capabilities vocabulary a part of OData 4.0, Vocabularies
43.
ODATA-406
Attribute ContainsTarget (public comment c201305e00009), OData CSDL OData URL Conventions
44.
ODATA-407
Navigation Properties in Complex Types (public comment c201305e00012), OData ATOM Format
45.
ODATA-408
11.2.3 OData services MAY/SHOULD/MUST expose their data model, OData Protocol
46.
ODATA-409
11.3.3.1 conflicts with conformance for intermediate and advanced OData, OData Protocol
47.
ODATA-411
Reconsider placement and semantics of OnDelete element, OData CSDL
48.
ODATA-412
Consistent representation of empty values, OData ATOM Format OData JSON Format OData Protocol
49.
ODATA-414
Fix syntax for deleting links to support containment, OData ABNF Construction Rules OData Protocol OData URL Conventions
50.
ODATA-417
Define content negotiation and default format for paths ending in /$value, /$count, /$metadata and /$batch, OData ATOM Format OData JSON Format OData
URL Conventions
51.
ODATA-418
EntitySet attribute or NavigationPropertyBinding child elements for Named Entities (edm:Entity), OData CSDL
52.
ODATA-420
Response codes 404 and 405: MUST instead of SHOULD, OData Protocol
53.
ODATA-421
Remove odata.kind from JSON and add metadata URL templates for link, deletedLink, and deletedEntity, OData JSON Format OData Protocol
54.
ODATA-422
Add metadata URL to representations of entity references, define format for collections of references, OData ATOM Format OData JSON Format OData Protocol
55.
ODATA-429
Add Boolean property RequiresFilter to Capabilities.FilterRestrictionsType, Vocabularies Issues in proposed state
1.
ODATA-166
Inconsistent lifted operators for $filter, OData Protocol [Open]
2.
ODATA-289
Callback for notification after async invocation of Create, Update, Delete and Service Operations, OData URL Conventions [Open]
3.
ODATA-291
Consider adding a mechanism for idempotence with POST, OData Protocol [New]
4.
ODATA-294
Clarifications needed for Filter System Query Option: Operators and Functions, OData URL Conventions [Open]
5.
ODATA-317
Allow multiple reads in the same transaction, OData Batch Processing Format [Open]
6.
ODATA-333
Visualize high level EDM overview through means of small diagrams to aid the reader on understanding base terms, OData Protocol [New]
7.
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]
8.
ODATA-415
Use of "MUST," "MAY," "SHOULD," etc in Part 3 CSDL definitions, OData CSDL [Open]
9.
ODATA-423: Rename
edm:Entity to edm:Singleton,
OData ATOM Format , OData CSDL,
OData JSON Format, OData Protocol ,
OData URL Conventions
[Open]
10.
ODATA-427
Consider Providing More Information For Changed Links In a Delta Response, OData Protocol [New]
11.
ODATA-428
Introduce dynamic _expression_ AnnotationPath and accompanying abstract type Edm.AnnotationPath, OData CSDL [New]
12.
ODATA-430
Add term Core.ResourcePath to describe unconventional resource paths in CSDL, OData CSDL OData URL Conventions Vocabularies [New]
13.
ODATA-431
Add $expand=*, $expand=*/$ref, $expand=*($levels=...) for expanding all navigation properties, OData URL Conventions [New]
14.
ODATA-432
Define meaning of odata.associationLink on entity level, OData Extension for JSON Data [New]
15.
ODATA-433
Rollback requirement that services support $expand, OData Protocol [New]
16.
ODATA-434
Introduce path segment for cross-joins on entity-container level, OData ABNF Construction Rules OData URL Conventions [New]
17.
ODATA-435
Simplify URL syntax and CSDL by restricting services to exactly one entity container, OData ABNF Construction Rules OData CSDL OData URL Conventions
[New]
18.
ODATA-436
Allow annotating edm:Annotation element, disallow annotating edm:Collection element, OData CSDL [New]
19.
ODATA-437
Describe path syntax for edm:Annotations/@Target, OData CSDL [New]
20.
ODATA-438
Rename edm:Url to edm:UrlExpression [New]
21.
ODATA-439
Complete Metadata URL patterns (was: Metadata URL patterns for ...),
OData ABNF Construction Rules, OData Protocol [New]
22.
ODATA-440
Specify response for function or action that returns a single null value,
OData Protocol [New]
23.
ODATA-441
Specify canonical form of entity-id, OData Protocol ,
OData URL Conventions [New]
24.
ODATA-442
Adapt metadata service, OData CSDL [New]
25.
ODATA-443
Last page of delta response MUST contain a delta link,
OData Protocol
[New]
26.
ODATA-444
Representation of entity references, OData JSON Format [New]
27.
ODATA-445
odata.type relative to odata.type in surrounding entities,
OData JSON Format [New] Day 2: June 14, 2013
09:00am – 10:30am
·
Review agenda and make adjustments
·
Review action items 10:30am – 10:45am
·
Break 10:45am – 12:00pm
·
Specification review 12:00pm – 01:00pm
·
Lunch break 01:00pm – 03:00pm
·
Review next steps towards approving CSD02
·
Timeline and next steps 03:00pm – 03:15pm
·
Break 03:15pm – 6:00pm
·
Next meeting
·
Wrap up
·
AOB [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
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]