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: Re: [odata] Agenda for OData TC meeting 2013.05.02


I suggest to also include the applied ODATA-301 issue in Processing of "all" applied issues in 5.1 and to list it after ODATA-298 and before ODATA-323.

Summary of ODATA-301

"Guidance around data authorization model and secure authenticated access to an OData Service" [component: OData Protocol] is Applied.
Created: 2013-03-18T10:55:21.000Z, Status: Applied, Type: Improvement, Priority: Major, Updated: 2013-04-30T15:54:27.000Z,
Reporter: 'Ralf Handl', Assignee: 'Martin Zurmuehl', Components: (OData Protocol),
CreatedBefore: 'Meeting #30', Version: 'V4.0_CSD01', FixVersion: 'V4.0_CSD01'




Am 30.04.13 09:55, schrieb Hartel, Barbara:
Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday May 02, 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.
 
Thanks.
 
[1] Agenda for 2013.05.02 OData TC meeting
  1. Roll call [8:00am PT]
 
  1. Approve agenda [8:05am PT]
 
  1. Approve minutes from previous meeting(s) [8:10am PT]
  1. Minutes from April 25/26, 2013 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/48960/odata-meeting-34_on-20130425_26-F2F-minutes.html
 
  1. Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]
  1. Action items due by May 02, 2013
  1. None
  1. Action items NOT due by May 02, 2013 but MAY be ready for closure
  1. Any?
 
  1. Process issues [Issues list: https://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10103] [8:20am PT]
  1. Issues in Applied state, editors will give information only for issues where they had problems with applying
  1. ODATA-34 Control verbosity of $metadata response: include annotations or documentation, OData Protocol
  2. ODATA-48 Consistent typographical conventions for OData specifications, OData Extension for JSON Data OData Extension for Temporal Data OData Extension for XML Data
  3. ODATA-144 "Scoping" syntax for $aggregate, OData Extension for Data Aggregation
  4. ODATA-192 Define vocabulary term as a replacement for StoreGeneratedPattern attribute, Vocabularies
  5. ODATA-223 ODATA-224 Specify Service behavior for not implemented functionality, OData ATOM Format OData Batch Processing Format OData CSDL OData Extension for Data Aggregation OData Extension for JSON Data OData Extension for Temporal Data OData Extension for XML Data OData JSON Format OData Protocol OData URL Conventions
  6. ODATA-224 Fill out Capabilities sections of an OData Service, OData ABNF Construction Rules OData ATOM Format OData Batch Processing Format OData CSDL OData Extension for Data Aggregation OData Extension for JSON Data OData Extension for Temporal Data OData Extension for XML Data OData JSON Format OData Protocol OData URL Conventions
  7. ODATA-239 Allowing expressions to be passed as parameters to (super) functions, OData ABNF Construction Rules OData URL Conventions
  8. ODATA-240 Better describe, and possible extend, expected behavior of dealing with async $batch requests, OData Protocol
  9. ODATA-286 Need clarity about JSON encoding of Single and Double (and the applicability or not of ABNF rules) particularly for NaN, INF and –INF, OData JSON Format
  10. ODATA-298 Clarify Requesting Changes to entity sets that include Stream properties, OData Protocol
  11. ODATA-323 InlineCount should just be Boolean, OData ABNF Construction Rules OData Protocol
  12. ODATA-326 include-annotations should allow inclusion (or exclusion) of specific terms, OData Protocol
  13. ODATA-330 Define whether null values come first or last with $orderby asc, OData Protocol
  14. ODATA-331 Ensure that high level grouping expressions like eg. 'create operations' are easily mapped to real actions (HTTP methods, OData expectations), OData Protocol
  15. ODATA-332 Ensure comparability and emphasize differences in directly grokable way for all formats (currently only ATOM and JSON), OData ATOM Format OData Extension for JSON Data
  16. ODATA-334 Integrate conformance concept with careful consideration of versioning semantics (into protocol work product), OData Protocol
  17. ODATA-335 Review results for OData ATOM Format Version 4.0, OData ATOM Format
  18. ODATA-336 Be more generous on accepting values for the $format query option, OData ABNF Construction Rules OData ATOM Format OData JSON Format
  19. ODATA-337 Review results for OData JSON Format Version 4.0, OData JSON Format
  20. ODATA-339 $inlinecount and $count, do we need both? Could we use $count in select clause as well?, OData ABNF Construction Rules OData Protocol
  21. ODATA-340 How to retrieve both the entity references as well as the count of a collection referenced by a navigation property?, OData Protocol
  22. ODATA-341 Can we get rid of the optional trailing 'L'/'l' for int64 numbers, OData ABNF Construction Rules
  23. ODATA-342 Can we relax the requirement of int64 numbers being represented as strings in the JSON Format for integer numbers that don't lose precision in ECMAScript when represented as numbers?, OData JSON Format
  24. ODATA-343 Ensure consistent placement and delegation of descritions for presentations of primitive values, OData ABNF Construction Rules OData ATOM Format OData CSDL OData JSON Format
  25. ODATA-345 Specify which nested query options can be used when expanding only references, and adapt syntax, OData ABNF Construction Rules OData Protocol OData URL Conventions
  26. ODATA-347 RFC and W3C citation content and formats in odata-atom-format-v4.0-wd01-2013-03-19-with-comments, odata-json-format-v4.0-wd01-2013-03-19-with-comments and odata-core-v4.0-wd01-part1-protocol-2013-4-5-with-comments, OData ATOM Format OData JSON Format OData Protocol
  27. ODATA-350 Clearly describe the service documents role, expected usage and responsibility in comparison with $metadata, OData ATOM Format OData CSDL OData JSON Format OData Protocol OData URL Conventions
  28. ODATA-352 Part II: Review results for OData JSON Format Version 4.0, OData JSON Format
  29. ODATA-353 Remove <CollectionType> and <TypeRef> elements, OData CSDL
  30. ODATA-354 Make Edm. prefix required when referring to built-in types, OData CSDL
  31. ODATA-355 ODATA-60 Define how property paths are represented in key part of URL, OData ABNF Construction Rules OData CSDL OData URL Conventions
  32. ODATA-356
  33. Review the changes in the latest version of Working Drafts
  34. OData ATOM Format OData Batch Processing Format OData CSDL OData JSON Format OData Protocol OData URL Conventions Vocabularies
  35. ODATA-357 Use GeoJSON in JSON and GML in Atom to represent geo types, OData ATOM Format OData JSON Format
  36. ODATA-358 Second parameter of the canonical search function should not allow search expressions, OData URL Conventions
  37. ODATA-359 Allow only true and false as boolean values, remove values 1 and 0, make values case-sensitive, all-lowercase, OData ABNF Construction Rules
  38. ODATA-360 Remove edm:documentation element from [CSDL], OData CSDL
  39. ODATA-361 Remove requirement that annotations come after all defined properties in CSDL, OData CSDL
  40. ODATA-363 specifiying selected properties in metadataurl is broken, OData Protocol
 
  1. Issues in Proposed state
  1. None
 
  1. Specifiction review: OData Extension for Data Aggregation Version 4.0 [8:30 am PT]
  1. OData Extension for Data Aggregation Version 4.0
  2. OData-TC 2013-05-02 Data Aggregation.pptx
 
  1. Next meeting [9:58am PT]
  1. May 9, 2013 during 8-10am PT
 
  1. AOB and wrap up [9:59am PT]
 
[2] References
 
[3] Timeline
 



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