Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled
on Wednesday September
13, 2023 during 8-10 am PDT (17:00-19:00 CEST).
For TC timeline, see [2].
Feel free to suggest additions or modifications.
Thanks.
[1] Agenda
- Roll call [8:00]
-
- Approve agenda [8:05]
- Approve minutes from previous meeting(s) [8:10 am]
-
-
Data Aggregation [8:10]
- CSD04 Public Review ended on August 17, 2023
- Public Review Comments: https://lists.oasis-open.org/archives/odata-comment/202308/threads.html
- Comment Resolution Log: https://www.oasis-open.org/committees/document.php?document_id=71270&wg_abbrev=odata
- List
of Non-Material Changes: https://www.oasis-open.org/committees/document.php?document_id=71318&wg_abbrev=odata
-
-
- RAPID
Profile for OData [8:15]
- Pull
Requests
- Issues
-
Issues [8:20]
- V4.02
(and V4.01 Errata 01): RESOLVED -
editors needed
- ODATA-1133 Part
1 protocol clause 1.3 Entity is unclear on template usage
- 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-1547 Recursive
complex types must be nullable
- 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
- V4.02 (and V4.01 Errata 01): APPLIED
- ODATA-1323 Clarify
representation of GEO literals and streams in annotations (XML, JSON)
- ODATA-1353 Clarity
for “@odata.type” in request payloads
- ODATA-1360 Clarify
that clients have to do content-ID replacing to interpret Location headers in batch results
- ODATA-1380 11.4.1.2
Handling of DateTimeOffset Values: replace “i.e. UTC” with “for example UTC”
- ODATA-1385 Add
TypecastSegmentSupported to ReadRestrictions
- ODATA-1410 $expand:
clarify that property paths must
not appear twice
- ODATA-1411 $expand:
Discrepancy in argument descriptions
- ODATA-1413 Clarification
of response to a request against a delta link
- ODATA-1417 Inconsistencies
in OData-CSDL section 14.2.2
- ODATA-1419 Use
of Core.ContentID by clients if service does not reference Core vocabulary
- ODATA-1420 Path
evaluation for annotations targeting annotations
- ODATA-1422 Clarify
$select behavior for stream properties
- ODATA-1429 Clarify
applicability of $expand options
- ODATA-1430 Clarify
handling of null values for complex-typed properties
- ODATA-1432 Clarify
wording in Section 7.2, Type Facets
- ODATA-1433 Clarify
applicability of lambda operators to complex-typed collections
- ODATA-1434 List
of recommended navigation property bindings is incomplete.
- ODATA-1437 11.4.9.4
Update a Collection Property: reference section 11.4.11 Positional Inserts
- ODATA-1446 Clarify
usage of Edm.Stream-typed function and action return types
- ODATA-1450 Key
with PropertyRef using navigation path incompatible with Protocol 11.4.2 “Create an Entity”
- ODATA-1456 Navigation
path from instance to lambda operator
- ODATA-1464 Redundant
section 14.4.4.3 Function odata.matchesPattern
- ODATA-1465 Clarification:
Delete supported for Nullable single-valued navigation properties
- ODATA-1469 Clarify
$select behavior for properties of “null” instances
- ODATA-1470 Clarify
value of @odata.mediaContentType if
stream is null
- ODATA-1472 Clarify:
PATCH should allow changing type on nested complex type
- ODATA-1476 JSON
batch body encoding for “text” content types may cause conversion errors or data loss
- ODATA-1478 7.2.3
Precision: clarify absence of $Precision for DateTimeOffset
- ODATA-1481 Allow
Edm.Stream for non-binding action and function parameters
- ODATA-1482 Clarify
response to batch request that fails before “OData processing”
- ODATA-1485 Clarify
canonical URLs for stream properties
- ODATA-1486 Section
4.3: Correct references to ABNF rules
- ODATA-1487 broken
link in “References” section
- ODATA-1491 Inconsistency
in example 16.1, entity type Product
- ODATA-1493 OData-URL
5.1.1.15 does not explain example 106 in 5.1.1.14.4
- ODATA-1495 Remove
statement about format of media streams
- ODATA-1497 13.6
Function Import: annotations allowed but not mentioned
- ODATA-1498 Clarify
where collection of primitive type can be used
- ODATA-1500 Why
is function “matchesPattern” written in camelCase?
- ODATA-1501 Annotations
targeting contained singletons
- ODATA-1508 Missing
annotation namespace in example 8
- ODATA-1518 Extend
[OData-Protocol, example 18] with properties from derived types
- ODATA-1520 Central
definition for type-cast and term-cast segments
- ODATA-1521 Case
statement ambiguous with timeOfDay values
- ODATA-1524 Clarify
key-as-segment representation for Duration and EnumValue
- ODATA-1525 Clarify
context URL for response to $expand=*
- ODATA-1530 Specify
when and how stream valued properties are included
- ODATA-1531 14.1.2
Applicability: clarify that “Property” means “structural property” and excludes navigation properties
- ODATA-1536 ODATA
4.01. 16.1 Example CSDL has missing alias
- ODATA-1539 Clarify
decoding of plus character in URLs
- ODATA-1541 Forward
slashes in /$filter segments
- ODATA-1546 Clarify
/$value segment appended to function returning a primitive value
- ODATA-1562 Clarify
uniqueness of bound action and function names
- ODATA-1564 Protocol
11.7.7.1 misleading text on request formats
- ODATA-1568 Allow
handling of in-stream errors on protocol level
- ODATA-1570 CSDL
XML is defined with reference to XML 1.1 but none of the examples use XML version 1.1 documents
- ODATA-1571 Allow
empty entity containers
- ODATA-1576 Consistently
use “instances of structured types” instead of “structured instances”
- ODATA-1577 Consistently
use “entity-id” instead of “entity id”
- ODATA-1578 Consistently
use “annotated with the term” instead of “annotated with term”
- ODATA-1581 Clarify
duplicate properties in JSON Batch payload
- ODATA-1582 Mention
use of ETag with bound function: only process if binding entity matches ETag
- V4.02 (and V4.01 Errata 01): NEW
or OPEN with champion and proposal
- 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-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-1370 CSDL
Section 12.9 “Parameter” mixing with “overload” causes ambiguity, particularly with regard to parameter ordering
- ODATA-1397 Examples
86 and 87 apply an entity type as term
- ODATA-1398 Improve
text and examples for JSON and multipart batch
- ODATA-1405 /$query
shall allow Content-Type: application/x-www-form-urlencoded
- ODATA-1407 No
way to $select instance annotations on primitive types
- ODATA-1424 OData
4.01 JSON “Delta Responses” doesn’t describe use of “@id” (or “@odata.id”)
for Added/Changed Entity
- ODATA-1435 Conditionally
add an element to a collection
- ODATA-1457 Potential
confusion wrt Content-Type header for media entities
- ODATA-1475 How
to search for double quotes
- ODATA-1503 Instance
annotations of absent complex properties
- ODATA-1506 Allow
index segments in path expressions
- ODATA-1517 [OData-CSDL,
example 64] annotating a navigation property or its addressed resource?
- 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-1553 Clarify
the algorithm for evaluating $compute
- ODATA-1555 Strengthen
definitions for $orderby, $top and $skip
- ODATA-1558 Define
semantics for navigation properties of type Edm.EntityType
- ODATA-1563 URL
4.11, paragraph 2: clarify restriction “that is part of a Boolean _expression_”
- ODATA-1569 Allow
CSDL JSON also for OData versions 2.0 and 3.0
- ODATA-1575 Remove
restriction on Partner navigation
- ODATA-1585 Should
be able to change type when PATCHing an entity
- ODATA-1587 Remove
reference to obsolete GeoJSON document
- ODATA-1588 Allow
creating and linking along a nullable single-valued navigation
- ODATA-1589 /$query
shall allow Content-Type: application/json
- ODATA-1591 OData-Protocol
example 64 is syntactically wrong
- ODATA-1592 correct
vocabulary URIs in CSDL XML examples
- ODATA-1593 11.4.12
Update a Collection of Entities: add examples
- ODATA-1594 Add
support for fuzzy search function within $filter, etc.
- ODATA-1595 Replace
references to RFC7230, RFC7231, and RFC7232 with RFC9110
- ODATA-1596 Allow
Scale=“floating” also in 4.0 responses
- V4.02 (and V4.01 Errata 01): NEW
or OPEN without champion or proposal
- 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-730 Lack
of ordering constraints on delta responses may require clients to buffer (or persist) entire response to process it correctly
- 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-1113 Allow
alternate / native search syntax
- 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-1479 Current
instance/collection is only defined adhoc
- ODATA-1496 clarify
the relationship of the various path _expression_ types
- 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-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-1574 Expand
function results
- ODATA-1579 Allow
references to Core.ContentIDs in batch request URLs
- ODATA-1583 Clarify
representation of context URLs in JSON payloads
- ODATA-1584 Inconsistency
regarding $select=@Namespace.Term
- ODATA-1586 Clarify
create/replace for server-defined dynamic properties
- ODATA-1590 Clarify
where alternate keys can be used
- 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
- 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
- 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
-
Next meetings [9:50]
- Wednesday September 20, 2023 during 8-10 PDT (17:00-19:00 CEST)
-
Wednesday
September 27, 2023 during 8-10 PDT (17:00-19:00 CEST)
-
Wednesday
October 04, 2023 during 8-10 PDT (17:00-19:00 CEST)
-
Wednesday
October 13, 2023 during 8-10 PDT (17:00-19:00 CEST
-
AOB and wrap up [9:55]
|