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 2012.09.06


Here [1] is a revised agenda (revision 1) for the OData TC (Technical Committee) meeting scheduled on Thursday September 06, 2012 during 8-9am PT. For additional information, such as dial-in details, chat room, and timeline, refer to [2]. Feel free to suggest additions or modifications.

 

Changes in revision 1:

·       Removed ODATA-48 from 6d since it is already scheduled for discussion in section 6c.

·       Additions to 6d: ODATA-2, ODATA-113, ODATA-114, ODATA-115, ODATA-116, ODATA-117.

·       Section 7: Discussion item about extending TC meeting to 90 minutes.

 

Thanks.

 

[1] Draft agenda for 2012.09.06 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]
    1. Minutes from Aug 30, 2012 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/46804/odata_meeting-5_on-20120830_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 Sept 6, 2012

                                                               i.      None

    1. Action items NOT due by Sept 6, 2012 but MAY be ready for closure

                                                               i.      #0022: Investigate with the TC administration how to manage the isolated ABNF Grammar artifact in the standardizing process [owner: Ram Jeyaraman]

  1. Bunching up issues [8:20am PT]
    1. Given the large number of issues, we could consider bunching up issues for approvals, if and where possible. For example, the bunch of issues that have previously been resolved by the TC and currently in the Applied state could potentially be approved via a single motion to Closed, assuming everyone has reviewed the application of the resolutions and are fine with it. If anyone has any concern over the application of the approved resolution for any of the issues in that bunch, we can peel off those issues and process them via separate motions. This optimization could free up some time which we could use for discussing issues. Let’s discuss this and see if it makes sense to do it this way.
  2. Process issues [Issues list: https://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10103] [8:25am PT]
    1. Applied resolutions from Aug 30, 2012

                                                               i.      ODATA-27: Rules for primitive literals binary, datetimebody, decimal, double, single, string

                                                             ii.      ODATA-50: Inheritance for ComplexType: BaseType and Abstract attributes missing

                                                           iii.      ODATA-55: Allow Documentation for Schema, EnumType, and Member

                                                           iv.      ODATA-59: Literal value "Max" for MaxLength attribute is missing

                                                             v.      ODATA-63: 5.2.2 The edm:Alias Attribute should be optional

                                                           vi.      ODATA-64: Uniqueness of names of EntityContainer child elements

b.      Trivial issues directly moved to Applied state

                                                               i.      ODATA-44: Section 20: refer to rules in OData ABNF Construction Rules that define the necessary literals, add ABNF rules if necessary

                                                             ii.      ODATA-70: Correct definition of Edm.Time

c.       Issues in Open and Proposed state

                                                               i.      ODATA-48: Consistent typographical conventions for OData specifications

d.      Issues in New and Proposed state

                                                               i.      ODATA-2: Rules for error message inconsistent to Atom document

                                                             ii.      ODATA-4: Allow DefaultValue facet for FunctionImport Parameter

                                                           iii.      ODATA-5: Allow Collection(ComplexType) and Collection(PrimitiveType) for Type attribute of ValueTerm

                                                           iv.      ODATA-17: Define which DataServiceVersion this specification defines: 3.0 or 4.0

                                                             v.      ODATA-19: New / alternative XML namespaces with OASIS naming convention

                                                           vi.      ODATA-65: Remove the edm:Mode attribute

                                                          vii.      ODATA-66: 10.1 Collection Types: enumeration types are missing from list of types usable with attribute notation

                                                        viii.      ODATA-69: Enumeration types missing in ABNF

                                                           ix.      ODATA-74: Explicitly mention dynamic navigation properties

                                                             x.      ODATA-75: Schemas can span across more than one CSDL document

                                                           xi.      ODATA-76: Edm.Decimal is a floating-point type

                                                          xii.      ODATA-78: Allow $select to project parts of complex properties

                                                        xiii.      ODATA-79: PATCH for properties of complex properties

                                                        xiv.      ODATA-80: Add ABNF rules for requests and responses in JSON

                                                          xv.      ODATA-81: Rewrite section 3 Service Root URL for clarity and readability

                                                        xvi.      ODATA-82: Rewording of 4 Resource Path first paragraph

                                                      xvii.      ODATA-83: Rewording of 4 Resource Path second paragraph for clarity and readability

                                                     xviii.      ODATA-85: Move section 19 Informative XSD for CSDL into separate XML (text) file

                                                        xix.      ODATA-86: Allow TypeAnnotation only to target entity types and complex types

                                                          xx.      ODATA-87: Consider rewording 1 Introduction, second paragraph

                                                        xxi.      ODATA-88: The term EDMX wrapper should be explicitly declared once.

                                                      xxii.      ODATA-89: Add normative reference to JSON definition

                                                     xxiii.      ODATA-91: 2.1: explicitly state which format the server will return in response to each given set of headers

                                                     xxiv.      ODATA-92: 3.1.1.2: specify behavior if action overloads exist

                                                      xxv.      ODATA-94: 9.1.1: edm:UnderlyingType should be optional in <EnumType> definition

                                                     xxvi.      ODATA-95: ValueTerms should support a default value

                                                   xxvii.      ODATA-97: 10.4.2.4 Action Overload Resolution: resolution is done by binding parameter type

                                                 xxviii.      ODATA-98: 3.8 Representing Annotations: avoid the undefined terms "internally" and "externally"

                                                     xxix.      ODATA-99: 3.9 Advertisement for a Function or Action: add example and refer to ABNF rules

                                                      xxx.      ODATA-101: 5.3 Representing a Property in a Response: the object wrapper should be named "d"

                                                     xxxi.      ODATA-102: 5.4.1/2 Representing Actions/Functions Bound to Multiple Entities: add examples

                                                   xxxii.      ODATA-106: ValueTerms should support primitive types, complex types, and collections, but not entitytypes or collections of entitytypes

                                                 xxxiii.      ODATA-112: DateTime[Offset]: allow 24:00[:00] in time part

                                                 xxxiv.      ODATA-113: Remove legacy service operations from URL conventions and ABNF

                                                   xxxv.      ODATA-114: Allow /$count path suffix also for collection properties

                                                 xxxvi.      ODATA-115: Inconsistent use of WSP in system query options

                                                xxxvii.      ODATA-116: ABNF rule for parameter alias

                                              xxxviii.      ODATA-117: Case-sensitivity of system query options

 

  1. Extend TC meeting to 90 minutes? [8:50am PT]
    1. Given the large number of issues and the need for more discussion time, should we consider extending the weekly TC meeting duration to 90 minutes?

 

  1. Timeline and next steps [8:55am PT]
    1. Have all known issues on core specification been filed?
    2. Let’s review the timeline and discuss the immediate next steps.

 

9.       Next meeting [8:56am PT]

    1. Thursday September 13, 2012 8-9am PT?
  1. 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

·       Timeline (based on the F2F discussions and information we currently have)

o   Aug 31

§  All the core specs (seven in total) imported to OASIS specification template.

§  All known issues on core specs have been filed

o   Sept 20

§  Based on the outstanding issues, the TC will determine a reasonable timeline for the core specs.

 

GIF image



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