Chat transcript: Room information was updated by: Stefan Please register yourself at
https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=39089 - thanks. Stefan: @All: Voting Members: 1 of 16 (6%) (used for quorum calculation) Stefan: @All: Voting Members: 3 of 16 (18%) (used for quorum calculation) anonymous morphed into Ted Jones (Red Hat) Stefan: @All: Voting Members: 5 of 16 (31%) (used for quorum calculation) anonymous morphed into Matt Borges (SAP) Stefan: @All: Voting Members: 7 of 16 (43%) (used for quorum calculation) Mike Pizzo: I'm joining, but having Lync issues again. Need to grab another phone... Stefan: Quorum reached! Voting Members: 11 of 16 (68%) (used for quorum calculation) Stefan: Meeting will start in a minute ... Ralf Handl (SAP): 2.Approve agenda [8:05am PT] Ralf Handl (SAP): Switch order of item 5 and 6 Ralf Handl (SAP): Discuss additional Jira issues if time allows Ralf Handl (SAP): 3.Approve minutes from previous meeting(s) [8:10am PT] Ralf Handl (SAP): Minutes of 2015-02-02 approved Ralf Handl (SAP): Minutes of 2015-02-26 to be revisited in next meeting Ralf Handl (SAP): 4.Review action items Ralf Handl (SAP): a.Action items due i.Follow up with JSON-Schema on use for modeling anonymous morphed into Ed Bourne (BlackBerry) Ralf Handl (SAP): 6.Ramesh Reddy: Define a Reference Service (schema, data) that can be used to validate implementations Ralf Handl (SAP): Ramesh: define a reference service that uses all V4 constructs Ralf Handl (SAP): Ramesh: can be used for validating implementations and test interoperability Ralf Handl (SAP): Mike: have a live implementation of the reference service and make the example URLs in the spec live links Ralf Handl (SAP): Ramesh: document schema as well as example requests and responses Ralf Handl (SAP): Ramesh: TripPin service is rather complete with respect to V4 features Martin Zurmuehl:
http://www.odata.org/blog/trippin-new-odata-v4-sample-service/ e.g. Person contains trips Martin Zurmuehl:
https://github.com/OData/ODataSamples/issues Ralf Handl (SAP): Mike to investigate whether Olingo and/or the OData-TC can use the TripPin model and data Ralf Handl (SAP): 5.Process issues Ralf Handl (SAP): a.Issues for V4.0_ERRATA03 in New or Open state i.OData CSDL Ralf Handl (SAP): 1.ODATA-789 Primitive type Edm.Decimal is ill-defined in regard to Precision Ralf Handl (SAP): ODATA-789 is OPEN Ralf Handl (SAP): Make it clear that CSDL Precision for Edm.Decimal is equated with significant digits. Furthermore, since (unlike with temporal types) some clients will be unable to represent Edm.Decimal values with more than 28 digits (not just losing significant digits, but completely unable to represent). Not the 29 that we state currently. (C# doesn't rule the world (yet) but is important to accomodate). Require that any client or server which can represent a value of type Edm.Decimal must preserve all significant digits. C# decimal is fine for this, it just can't represent large values. java.math.BigDecimal is fine too. But IEEE DECFLOAT is not acceptable except when the Precision is > 16 (for 64-bit) or > 34 (for 128-bit). For example, 9.9e6144 is not representable using DECFLOAT for Edm.Decimal, as IEEE DECFLOAT cannot retain 6145 significant digits. Ralf Handl (SAP): 6.2.3 Attribute Precision Ralf Handl (SAP): Note: service designers SHOULD be aware that some clients are unable to support a precision greater than 29 for decimal properties and 7 for temporal properties. Ralf Handl (SAP): Combine ODATA-789 and ODATA-771 Ralf Handl (SAP): Proposal will have to clarify Ralf Handl (SAP): - Mapping of internal types to OData types Ralf Handl (SAP): - how clients can / have to deal with this Ralf Handl (SAP): 2.ODATA-787 Clarify how odata.Include-annotations preference affects odata.* markup Ralf Handl (SAP): ODATA-787 is OPEN Mike Pizzo: discussion: -We could define an alternate preference, odata.include-metadata as a general way to request certain metadata be omitted (regardless of format). -In this case we would probably want to explicitly say that odata.* annotations would be ignored in include-annotations, but that might seem a little strange for the JSON format. -Do we optimize for the JSON format, or try to anticipate potential future formats? Mike Pizzo: It's ignored by formats that don't represent this control information as annotations Put in the JSON document: -It's okay to use include-annotations to add additional odata annotations beyond those prescribed by the odata.metadata type parameter -Services MUST not subtract from odata.metadata level. -Services MUST always not exclude nextlink, delta link and count as appropriate Hubert Heijkers: I move to resolve ODATA-787 as proposed. Martin Zurmuehl: I second Ralf Handl (SAP): ODATA-787 is resolved as proposed Ralf Handl (SAP): 2.ODATA-479 Allow Content-ID referencing in request bodies for inserting links to newly created entities Ralf Handl (SAP): Postponed until a proposal has been added Ralf Handl (SAP): 3.ODATA-788 Clarify precidence rules for odata.include-annotations preference Ralf Handl (SAP): ODATA-788 is OPEN Hubert Heijkers: I move to resolve ODATA-788 as proposed. Mike Pizzo: I second Ralf Handl (SAP): ODATA-788 is resolved as proposed Ralf Handl (SAP): 7.Next meeting a.Thursday March 19, 2015 during 8-10am PT Ralf Handl (SAP): 8.AOB and wrap up From:
odata@lists.oasis-open.org [mailto:
odata@lists.oasis-open.org] On Behalf Of Handl, Ralf Sent: Mittwoch, 11. März 2015 16:09 To:
odata@lists.oasis-open.org Subject: [odata] Agenda for OData TC meeting on 2015-03-12 Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday March 12, 2015 during 8-10am PDT (16:00-18:00 CET) . 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 1. Roll call [8:00am PT] a. Self-registration link:
https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=39089 2. Approve agenda [8:05am PT] 3. Approve minutes from previous meeting(s) [8:10am PT] a. Minutes from February 02, 2015 TC meeting:
https://www.oasis-open.org/committees/download.php/55223/odata-meeting-90_on-20150205-minutes.html b. Minutes from February 26, 2015 TC meeting:
https://www.oasis-open.org/committees/download.php/55229/odata-meeting-91_on-20150226-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 i. Follow up with JSON-Schema on use for modeling 5. Process issues [Issues list:
https://issues.oasis-open.org/issues/?jql=project%20%3D%20ODATA ] [8:20am PT] a. Issues for V4.0_ERRATA03 in New or Open state i. OData CSDL 1. ODATA-789 Primitive type Edm.Decimal is ill-defined in regard to Precision ii. OData JSON Format 1. ODATA-771 Exponential notation for Edm.Decimal values in JSON payloads 2. ODATA-787 Clarify how odata.Include-annotations preference affects odata.* markup iii. OData Protocol 1. ODATA-774 Qualifiers for annotations: Preference odata.include-annotations 2. ODATA-479 Allow Content-ID referencing in request bodies for inserting links to newly created entities 3. ODATA-788 Clarify precidence rules for odata.include-annotations preference 4. ODATA-790 Bug in example 70 5. ODATA-791 11.2.5.2 System Query Option $orderby: specify order of Edm.Boolean and Edm.Geo iv. OData URL Conventions 1. ODATA-784 Need to specify the behaviour of arithmetic operators on Decimal type 2. ODATA-785 Numeric promotion (on overflow) across "number type families" is undesirable. 6. Ramesh Reddy: Define a Reference Service (schema, data) that can be used to validate implementations [9.00am PT] 7. Next meeting [9:50am PT] a. Thursday March 26, 2015 during 8-10am PT? 8. AOB and wrap up [9:55am 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/document.php?document_id=54822&wg_abbrev=odata