Bug
- [ODATA-734] - Unicode Facet is inadequate
- [ODATA-741] - Mismatch between explanatory text and URL in example 96
- [ODATA-744] - 11.2.3: representation of null for single-valued primitive properties
- [ODATA-745] - Sections 4.5.5, 7.3, and 7.4: is odata.nextLink allowed for all collections?
- [ODATA-748] - Section 4.5.4: odata.count needs to be allowed for all collections
- [ODATA-749] - What should service return when attempting to related two entities that are already related?
- [ODATA-750] - Explicitly mention the @ sign in instance annotations
- [ODATA-751] - Clarification of Edm.NavigationPropertyPath and Edm.PropertyPath
- [ODATA-752] - Bug in example 47
- [ODATA-753] - Minor typo in references to bound function calls
- [ODATA-755] - Construction rule for canonical URL is incomplete
- [ODATA-756] - Clarify when odata.metadataEtag will be returned
- [ODATA-758] - Example 81: wrong parameter style
- [ODATA-766] - 8.2.4 and 8.2.5 should refer to RFC7232 (public comment c201501e00001)
- [ODATA-770] - 18.2: incomplete description of annotation name format
- [ODATA-773] - Qualifiers for instance annotations: JSON Format
- [ODATA-774] - Qualifiers for annotations: Preference odata.include-annotations
- [ODATA-775] - Should allow use of parameter aliases for key lookup
- [ODATA-777] - Clarify multiply/divide duration by number
- [ODATA-778] - Example in section 11.7.3.1, "Referencing Requests in a Change Set", should use JSON, not ATOM
- [ODATA-779] - Org.OData.Core.V1 defines Term IsURL but references it as IsUrl
- [ODATA-787] - Clarify how odata.Include-annotations preference affects odata.* markup
- [ODATA-788] - Clarify precidence rules for odata.include-annotations preference
- [ODATA-790] - Bug in example 70
- [ODATA-795] - Support annotations for expanded references
- [ODATA-796] - Add annotation to specify whether additional properties may be returned for an entity
- [ODATA-797] - Org.OData.Capabilities.V1 term property FilterRestrictions/RequiresFilter has wrong facets
- [ODATA-800] - Media streams section does not reference the AtomPub spec
- [ODATA-803] - Collection-valued property: Define default value for nullable facet
- [ODATA-806] - Wrong description in capabilities vocabulary in term SearchRestrictions
- [ODATA-807] - Don't need TargetId in a deleted link for a to 0..1 relationship
- [ODATA-810] - Part 3, 14.1.5 uses IsURI instead of IsURL
- [ODATA-819] - 10.2.2: Clarify whether enum types allow multiple members with the same value
- [ODATA-821] - 14.2.1 Attribute Target: targeting of nested properties of structured types
- [ODATA-822] - Async Batch Request: Bug in example 85
- [ODATA-826] - Wrong Target attribute value in Edm.Metadata.Annotation/Target navigation property
- [ODATA-830] - Header OData-EntityId: when required
- [ODATA-831] - MetadataService.edmx: type of OpenType property should be Edm.Boolean
- [ODATA-832] - 15.6: typo in diagram (Function/Action swapped)
- [ODATA-835] - 5.1: PATCH missing in list of operations that do not allow system query options
- [ODATA-848] - ABNF construction rules don't permit empty functionParameters
- [ODATA-852] - 8.3.1: superfluous text paragraph 3, sentence 1
- [ODATA-853] - 8.3.3: last sentence should use "header" instead of "preference"
- [ODATA-858] - Define meaning of MaxLength for String, Binary, and Stream
- [ODATA-869] - Explicitly state the location of the Content-ID header in a change set
- [ODATA-870] - Round-off description for creating related entities when creating an entity
- [ODATA-877] - Must delta responses continue to track "orphaned" entities?
- [ODATA-878] - Example 84: EntityContainer is a Singleton, not an EntitySet
- [ODATA-885] - Permissions should apply to more than just properties
- [ODATA-891] - Misleading reference to "open" in description of $select
- [ODATA-892] - Clarify dynamic properties support in $filter, $orderby, $expand
- [ODATA-893] - Is @odata.type required on update of a derived type
- [ODATA-896] - Reconsider guidance on odata.count position (public comment c201512e00001)
- [ODATA-899] - Type cast segment after $all
- [ODATA-903] - ABNF: should allow cast segment following collection of complex types
- [ODATA-908] - Header Content-Type shouldn't be required for media types
- [ODATA-912] - Clarify what clients should do if they see an unknown/invalid expression for a known annotation term.
- [ODATA-913] - Should we specify a default response format if neither Accept header nor system query $format are specified
- [ODATA-917] - 5.1.1.2.1 Addition and 5.1.1.2.2 Subtraction: Date add/sub Duration is DateTimeOffset - but in which time zone?
- [ODATA-931] - Typo in Example 32: An entity container aggregates entity sets, singletons, action imports, and function imports.
- [ODATA-932] - Typo in example 44: missing T in duration literal
- [ODATA-934] - Clarify invoking an action with no parameters
- [ODATA-936] - CSDL errata02 11.1.3 Type Definition Facets references nonexistent standard vocabulary
New Feature
- [ODATA-850] - Improve document structure for functions used in common expressions
Task
- [ODATA-915] - Be consistent in citing rules around namespace qualification
- [ODATA-916] - Define what services (and clients?) do with unknown format parameters
Improvement
- [ODATA-479] - Allow Content-ID referencing in request bodies for inserting links to newly created entities
- [ODATA-656] - Requesting clarity on payload ordering constraints for clients
- [ODATA-731] - Explicitly state that JSON service documents may contain annotations
- [ODATA-732] - Add enumeration member "Write" to "Permission" type
- [ODATA-733] - Clarify handling of cycles in Extends for EntityContainers
- [ODATA-740] - Let's update the GeoJSON reference (again)
- [ODATA-742] - Usage of domain contoso.com and term name contoso in examples
- [ODATA-746] - 12.2.3: IsComposable - clarify what is allowed even if set to false
- [ODATA-754] - Clarify that numeric enum values are serialized as strings
- [ODATA-761] - 11.5.4.1 Invoking an Action: Location header for 201 Created responses
- [ODATA-762] - Section 8.5: clarify that @odata.bind:null is valid for updating of 0..1 navigation properties
- [ODATA-765] - Example 77 (invoking an action): show complex parameters
- [ODATA-767] - Adapt Acknowledgements
- [ODATA-768] - Remove superfluous text after references
- [ODATA-769] - 5.2 Model Versioning: allow adding a new term to the model
- [ODATA-771] - Exponential notation for Edm.Decimal values in JSON payloads
- [ODATA-776] - Clarify function invocation
- [ODATA-780] - indexof: what to return if the second argument does not appear in the first argument
- [ODATA-781] - substring: what to return if the start index is outside the first argument string, or the desired length exceeds the remaining string length
- [ODATA-782] - Example 57: choose better example
- [ODATA-783] - Is it intentional that mindatetime/maxdatetime/now don't permit %-encoded parentheses in ABNF?
- [ODATA-784] - Need to specify the behaviour of arithmetic operators on Decimal type
- [ODATA-785] - Numeric promotion (on overflow) across "number type families" is undesirable.
- [ODATA-789] - Primitive type Edm.Decimal is ill-defined in regard to Precision
- [ODATA-791] - 11.2.5.2 System Query Option $orderby: specify order of Edm.Boolean and Edm.Geo
- [ODATA-793] - Expand * on complex type
- [ODATA-794] - 11.4.2.2: Create Related Entities When Creating an Entity
- [ODATA-801] - Consider supporting negative scale for decimal type
- [ODATA-802] - Define a vocabulary for odata.* annotations
- [ODATA-815] - Clarify that the values of the format parameters odata.metadata etc. are case-insensitive
- [ODATA-823] - Header Content-Transfer-Encoding not used in HTTP
- [ODATA-825] - AnnotationPath expression: traversal of multiple collection-valued scalar or navigation properties
- [ODATA-828] - Update I-JSON reference
- [ODATA-837] - Example 28: replace $deltaToken with a valid custom query option
- [ODATA-840] - Add example for $expand=NavProp/$count
- [ODATA-847] - Clarification: use of Schema namespace aliases within URLs
- [ODATA-865] - 14.2.1 Attribute Target: complete list of externally targetable CSDL elements
- [ODATA-880] - 14.5.10: edm:Null can have edm:Annotation child elements
- [ODATA-882] - Mismatch between 11.2.6 Requesting Related Entities and 11.2.7 Requesting Entity References
- [ODATA-930] - Ensure that errata03 vocabularies have explicit Nullable facet for collection-typed properties
Sub-task
- [ODATA-808] - Minor changes to new OnlyDeclaredProperties annotation
- [ODATA-861] - Define behavior when neither accept header or $format query parameter is specified
Edit/Copy Release Notes
The text area below allows the project release notes to be edited and copied to another document.