[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Agenda for OData TC meeting 2016-04-21 - chat transcript
Room information was updated by: Stefan Agenda link: https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201604/msg00062.html
Please register yourselves as usual at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41459
Stefan: Voting Members: 1 of 13 (7%) (used for quorum calculation) Stefan: Voting Members: 2 of 13 (15%) (used for quorum calculation) Stefan: Voting Members: 4 of 13 (30%) (used for quorum calculation) Stefan: Voting Members: 6 of 13 (46%) (used for quorum calculation) Stefan: @Ramesh: Shall I register you on your behalf? anonymous morphed into Ted Jones (Red Hat) Stefan: Voting Members: 7 of 13 (53%) (used for quorum calculation) Stefan: @Ralf: It looks we are formally quorate. Ralf Handl (SAP): We have only five people in the telco Ralf Handl (SAP): Anyone with dial-in problems? Stefan: @Ralf: I am happy, when my chat link does not drop ... Ralf Handl (SAP): Now everyone seems to have dialed in Ralf Handl (SAP): 2.Approve agenda Ralf Handl (SAP): Agenda item 5 will be deferred as Martin cannot attend today Ralf Handl (SAP): 3.Approve minutes from previous meeting(s) [8:10am] a.Minutes from April 14, 2016 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57959/odata-meeting-128_on-20160414-minutes.html
Ralf Handl (SAP): Minutes are approved 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] a.Action items due
i.#0032: Overview presentation on HTTP/2 features (due May 19, 2016)
ii.#0035: Identify the right open source license for the OASIS Open Source repositories for vocabularies and libraries (due March 31, 2016)
Ralf Handl (SAP): Postponed as Ram also cannot join today Ralf Handl (SAP): 5.Review of HTTP/2 features by Martin Zurmuehl [8:20am] Ralf Handl (SAP): Postponed Ralf Handl (SAP): 6.V4.0 Errata 3 [8:40am] a.ODATA-932: Typo in example 44: missing T in duration literal
Ralf Handl (SAP): <Annotation Term="org.example.task.duration"> <Duration>P11DT23H59M59.999999999999S</Duration>
</Annotation>
Ralf Handl (SAP): ODATA-932 is OPEN Hubert Heijkers: I move to resolve ODATA-932 as proposed Mark Biamonte (Progress): I second Ralf Handl (SAP): ODATA-932 is RESOLVED as proposed Ralf Handl (SAP): 7.V4.01 issues [8:50am] a.Issues for V4.01_WD01 in New or Open state
Ralf Handl (SAP): i.OData protocol 1.ODATA-920 Specify overflow for int data types
ODATA-919 Specify the result type for each operation based on operator types
Ralf Handl (SAP): Java INT roll over from MAXINT to MININT without error message Ralf Handl (SAP): Postpone until we have more insight into behavior of mainstream programming languages Ralf Handl (SAP): 3.ODATA-918 Add operator "divideby" that always results in a decimal. Ralf Handl (SAP): ODATA-918 is OPEN Ralf Handl (SAP): Add operator "divideby" that does mathematical division and always results in a decimal (as if both operands were promoted to decimal). Ralf Handl (SAP): a divideby b is identical to cast(a,Edm.Decimal) div cast(b,Edm.Decimal) Ralf Handl (SAP): Services that support div and cast SHOULD also support divideby Ralf Handl (SAP): Services MAY advertise it with Capabilities.FilterFunctions Ralf Handl (SAP): Alternative shorter names: Ralf Handl (SAP): divby Ralf Handl (SAP): div2 Ralf Handl (SAP): ddiv for decimal div Ramesh Reddy(RedHat): divd Ralf Handl (SAP): divby is the agreed name Hubert Heijkers: I move to resolve ODATA-918 as per the amended proposal. Mark Biamonte (Progress): I second Ralf Handl (SAP): ODATA-918 is OPEN Ralf Handl (SAP): Amended proposal: Add operator "divby" that does mathematical division and always results in a decimal (as if both operands were promoted to decimal).
a divbyb is identical to cast(a,Edm.Decimal) div cast(b,Edm.Decimal)
Services that support div and cast SHOULD also support divby
Services MAY advertise it with Capabilities.FilterFunctions
Hubert Heijkers: I move to resolve ODATA-918 as per the amended proposal. Mark Biamonte (Progress): I second Ralf Handl (SAP): ODATA-918 is RESOLVED as proposed Ralf Handl (SAP): 4.ODATA-921: Specify operations for keyless nav props Ralf Handl (SAP): ODATA-921 is already RESOLVED - remove from agenda Ralf Handl (SAP): ODATA-925: Add a Core term for a service/schema/model version.
<Term Name="SchemaVersion" Type="String" AppliesTo="Schema">
<Annotation Term="Core.Description" String="Version of the schema (not to be confused with the protocol version)" />
</Term>
Ralf Handl (SAP): Is already RESOLVED
Ralf Handl (SAP): 5.ODATA-928: Allow client to use OData-SchemaVersion header to indicate the metadata version it is using
Ralf Handl (SAP): Client can set an OData-SchemaVersion header in requests.
Server may (these are example possibilities, possibilities, not requirements) use this information in a number of ways:
(1) Refuse requests from the client if the server's metadata version is now incompatible with the version the client has indicated it is using.
(2) Include extra metadata in responses, e.g. "@odata.type" for properties which weren't in the client's versin of the metadata, but now exist in the server's version (e.g. this allows the client to correctly treat those properties as dynamic, while knowing their proper type). Room Information:
Agenda link: https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201604/msg00062.html
Please register yourselves as usual at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41459
Ralf Handl (SAP): ODATA-928 is OPEN Ralf Handl (SAP): Mike volunteers to flesh out proposal Ralf Handl (SAP): Ideas: allow incompatible changes at same service root Ralf Handl (SAP): Allow clients to request a specific schema version Ralf Handl (SAP): 6.ODATA-812: Allow omitting namespaces for unambiguous functions/actions Ralf Handl (SAP): Reconsider choice of annotation versus XML element/attribute: clients have to change their interpretation of JSON payloads depending on this flag anyway. Ralf Handl (SAP): Going with an annotation allows keeping the XML schema stable Ralf Handl (SAP): Check with mainstream clients whether they specify odata-maxversion:4.0 Ralf Handl (SAP): Mike to check .NET clients Ralf Handl (SAP): Ralf to check Olingo clients Ralf Handl (SAP): ii.Simplified Payload 1.ODATA-818 Omit properties whose value is null or the $metadata-defined default value
Ramesh Reddy(RedHat): default value being payload or not I see as completely different issue Ralf Handl (SAP): Hubert: make this a preference Ralf Handl (SAP): Prefer: omit-default-values Ralf Handl (SAP): Prefer: omit-null-values Ralf Handl (SAP): Proposal: specify preferences odata.omit-default-values and odata.omit-null-values to indicate that the client is able to fill in the blanks. odata.omit-default-values implies odata.omit-null-values Martin Z. SAP SE: next meeting will be next week Martin Z. SAP SE: meeting is adjourned From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org]
On Behalf Of Handl, Ralf Here [1] is the agenda for the OData TC (Technical Committee) meeting
scheduled on Thursday April 21, 2016 during 8-10am Pacific Time. 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
i. #0032:
Overview presentation on HTTP/2 features (due May 19, 2016)
ii. #0035:
Identify the right open source license for the OASIS Open Source repositories for vocabularies and libraries (due March 31, 2016)
5.
Review of HTTP/2 features by Martin Zurmuehl [8:20am]
a.
Issues
for V4.01_WD01 in New or Open state
i. OData protocol
1.
ODATA-920 Specify overflow for int data types
2.
ODATA-919 Specify the result type for each operation based on operator types
3.
ODATA-918 Add operator "divideby" that always results in a decimal.
4.
ODATA-921:
Specify operations for keyless nav props
6.
ODATA-812: Allow omitting namespaces for unambiguous functions/actions
ii. Simplified Payload
1.
ODATA-818
Omit properties whose value is null or the $metadata-defined default value
2.
ODATA-809
Define non-message format for final response of async request
iii. New Query Capabilities
1.
ODATA-614 Allow $expand, $select, ... with POST/PATCH/PUT in combination with return=representation to specify the response shape
2.
ODATA-827 introduce $compute query option
3.
ODATA-798 - Semantic Key or Alternate Key for entity types
iv. Enumerations
1.
ODATA-849 Add possibility for enumeration types to "extend" another enumeration type
2.
ODATA-494 Define inheritance for enumeration types
3.
ODATA-874 Allow Edm.String as underlying type for enumeration types
v. OData CSDL
1.
ODATA-923:
$expand for $metadata to include referenced schemas
2.
ODATA-618: Allow using term names in positions that allow type names
3.
ODATA-929: Nullable facet should default to false for collection types, rather than being unspecified
vi. Annotations
1.
ODATA-516 - Add super type Edm.AnyPath for Edm.PropertyPath, Edm.NavigationPropertyPath, and Edm.AnnotationPath
2.
ODATA-545 - Allow applying Capability terms CountRestrictions, TopSupported, SkipSupported etc. to all resources returning collections
3.
ODATA-571 - Add annotation for properties that are (not) part of the default selection if no $select is specified
4.
ODATA-631 - Allow expressing that a term can be applied any collection and is not restricted to entity sets
5.
ODATA-735 - Enhance the CSDL for instance annotations
6.
ODATA-811 - Define propagation and (partial) overriding of annotations
7.
ODATA-816 - Add Capability term for filter _expression_ restrictions
8.
ODATA-859 - Define term, semantics for inserting error information into a (mostly) successful
response
9.
ODATA-884 - Add term ErrorCodes to describe possible codes in error messages (public comment
c201510e00019)
vii. JSON Format
1.
ODATA-868 - Describe format for In-Stream errors
viii. Batch
1.
ODATA-541 - Allow the If-Match header to reference the ETag that resulted from an earlier operation in a batch request
ix. Complex Types
1.
ODATA-560 - Allow arbitrary properties in referential constraints
x. Decimal
1.
ODATA-557 - Allow exponential notation for Edm.Decimal
2.
ODATA-747 - Allow IEEE 754 constants [-]INF and NaN also for Edm.Decimal and integer types
8.
OData CSDL JSON [9:30am]
a.
Parked issues
i. ODATA-906 Consider how to specify an included namespace as a default in JSON CSDL
ii. ODATA-890 Specify how to get from a JSON message to a JSON schema for validating this
message
iii. ODATA-863 Represent Terms similar to Types
a.
Hierarchy discussion
b.
Issues
i. ODATA-905 Example 67: result row for USA, Sugar missing, Example 68: last
total should be 7
ii. ODATA-904 Example 55: clarify groupby in combination with relationships of
instance cardinality zero
iii. ODATA-909 ABNF for pathPrefix should also allow qualified ComplexTypeName
b.
Thursday April 28, 2016?
[2] References
[3] Timeline |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]