[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [odata] Agenda for OData TC meeting on 2015-02-26
Transcript of chat room – raw minutes: Stefan: @ALL: Please register yourself (is now open) at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=39087 ... thanks. Room Information:
OASIS OData Technical Committee meeting chat room.
Dial-in details: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/46401/TC%20meeting%20dial-in%20details.htm.
Meeting starts @ 0800 PT i.e. 1700 CEST. Ralf Handl (SAP): Hi Stefan, good to see you! Susan Malaika (IBM): Unfortunately I cannot join the call today - I'm just in the chat ..... Ralf Handl (SAP): Hi Susan, no problem. Can you register your attendance? anonymous morphed into Matt Borges (SAP) Ralf Handl (SAP): One more registration needed to achieve quorum Ralf Handl (SAP): Voting Members: 9 of 16 (56%) (used for quorum calculation) - achieved quorum Ralf Handl (SAP): 2.Approve agenda [8:05am PT] Ralf Handl (SAP): Agenda is approved Ralf Handl (SAP): 3.Approve minutes from previous meeting(s) [8:10am PT] Ralf Handl (SAP): Postponed to next meeting Ralf Handl (SAP): 4.Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT] Ralf Handl (SAP): a.Action items due i.Follow up with JSON-Schema on use for modeling
Mike Pizzo: (I'm having audio difficulties...) Ralf Handl (SAP): We'll wait Mike Pizzo: I can't seem to call in. I keep getting "Sorry, can't connect you to your meeting right now." Was everyone else able to call in okay? Mike Pizzo: I tried two numbers, will try another phone, but please don't wait for me. Ralf Handl (SAP): 5.Process issues [Issues list: https://issues.oasis-open.org/issues/?jql=project%20%3D%20ODATA] [9:00 am PT] Ralf Handl (SAP): a.Issues for V4.0_ERRATA03 in New or Open state i.OData ABNF
Ralf Handl (SAP): 2.ODATA-783 Is it intentional that mindatetime/maxdatetime/now don't permit %-encoded parentheses in ABNF? Stefan: @Ralf: Have problems dialing in, but will continue to try (travelling ...) Ralf Handl (SAP): ODATA-783 is OPEN Mark Biamonte (Progress): I move to resolve OData-783 to allow %encoding paraenthesis for minDatetime, maxdatetime and now functions jwillson (ind-msi): I second Martin Zurmuehl: I second Ralf Handl (SAP): ODATA-783 is resolved as proposed Ralf Handl (SAP): 1.ODATA-774 Qualifiers for annotations: Preference odata.include-annotations Ralf Handl (SAP): Postpone to next meeting Ralf Handl (SAP): ii.OData CSDL Ralf Handl (SAP): 1.ODATA-782 Example 57: choose better example Ralf Handl (SAP): 1.ODATA-782 Example 57: choose better example Martin Zurmuehl: <Apply Function="odata.fillUriTemplate"> <String>http://host/service/Genres('{genreName}')</String> <LabeledElement Name="genreName" Path="NameOfMovieGenre" />
</Apply>
Ralf Handl (SAP): http://host/someAPI/Genres/{genreName}/LongDescription Ralf Handl (SAP): ODATA-782 is OPEN Martin Zurmuehl: <Apply Function="odata.fillUriTemplate"> <String>http://host/service/Genres({genreName})</String> <LabeledElement Name="genreName">
<Apply Function="odata.uriEncode" >
<Path>NameOfMovieGenre</Path>
</Apply>
</LabeledElement>
</Apply>
Mike Pizzo: Propose to resolve ODATA_782 as proposed. Martin Zurmuehl: I second Ralf Handl (SAP): ODATA-782 is resolved as proposed Ralf Handl (SAP): iii.OData JSON Format Ralf Handl (SAP): 1.ODATA-771 Exponential notation for Edm.Decimal values in JSON payloads Ralf Handl (SAP): Postponed to next meeting Ralf Handl (SAP): iv.OData Protocol Ralf Handl (SAP): 1.ODATA-479 Allow Content-ID referencing in request bodies for inserting links to newly created entities Ralf Handl (SAP): Postpone to next meeting Ralf Handl (SAP): 2.ODATA-778 Example in section 11.7.3.1, "Referencing Requests in a Change Set", should use JSON, not ATOM Ralf Handl (SAP): ODATA-778 is OPEN Martin Zurmuehl: I move to resolve OData-778 as proposed Mike Pizzo: I second Hubert Heijkers: I second Ralf Handl (SAP): ODATA-778 is resolved as proposed Ralf Handl (SAP): v.OData URL Conventions Ralf Handl (SAP): 1.ODATA-777 Clarify multiply/divide duration by number Ralf Handl (SAP): ODATA-777 is OPEN Hubert Heijkers: I move to resolve ODATA-777 as proposed Mike Pizzo: I second. Ralf Handl (SAP): ODATA-777 is resolved as proposed Ralf Handl (SAP): 2.ODATA-780 indexof: what to return if the second argument does not appear in the first argument Ralf Handl (SAP): ODATA-780 is OPEN Hubert Heijkers: I move to resolve ODATA-780 as proposed Ramesh Reddy(Red Hat): i second Ralf Handl (SAP): ODATA-780 is resolved as proposed Ralf Handl (SAP): 3.ODATA-781 substring: what to return if the start index is outside the first argument string, or the desired length exceeds the remaining string length Ralf Handl (SAP): ODATA-781 is OPEN Ramesh Reddy(Red Hat): should not return null. it could be valid value Ralf Handl (SAP): Hubert: check with SQL what it does, null or empty string Ralf Handl (SAP): Hubert: don't like "bad request" Ralf Handl (SAP): Reserve "bad request" for negative start index or length, both never make sense Ralf Handl (SAP): Mike: desired length exceeds remaining string length just leads to a shorter result Mark Biamonte (Progress): Java defines this as error conditions. From the documentationIndexOutOfBoundsException - if the beginIndex is negative, or endIndex is larger than the length of this String object, or beginIndex is larger than endIndex. Ramesh Reddy(Red Hat): I agree that if SQL ref returns empty or null then that is fine Ramesh Reddy(Red Hat): I am also checking SQL Spec Ramesh Reddy(Red Hat): orcacle: http://www.techonthenet.com/oracle/functions/substr.php Ralf Handl (SAP): Negative start index could be treated as counting from the end of the string, i.e. substring(X,-3) gives the last three characters Ralf Handl (SAP): DB2 will return empty string of start > length Ralf Handl (SAP): DB2 will return error if start < 0 Ralf Handl (SAP): SQL Anywhere treats negative start as "start from beginning" Ralf Handl (SAP): SQL Anywhere returns empty string as start > length Ralf Handl (SAP): Mike: return empty string if start > length Ralf Handl (SAP): Mike: return remaining characters if desired length exceeds string length Ralf Handl (SAP): Mike: explicitly "unspecify" behavior for negative start index Mike Pizzo: Proposal: Mike Pizzo: -Empty string should be returned for an index larger than the length of the string. -Length too long should be allowed and return as many characters up to the specified length.
-The behavior for a negative index is undefined.
-A negative length is a bad request.
Mark Biamonte (Progress): I move to resolve OData-781 as proposed Matt Borges (SAP): I second Brent Gross: I second Ralf Handl (SAP): ODATA-781 is resolved as proposed Ralf Handl (SAP): 4.ODATA-784 Need to specify the behaviour of arithmetic operators on Decimal type Ralf Handl (SAP): If A and B are values of type decimal, with scales scaleof(A) and scaleof(B), then:
scaleof(A add B) = max(scaleof(A), scaleof(B))
scaleof(A sub B) = max(scaleof(A), scaleof(B))
scaleof(A mul B) = scaleof(A) + scaleof(B)
scaleof(A div B) = scaleof(A) + scaleof(B)
Ralf Handl (SAP): ODATA-784 is OPEN Ralf Handl (SAP): 1 div 3 add 2 div 3 Ralf Handl (SAP): Rules 1-3 are straight-forward Ralf Handl (SAP): Precision for add also might need to be increased by 1 Ralf Handl (SAP): Mike: to what extent do we need to specify this? Mike Pizzo: Questions brought up: Mike Pizzo: To what extent do we need to specify this? Can we say the result is a decimal of sufficient scale?
Is it dependent upon the defined scale of the data types or the actual numbers?
If the _expression_ is used in a $filter, and some of the operands result in an overflow and some do not, how is that handled?
Ralf Handl (SAP): Whole request needs to fail if computation fails for an instance Ralf Handl (SAP): Issue postponed to next meeting Ralf Handl (SAP): 5.ODATA-785 Numeric promotion (on overflow) across "number type families" is undesirable. Ralf Handl (SAP): ODATA-785 is OPEN Ralf Handl (SAP): Proposal
Expressly disallow numeric promotion (on overflow) across number type families.
Expressly disallow numeric promotion (on overflow) between Single and Double.
The remaining legal option would be numeric promition on overflow only for integer types.
Ralf Handl (SAP): Concern that this would change normative parts of the specification Ralf Handl (SAP): Clients are probably not concerned about current rules Ralf Handl (SAP): Servers may find it difficult to follow current rules Ralf Handl (SAP): Research required Ralf Handl (SAP): Postponed to next meeting Ralf Handl (SAP): Back to i.Follow up with JSON-Schema on use for modeling Ralf Handl (SAP): Mike started investigation, follow-up on next meeting Ralf Handl (SAP): 6.Next meeting [9:50am PT] Ralf Handl (SAP): a.Thursday March 12, 2015 during 8-10am PT? Ramesh Reddy(Red Hat): Ralf how I can request an agenda item on meeting? Ralf Handl (SAP): NOTE: US and Europe are one hour out of sync Ralf Handl (SAP): Meeting is adjourned From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org]
On Behalf Of Handl, Ralf Here [1] is a draft agenda for the OData TC (Technical Committee) meeting
scheduled on
Thursday February 26, 2015 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
1.
Roll call [8:00am PT]
a.
Self-registration link:
https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=39087
2.
Approve agenda [8:05am PT]
3.
Approve minutes from previous meeting(s) [8:10am PT]
a.
Minutes from February 05, 2015 TC meeting not yet available, postponed to next meeting
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]
[9:00 am PT]
a.
Issues
for V4.0_ERRATA03 in New or Open state
i. OData ABNF
1.
ODATA-774
Qualifiers for annotations: Preference odata.include-annotations
2.
ODATA-783
Is it intentional that mindatetime/maxdatetime/now don't permit %-encoded parentheses
in ABNF?
ii. OData CSDL
1.
ODATA-782
Example 57: choose better example
iii. OData JSON Format
1.
ODATA-771
Exponential notation for Edm.Decimal values in JSON payloads
iv. OData Protocol
1.
ODATA-479
Allow Content-ID referencing in request bodies for inserting links to newly
created entities
2.
ODATA-778
Example in section 11.7.3.1, "Referencing Requests in a Change Set", should use JSON,
not ATOM
v. OData URL Conventions
1.
ODATA-777
Clarify multiply/divide duration by number
2.
ODATA-780
indexof: what to return if the second argument does not appear in the first argument
3.
ODATA-781
substring: what to return if the start index is outside the first argument string,
or the desired length exceeds the remaining string length
4.
ODATA-784
Need to specify the behaviour of arithmetic operators on Decimal type
5.
ODATA-785
Numeric promotion (on overflow) across "number type families" is undesirable.
6.
Next meeting [9:50am PT]
a.
Thursday March 12, 2015 during 8-10am PT?
7.
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
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]