Here [1] is a draft agenda for the OData TC (Technical
Committee) meeting scheduled
on Wednesday January 17, 2023 during 8-10 am PST (17:00-19:00 CET).
For TC timeline, see [2].
Feel free to suggest additions or modifications.
Thanks.
[1] Agenda
-
Roll call [8:00]
-
-
Conference ID: 629 315 222#
Local
numbers |
Learn more about Teams |
Meeting options
-
Approve agenda [8:05]
-
Approve minutes from previous meeting(s) [8:10]
-
-
OData Metamodel [8:15]
-
George's approach with UML stereotypes [8:15]
-
Christof's approach [8:45]
-
Issues [9:00]
-
V4.02 and V4.01 Errata 01: RESOLVED
-
ODATA-1354 Add
support for SoundsLike expressions
-
ODATA-1426 Clarify
use of byte-order mark (BOM) in text/plain responses
-
ODATA-1436 Relax
constraint that DELETE Cannot return data
-
ODATA-1484 Allow
a client to query the status of an asynchronous request without returning the result if the request completed.
-
ODATA-1516 Support
returning inline count accuracy
-
ODATA-1526 Support
collapsing individual sections (chapters) in the HTML versions of the specification
-
ODATA-1528 Update
JSON Delta Response payload examples
-
ODATA-1549 Clarify
semantics of etag in delta requests/responses
-
ODATA-1567 Clarify
“Expand to the level present in the deep insert request”
-
ODATA-1580 Further
clarify restrictions around open types
-
ODATA-1599 Clarify
support for supplementary plane characters in OData Identifiers
-
V4.02 and V4.01 Errata 01:
APPLIED
-
ODATA-1323 Clarify
representation of GEO literals and streams in annotations (XML, JSON)
-
ODATA-1481 Allow
Edm.Stream for non-binding action and function parameters
-
ODATA-1547 Recursive
complex types must be nullable
-
ODATA-1588 Allow
creating and linking along a nullable single-valued navigation
-
V4.01 Errata:
NEW or OPEN
-
ODATA-1370 CSDL
Section 12.9 “Parameter” mixing with “overload” causes ambiguity, particularly with regard to parameter ordering
-
ODATA-1424 OData
4.01 JSON “Delta Responses” doesn’t describe use of “@id” (or “@odata.id”) for Added/Changed Entity
-
ODATA-1496 clarify
the relationship of the various path _expression_ types
-
ODATA-1558 Define
semantics for navigation properties of type Edm.EntityType
-
ODATA-1559 Clarify
definition of transient.
-
ODATA-1560 Clarify
usage of URL templates with callback preference
-
ODATA-1573 clarify
behavior for omitted values in PATCH and PUT
-
ODATA-1603 It
is not clear if the entities in a collection returned by a function always have an entity-id
-
ODATA-1610 Clarify
use of ‘wait’ preference without ‘respond-async’ preference
-
V4.02:
NEW or OPEN with champion and proposal
-
ODATA-730 Lack
of ordering constraints on delta responses may require clients to buffer (or persist) entire response to process it correctly
-
ODATA-879 Support
Arrays of Arrays
-
ODATA-919 Specify
the result type for each operation based on operator types
-
ODATA-923 Support
subsetting returned metadata
-
ODATA-1059 Improve
specification and use of NavigationProperties, EntitySets, and Singletons
-
ODATA-1060 Improve
specification of element response requirements
-
ODATA-1071 Nullable
Collection Navigation Property
-
ODATA-1113 Allow
alternate / native search syntax
-
ODATA-1239 Define
a mechanism to distinguish between inserted and updated entities in a Delta message
-
ODATA-1253 Abstract
type definition Core.Number as a super-type of all numeric types
-
ODATA-1336 Querying
“JSON properties”
-
ODATA-1340 PATCH:
new preference return=delta to get back a delta response
-
ODATA-1405 /$query
shall allow Content-Type: application/x-www-form-urlencoded
-
ODATA-1407 No
way to $select instance annotations on primitive types
-
ODATA-1435 Conditionally
add an element to a collection
-
ODATA-1457 Potential
confusion wrt Content-Type header for media entities
-
ODATA-1506 Allow
index segments in path expressions
-
ODATA-1534 OData
4.01 JSON batch format doesn’t support streaming use cases well
-
ODATA-1540 Require
decoding of plus as space in query part of URL
-
ODATA-1544 Section
4.17: support new HTTP QUERY method, deprecate /$query path suffix
-
ODATA-1545 Allow
services to validate read-only properties in update payloads
-
ODATA-1548 Encourage
clients to specify the correct value for non-key, non-computed read-only values (or omit)
-
ODATA-1569 Allow
CSDL JSON also for OData versions 2.0 and 3.0
-
ODATA-1575 Remove
restriction on Partner navigation
-
ODATA-1583 Clarify
representation of context URLs in JSON payloads
-
ODATA-1585 Should
be able to change type when PATCHing an entity
-
ODATA-1589 /$query
shall allow Content-Type: application/json
-
ODATA-1590 Clarify
where alternate keys can be used
-
ODATA-1594 Add
support for fuzzy search function within $filter, etc.
-
ODATA-1597 Allow
to create annotations in CSDL with a less verbose format to increase adoption
-
ODATA-1601 concat:
allow more than two arguments
-
ODATA-1616 Clarify
rules around results returned from Create/Update
-
ODATA-1618 Clarify
matchespattern and regular _expression_ flags
-
ODATA-1621 Clarify
annotations on unavailable properties
-
ODATA-1623 Support
alternate keys in delta patch
-
ODATA-1624 Make
conformance clauses more future-proof
-
ODATA-1626 Should
support annotations to bound actions/functions via path
-
-
ODATA-579 Should
we support dynamic functions/actions?
-
ODATA-601 Investigate
enhancements to interoperability and feature set of OData JSON through JSON-LD
-
ODATA-665 Add
OData-MetadataETag header
-
ODATA-854 Consider
use of OPTIONS for discovering formats, other capabilities and features
-
ODATA-900 Cross-service
navigation and service versioning
-
ODATA-1052 Consider
the “fragility” of server-driven paging
-
ODATA-1062 Revise
UML model for OData Metamodel
-
ODATA-1070 Clarify
text related to Canonical URL
-
ODATA-1107 Introduce
instance annotation to specify which types an instance “implements”
-
ODATA-1235 ActionImport
and FunctionImport on EntityType
-
ODATA-1246 Allow
BaseType of EntityType to be a ComplexType
-
ODATA-1261 Allow
$pagesize system query option
-
ODATA-1262 Explicitly
state structural restrictions of type Edm.Untyped
-
ODATA-1308 Ability
to reference newly discovered OData services
-
ODATA-1317 ContextUrl
does not represent navigation properties for which the entity references ($ref) are included
-
ODATA-1333 Add
Terms, Abbreviated Terms, and Symbols sections to specifications
-
ODATA-1350 OData
V2 required continue-on-error style batch responses, V4 makes it optional for servers (due to use of Prefer)
-
ODATA-1379 Consider
adding railroad diagrams for the URL syntax
-
ODATA-1386 Introduce
primitive types for color values
-
ODATA-1438 New
preference return=keys
-
ODATA-1441 New
query option $expect combining $expand and $select
-
ODATA-1479 Current
instance/collection is only defined adhoc
-
ODATA-1504 Dry-run
of data modification requests
-
ODATA-1505 Expressions
in action payloads
-
ODATA-1514 Generalize
the use of $each
-
ODATA-1527 Allow
functions/actions to return (and take) a delta payload
-
ODATA-1529 Provide
support for selecting the id of an entity
-
ODATA-1535 Should
updates of related resources be supported in Create?
-
ODATA-1574 Expand
function results
-
ODATA-1579 Allow
references to Core.ContentIDs in batch request URLs
-
ODATA-1586 Clarify
create/replace for server-defined dynamic properties
-
ODATA-1606 Separation
of concerns: ABNF for URL components instead of whole URLs
-
ODATA-1608 Safety,
Security and Privacy Considerations: fill out or remove appendix
-
ODATA-1614 Add
NonSelectableProperties to SelectSupportType
-
ODATA-1625 Cannot
specify null as DefaultValue in CSDL XML
-
Data Aggregation:
NEW or OPEN
-
ODATA-1492 Temporal
transformation at() for snapshot entity sets
-
Temporal:
NEW or OPEN
-
ODATA-1542 Chapter
3, example 7 still uses TimeSliceStart and TimeSliceEnd
-
ODATA-1551 4.3.2.3
Delete during a Period, step 3: align with corresponding step of 4.3.2.1, step 3
-
ODATA-1615 4.3.2.3
Delete during a Period: add example
-
Vocabularies:
NEW or OPEN with proposal
-
ODATA-1140 Add
details to HttpResponse
-
ODATA-1214 Annotate
constructor/factory actions
-
ODATA-1358 Detach
textual descriptions from operation restriction terms in Capability vocabulary
-
ODATA-1394 Add
full-fledged support for ISO 8601-1 duration
-
ODATA-1412 Capabilities
vocabulary: Add EntityContainer as annotation target
-
ODATA-1453 Capabilities.SearchRestrictions/UnsupportedExpressions:
description of default value “none” is misleading
-
ODATA-1467 Keep
a CHANGELOG.md, use Semantic Versioning for each vocabulary
-
ODATA-1550 Clarify
whether Validation.AllowedValues can be applied to collection-valued properties
-
ODATA-1600 Functions
and Actions as Interfaces
-
Vocabularies:
NEW
or OPEN without proposal
-
ODATA-1480 Missing
term property Capabilities.NavigationRestrictions/…/ComputeSupported
-
ODATA-1499 Clarify
how to allow/disallow an unbound function in filter/orderby
-
ODATA-1502 Allow
to specify expand query options beyond just nested expands (filter, select, …)
-
ODATA-1512 Delta:
distinguish “soft-deleted” and “hard-deleted” entities
-
ODATA-1513 Clarify
use of read/update restrictions for complex types
-
ODATA-1611 Clarify
where RequiredProperties have to appear
-
ODATA-1612 Capabilities
for creating a relation to an existing entity during insert
-
ODATA-1613 Validation.Minimum,
Validation.Maximum: clarify possible data types
-
ODATA-1627 clarify
usage of Capabilities.IndexableByKey Vs Capabilities.ReadRestrictions.ReadByKeyRestriction.Readable
-
Next meetings [9:50]
-
Wednesday January 24, 2024 during 8-10 PST (17:00-19:00 CET)
-
Wednesday January 31, 2024 during 8-10 PST (17:00-19:00 CET)
-
Wednesday February 07, 2024 during 8-10 PST (17:00-19:00 CET)
-
Wednesday February 14, 2024 during 8-10 PST (17:00-19:00 CET)
-
AOB and wrap up [9:55]
[2] Timeline
-
https://www.oasis-open.org/committees/download.php/71620/TC-Timeline-2024-01-10.docx
|