Bug
- [ODATA-674] - Specify navigation property binding combined with containment
- [ODATA-760] - Add to depth restrictions to Capabilities Vocabulary
- [ODATA-817] - Add client-side function odata.matchesPattern
- [ODATA-955] - Specifying odata.type on a collection of entities
- [ODATA-1008] - Consider deprecating symbolic "max" length
- [ODATA-1013] - Selected nav props in a defining query should specify interest in added/deleted links of a delta query
- [ODATA-1017] - Extend FilterExpressionRestrictions with "SearchExpression"
- [ODATA-1021] - Are additional values needed for the reason property of a removed Annotation
- [ODATA-1022] - Add an example of a delta payload used in a PATCH request to the Delta Payload section
- [ODATA-1024] - 5.1.1.5.7 substring: explicitly state that the index N (second parameter value) is zero-based
- [ODATA-1025] - Treatment of same query option in multiple "spellings"
- [ODATA-1027] - Support instance annotations in $orderby
- [ODATA-1028] - 4.3.4 and 4.4: clarify resolution of relative URLs in system query option $id
- [ODATA-1030] - Consider support of NavigationPropertyBindings to non-contained nav props
- [ODATA-1032] - Define comparison for numeric value exceptions
- [ODATA-1035] - 10.13: Simplify context URL for Property Value
- [ODATA-1036] - 10.7/8: Simplify context URL for "all operations in schema"
- [ODATA-1043] - Clarify purpose of context URL
- [ODATA-1046] - Add JSON format for Batch
- [ODATA-1050] - Change sets: do not require the same content type for all request in a change set
- [ODATA-1051] - Further simplify JSON Batch Format
- [ODATA-1054] - Part 1 Protocol: Add recommendations for Vary header
- [ODATA-1057] - Add path segment /$each
- [ODATA-1066] - Consider supporting optional operation parameters
- [ODATA-1074] - Support Functions with /$each and define the representation for collection-valued actions and functions with /$each
- [ODATA-1075] - Introduce operator for checking whether a collection is a subset or equal to another collection
- [ODATA-1076] - If-Match: align wording with RFC7232
- [ODATA-1077] - Include atomicityGroup in JSON Batch Response
- [ODATA-1078] - What happens if lambda variable name matches a (complex) property name?
- [ODATA-1084] - Rule searchWord is too restrictive
- [ODATA-1086] - AppliesTo semantics are not normative
- [ODATA-1090] - Clarify text about referential constraint for navigation properties on complex types
- [ODATA-1111] - Structural properties: default for $Nullable is false in CSDL JSON
New Feature
- [ODATA-999] - Consider adding support for 'aliases' on Entity sets, Singletons and Properties
- [ODATA-1002] - Add build in functions operating on collections of primitive (and complex?) types
- [ODATA-1003] - Allow casting of entities and complex type instances to arbitrary structural type
- [ODATA-1019] - Add term Core.ComputedDefaultValue
- [ODATA-1049] - Content referencing in batch requests
- [ODATA-1058] - Add ability to annotate revisions with information on all elements
- [ODATA-1083] - Add annotation expressions for arithmetic operators
Task
- [ODATA-1015] - Reference Atom format from Version 4.01 documents?
- [ODATA-1103] - Special values of temporal types (public comment c201708e0003)
Improvement
- [ODATA-615] - Allow PATCH and DELETE with /$filter=@... on collections to modify or delete all (and only) the matching entities
- [ODATA-836] - Allow applying actions to a filtered collection of entities
- [ODATA-920] - Specify overflow for int data types (-INF, INF, NaN)
- [ODATA-950] - Clarify what requests can be delta enabled
- [ODATA-994] - consider replacing SchemaVersion header with $SchemaVersion query option, or root URL versioning
- [ODATA-1016] - 11.2.9: clarify /$count segment and system query options
- [ODATA-1018] - Allow $expand, $select and $filter with modifying requests that return a collection in combination with return=representation to specify the response shape
- [ODATA-1020] - Remove / in reference in instance annotation in filter and orderby expression
- [ODATA-1023] - Provide stable anchors to all sections
- [ODATA-1026] - Clarify when $it is required
- [ODATA-1029] - 5.1.1.10.2: clarify that all() is always true if applied to an empty collection
- [ODATA-1033] - Interoperability issue when using escaped slash/backslash in URLs
- [ODATA-1034] - Support the notion of a collection of name/value pairs where the type of the value is known
- [ODATA-1037] - Add tagging term Core.Deprecated to mark deprecated model elements
- [ODATA-1039] - Relax constraints on namespace names
- [ODATA-1042] - Cast annotation expression and Unicode facet
- [ODATA-1045] - Disallow propagation of Accept header on batch requests to individual requests within the batch
- [ODATA-1047] - Rename $IsCollection to $Collection
- [ODATA-1048] - Clarify server-driven paging requirement
- [ODATA-1053] - URL conventions document should have non-normative examples if primitive value syntax
- [ODATA-1056] - Key-as-Segment with Referential Constraints
- [ODATA-1061] - Allow key expressions in Path constructs within annotations
- [ODATA-1063] - Allow $format and custom query options for all requests
- [ODATA-1065] - Generalize Edm.AnyPath to be a path to any model element and rename it to Edm.ModelElementPath
- [ODATA-1080] - $each as wildcard for keys
- [ODATA-1081] - Remove restriction on overriding of annotations on type definitions
- [ODATA-1087] - Discourage names differing only in case
- [ODATA-1094] - Apply expression: allow all URL functions with prefix odata.
- [ODATA-1097] - 14.4.1.1 Path Syntax: add odata.mediaETag
- [ODATA-1115] - Default values for $Precision and $Scale
Sub-task
- [ODATA-1014] - How does client find out if implicit parameter aliases are supported?
Edit/Copy Release Notes
The text area below allows the project release notes to be edited and copied to another document.