[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Agenda for OData TC meeting 2016-05-12
[8:00] Room information was updated by: Stefan Reg link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41462 [8:00] Stefan: Voting Members: 5 of 13 (38%) (used for quorum calculation) [8:07] Stefan: Voting Members: 7 of 13 (53%) (used for quorum calculation) [8:34] Ram (Microsoft): Meeting quorate [8:34] Ram (Microsoft): Minutes from April 21, 2016 approved, no objections. No corrections. [8:35] Ram (Microsoft): Action # 35: Update - Ram will send out an approval package (for next meeting) [8:35] Ram (Microsoft): Action #32: Martin gave a presentation on HTTP/2 today [8:46] Ram (Microsoft): Action 32 is closed. [8:52] Mike Pizzo: I propose w resolve ODATA-936 as proposed [8:52] Martin Z. SAP SE: I second [8:52] Ram (Microsoft): ODATA-936: CSDL errata02 11.1.3 Type Definition Facets references nonexistent standard vocabulary [8:52] Ram (Microsoft): ODATA-936 has been resolved as proposed, no objections [8:53] Ram (Microsoft): ODATA-934: Clarify invoking an action with no parameters [9:00] Ram (Microsoft): ODATA-934 is open [9:01] Mike Pizzo: I move we resolve ODATA-934 as proposed. [9:01] Martin Z. SAP SE: I propose w resolve ODATA-936 as proposed 934 [9:01] Martin Z. SAP SE: I second [9:01] Ram (Microsoft): ODATA-934 has been resolved as proposed, no objections [9:01] Mike Pizzo: I have opened ODATA-938 to track handling in 4.01 [9:04] Ram (Microsoft): v4.01 issues discussion [9:04] Ram (Microsoft): ODATA-928: Allow client to use OData-SchemaVersion header to indicate the metadata version it is using [9:13] Matt Borges (SAP): I move to resolve OData-928 as proposed [9:14] Mike Pizzo: I second [9:14] Ram (Microsoft): ODATA-928 has been resolved as proposed, no objections [9:14] Ram (Microsoft): ODATA-812: Allow omitting namespaces for unambiguous functions/actions [9:20] Mike Pizzo: I propose we (re-)resolve ODATA-812, with the following additional comment added to the proposal: [9:20] Mike Pizzo: -make sure that docs are clear that services must not require clients to understand custom annotations, but OData annotations may imply semantics that a client reporting support for that version of the specification would need to understand in order to work correctly with the service. [9:21] Martin Z. SAP SE: I second [9:22] Ram (Microsoft): ODATA-812 has been resolved as proposed, no objections [9:22] Ram (Microsoft): ODATA-846: Add version 4.01 [9:25] Ram (Microsoft): We will review the proposed resolutions and likely resolve this issue just before CSD01 approval in June [9:25] Ram (Microsoft): ODATA-920 Specify overflow for int data types [9:47] Martin Z. SAP SE: Values of types Edm.Byte, Edm.SByte, Edm.Int16, Edm.Int32, Edm.Int64, Edm.Single, Edm.Double, and Edm.Decimal are represented as JSON numbers, except for NaN, INF, and INF which are represented as strings. [9:48] Mike Pizzo: Working proposal: [9:48] Mike Pizzo: 1) Add a new annotation, "odata.numericValueException", with valid values "INF", "-INF" and "NaN". 2) Services don't return the property, just the property annotation specifying the value exception: "NumberOfODataUsers@odata.numericValueException":"INF" 3) Could be applied to any numeric type. 4) For 4.01 clients, always return this for single/double, instead of as property values. [9:51] Martin Z. SAP SE: I propose we resolve ODATA-920 as proposed [9:51] Mike Pizzo: I second [9:52] Ram (Microsoft): ODATA-920 has been resolved as proposed, no objections [9:52] Ram (Microsoft): ODATA-747 - Allow IEEE 754 constants [-]INF and NaN also for Edm.Decimal and integer types [9:57] Gerald Krause (SAP): I move to close ODATA-747 as resolved by ODATA-920. [9:57] Matt Borges (SAP): I second [10:05] Ram (Microsoft): ODATA-747 has been closed, no objections [10:05] Ram (Microsoft): Next meeting: next week same time [10:05] Ram (Microsoft): Meeting adjourned. From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org]
On Behalf Of Ram Jeyaraman Here [1] is the agenda for the OData TC (Technical Committee) meeting
scheduled on Thursday May 12, 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]
i. ODATA-936: CSDL errata02 11.1.3 Type Definition Facets references nonexistent standard vocabulary
ii. ODATA-934: Clarify invoking an action with no parameters
i. ODATA-932: Typo in example 44: missing T in duration literal
ii. ODATA-931: Typo in Example 32: An entity container aggregates entity sets, singletons, action imports, and function
imports. [see
minutes]
iii. ODATA-930: Ensure that errata03 vocabularies have explicit Nullable facet for collection-typed properties [see
minutes]
c.
Next steps (planned for next meeting)
i. Confirm the proposed corrections (including the above issues raised by TC members) as Approved Errata by a Full Majority Vote. We will list the above issues as
comments received during public review in a comment resolution log and provide that to the TC admin as part of the approval motion.
a.
Issues
for V4.01_WD01 in New or Open state
i. OData protocol
2.
ODATA-812: Allow omitting namespaces for unambiguous functions/actions
3.
ODATA-846: Add version 4.01
4.
ODATA-920 Specify overflow for int data types [may need more discussion]
5.
ODATA-919 Specify the result type for each operation based on operator types [may need more discussion]
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. Batch
1.
ODATA-541 - Allow the If-Match header to reference the ETag that resulted from an earlier operation in a batch request
iv. Complex Types
1.
ODATA-560 - Allow arbitrary properties in referential constraints
v. 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)
vi. 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
vii. 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
viii. 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
4.
ODATA-674:
Specify navigation property binding combined with containment *
5.
ODATA-935: Allow singletons to be members of an entity set
ix. JSON Format
1.
ODATA-868 - Describe format for In-Stream errors
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
ii. URL Conventions
1.
ODATA-933: Allow using instance annotations in $filter
iii. Interfaces
1.
ODATA-619: Attach action and function signatures to terms, i.e. make a term definition an interface definition
2.
ODATA-696: Support "interfaces" for casting entities to multiple different types
iv. Set operations
1.
ODATA-836: Allow applying actions to a filtered collection of entities
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 9.
OData CSDL JSON [9:40am]
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
b.
Thursday May 19, 2016?
[2] References
[3] Timeline |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]