Bug
- [ODATA-1] - ABNF rule for GUID
- [ODATA-2] - Rules for error message inconsistent to Atom document
- [ODATA-8] - Referenced RFC4646 (has inconsistency in entry) and should be replaced by RFC5646, since the latter obsoleted the former since September 2009
- [ODATA-18] - There are syntax errors in the core OData grammar
- [ODATA-27] - Rules for primitive literals binary, datetimebody, decimal, double, single, string
- [ODATA-28] - Rule for $orderby is broken
- [ODATA-29] - Rule for $filter is broken due to broken rule commonExpr
- [ODATA-30] - Section 8.5.1 says "returns 404 No Content": must be "returns 204 No Content"
- [ODATA-31] - Section 9.1.3: Describe call choreography for 202 Accepted (Async responses)
- [ODATA-35] - 10.2.3.2: replace "open properties" with "dynamic properties" in first sentence, mention them in "*" context
- [ODATA-40] - Incomplete example URL in section 3.1
- [ODATA-44] - Section 20: refer to rules in OData ABNF Construction Rules that define the necessary literals, add ABNF rules if necessary
- [ODATA-45] - Inconsistent use of WSP in many ABNF rules
- [ODATA-46] - Inconsistent use of leading and trailing slashes in URI path parts
- [ODATA-49] - Rules for xxxFunctionCall, boundXxxFuncCall and functionParameterName contain errors
- [ODATA-50] - Inheritance for ComplexType: BaseType and Abstract attributes missing
- [ODATA-51] - Section 3.4: allow at most one annotation per combination of term and qualifier
- [ODATA-52] - Section 3.5 Primitive Types list the primitive types, but doesn't define their meaning
- [ODATA-53] - 9.1.1 The edm:UnderlyingType Attribute: the list of allowed values is missing
- [ODATA-56] - metadata:IsDefaultEntityContainer is not defined
- [ODATA-57] - Remove xs:any and xs:anyAttribute from Informative XSD
- [ODATA-59] - Literal value "Max" for MaxLength attribute is missing
- [ODATA-62] - Specify uniqueness of Association names within a Schema
- [ODATA-63] - 5.2.2 The edm:Alias Attribute should be optional
- [ODATA-64] - Uniqueness of names of EntityContainer child elements
- [ODATA-65] - Remove the edm:Mode attribute
- [ODATA-66] - 10.1 Collection Types: enumeration types are missing from list of types usable with attribute notation
- [ODATA-67] - Describe representation of ReferenceTypes in requests
- [ODATA-68] - Describe representation of ReferenceTypes in responses
- [ODATA-69] - Enumeration types missing in ABNF
- [ODATA-70] - Correct definition of Edm.Time
- [ODATA-72] - Describe any() and all() lambda filter expressions
- [ODATA-77] - Are Edm primitive type names case-insensitive?
- [ODATA-78] - Allow $select to project parts of complex properties
- [ODATA-80] - Add ABNF rules for action parameters in request bodies
- [ODATA-89] - Add normative reference to JSON definition
- [ODATA-94] - 9.1.1: edm:UnderlyingType should be optional in <EnumType> definition
- [ODATA-96] - Need to define semantics, serialization format, etc. for Enums
- [ODATA-101] - 5.3 Representing a Property in a Response: the object wrapper should be named "d"
- [ODATA-103] - 5.4.1 Representing Actions Bound to Multiple Entities: specify treatment of action overloads
- [ODATA-106] - ValueTerms should support primitive types, complex types, and collections, but not entitytypes or collections of entitytypes
- [ODATA-107] - Should OData support a "clock time" (xs:time) datatype?
- [ODATA-111] - Define supported numeric promotions
- [ODATA-112] - DateTime[Offset]: allow 24:00[:00] in time part
- [ODATA-116] - ABNF rule for parameter alias
- [ODATA-118] - XSD references Microsoft namespaces edm/annotation and codegeneration
- [ODATA-120] - 5.1: Add Documentation to list of Schema child elements
- [ODATA-123] - Referential constraint: prose text does not properly reflect case of optional principal
- [ODATA-125] - XML schema for Edmx wrapper constructs edmx:Edmx and edmx:DataServices
- [ODATA-127] - Whitespace in URLs must be percent-encoded
- [ODATA-133] - Attributes defined on odata elements should be in empty namespace
- [ODATA-134] - Multiplicity of FunctionImport ReturnType element
- [ODATA-136] - Correct definition of Edm.Time in [ATOM]
- [ODATA-148] - 10.3.5: Allow PUT for changing to-one or to-zero-or-one relationships between entities
- [ODATA-157] - Specify how client correlates requests within a changeset with responses
- [ODATA-158] - OData ATOM format should require <category> element
- [ODATA-162] - Define OASIS XML namespaces for data: and metadata: in Atom payloads
- [ODATA-163] - Clarify, in OData Protocol, that $skip and $top are not allowed to be appended to a next link
- [ODATA-166] - Inconsistent lifted operators for $filter
- [ODATA-167] - 1.1 Terminology and 1.2 Normative References somehow mixed up in view "final version"
- [ODATA-170] - Core Part 1: 1.1 Terminology and 1.2 Normative References somehow mixed up in view "final version"
- [ODATA-174] - Core Part 2: 1 Introduction, 1.1 Terminology, 1.2 Normative References and 3 ServiceRootURL somehow mixed up in view "final version"
- [ODATA-175] - Define IsAlwaysBindable attribute for FunctionImport element
- [ODATA-176] - Re-Order Ref-Entries in Section 1.2 Normative References
- [ODATA-179] - Adapt OData inter document references to new work product structuring of core
- [ODATA-183] - The same navigation property should not be specified in multiple $expands
- [ODATA-184] - Relationships in CSDL examples should include Partner attribute
- [ODATA-185] - Nullable attribute should be required to be false for collection valued navigation properties.
- [ODATA-186] - Multiple navigationpropertybindings for the same navigation property should be prohibited
- [ODATA-187] - Need to remove references to associations and associationsets from protocol doc
- [ODATA-194] - Inside section 4.1.1 The Version Attribute, the version defined by this spec should be 4.0 and not 1.0 for the EDMX wrapper
- [ODATA-202] - Custom Mapping to Atom Elements not defined
- [ODATA-211] - Correct the sample inside section "JSON DeltaQuery Result Example" inside ODQP proposal pages 9/10
- [ODATA-216] - Allow edm:Documentation element in edm:TypeDefinition and edm:Annotations element
- [ODATA-217] - property facets in ValueTerm element
- [ODATA-218] - Remove doubled last paragraph in section 8.5.2 The Preference-Applied Header
- [ODATA-226] - Clarify that the root of the Path attribute of a <PropertyValue> element is rooted at the containing entity
- [ODATA-231] - Define how to specify enumeration values in annotations
- [ODATA-235] - Limit primitive types allowed as key parts to the "sufficiently discrete" types
- [ODATA-236] - Define maximum length of namespace names and simple identifiers
- [ODATA-237] - Require type usage to always specify a qualified name for types other than the built-in primitive types
- [ODATA-241] - Consistently require annotations to be placed at the end of the annotated CSDL element
- [ODATA-245] - any() and all() are missing from Core Part I/Protocol and Core Part 2/URL Conventions
- [ODATA-250] - For instance annotations in Atom, "Annotation" element, "Type", "Term" and "Target" attributes should be lower case
- [ODATA-251] - Clarify, within [ATOM], that complex types can be annotated
- [ODATA-252] - Clarify ordering of instance annotations in [ATOM] and [JSON]
- [ODATA-253] - Clients should be prepared to handle unadvertised properties
- [ODATA-254] - Selection of individual properties in [ATOM] should not include property name
- [ODATA-261] - Improve section 10.2.3.8 The $format System Query Option
- [ODATA-270] - Collections of Edm.PrimitiveType are problematic in JSON
- [ODATA-272] - Remove FixedLength facet
- [ODATA-273] - Clarify whether derived types MUST introduce new properties
- [ODATA-275] - Clarify whether binding parameters for actions and functions can be nullable
- [ODATA-279] - Define URL conventions for addressing functions and function imports
- [ODATA-285] - Section 4.7: explicitly mention which property types allow appending /$value
- [ODATA-306] - Batch Request processing: Define server behavior, if one or more request(s) didn't succeed
- [ODATA-307] - Return odata.etag in collections also for odata=minimalmetadata
- [ODATA-308] - Clarify whether format parameters odata.metadata and odata.streaming may be ignored by services
- [ODATA-318] - Explicitly state which calendar Date and DateTimeOffset use
- [ODATA-320] - Should use /@<annotation-name> to reference applied annotations
- [ODATA-323] - InlineCount should just be boolean
- [ODATA-324] - Support external metadata references in payload
- [ODATA-325] - Clarify what aliases can be used in instance annotations
- [ODATA-327] - Service MUST only return async if return-async is specified
- [ODATA-330] - Define whether null values come first or last with $orderby asc
- [ODATA-336] - Be more generous on accepting values for the $format query option
- [ODATA-344] - Software change mode artifacts 101 - Rewrite of current 6.1.2 The Type Attribute and 6.2 into single subsection
- [ODATA-345] - Specify which nested query options can be used when expanding only references, and adapt syntax
- [ODATA-348] - Require the use of <edmx:Include> to pull in specific namespaces from <edmx:Reference>
- [ODATA-357] - Use GeoJSON in JSON and GML in Atom to represent geo types
- [ODATA-360] - Remove edm:documentation element from [CSDL]
- [ODATA-361] - Remove requirement that annotations come after all defined properties in CSDL
- [ODATA-363] - specifiying selected properties in metadataurl is broken
- [ODATA-856] - Add annotations for Min/Max/Pattern
- [ODATA-864] - Translate @Core.Description annotations into JSON Schema description keywords
- [ODATA-875] - Use of $ref for referencing elements in a JSON Schema
New Feature
- [ODATA-25] - Support Obtaining Changes (Deltas) from a result.
- [ODATA-32] - Allow filtering of expanded to-many navigation properties
- [ODATA-33] - Allow $filter and $select to refer to annotations as if they were properties
- [ODATA-34] - Control verbosity of $metadata response: include annotations or documentation
- [ODATA-105] - Support instance annotations on errors in JSON
- [ODATA-119] - Allow definition of "simple" types that fix values for facet attributes of primitive types
- [ODATA-126] - Metadata as an OData service
- [ODATA-159] - Handling inline attachments in requests/responses
- [ODATA-201] - Allow specifying a list of acceptable media types for media entities and named resource properties
- [ODATA-222] - free-text search within a property
- [ODATA-239] - Allowing expressions to be passed as parameters to (super) functions
- [ODATA-322] - Define how nested service documents are supported
- [ODATA-589] - Add a JSON version of the Metadata document
Task
- [ODATA-17] - Define which DataServiceVersion this specification defines: 3.0 or 4.0
- [ODATA-19] - New / alternative XML namespaces with OASIS naming convention
- [ODATA-121] - Please clarify whether agents handling DateTimeOffset must preserve the UTC offset
- [ODATA-122] - Please clarify the meaning of filter functions applied to DateTimeOffset values
- [ODATA-124] - For round-tripping values, what precision must agents support for DateTime(Offset), and are leap seconds permitted?
- [ODATA-169] - Representation of named entities in the service document
- [ODATA-191] - Create subsections for attributes consistently as appropriate throughout [CSDL] document
- [ODATA-224] - Fill out Capabilities sections of an OData Service
- [ODATA-248] - Define required/optional format(s) for OData
- [ODATA-286] - Need clarity about JSON encoding of Single and Double (and the applicability or not of ABNF rules) particularly for NaN, INF and -INF
- [ODATA-314] - Please clarify the meaning of filter functions applied to DateTimeOffset values
- [ODATA-356] - Review the changes in the latest version of Working Drafts
- [ODATA-362] - Accept the application of 61 of the 64 issues applied in the latest work product revisions in one grouping motion
- [ODATA-372] - Addressing Derived Types
Improvement
- [ODATA-3] - Use CQL standard for query instead of odata-specific filter query protocol
- [ODATA-4] - Allow DefaultValue facet for FunctionImport Parameter
- [ODATA-5] - Allow Collection(ComplexType) and Collection(PrimitiveType) for Type attribute of ValueTerm
- [ODATA-6] - Use Content-Type: application/json in responses to requests with MaxDataServiceVersion: 2.0
- [ODATA-7] - Minor editorial changes to contribution during import into OASIS template
- [ODATA-11] - date/time values without explicit time zones need further investigation
- [ODATA-12] - create a data type for property names
- [ODATA-13] - A function that returns the current date and time is needed
- [ODATA-14] - add Edm.Date to the OData primitive data types
- [ODATA-15] - precision for functions that have Edm.DateTime or Edm.DateTimeOffset parameters
- [ODATA-20] - Feedback to document revision
- [ODATA-21] - Feedback to document revision
- [ODATA-24] - Simplify how Relationships are expressed in CSDL
- [ODATA-26] - Feedback to document revision
- [ODATA-36] - Make $expand implicit if navigation properties are mentioned in $select
- [ODATA-37] - UPSERT: allow PUT and PATCH to the URL of a not yet existing entity to create this entity
- [ODATA-38] - Recursive $expand and $select
- [ODATA-39] - Make use of additional HTTP response code 428 Precondition Required defined in RFC6585
- [ODATA-41] - Specify which URL formats are acceptable within $batch, and which to prefer
- [ODATA-42] - 8.2.5 If-None-Match: clarify use of If-None-Match in data modification or action requests
- [ODATA-43] - No indicator for optimistic concurrency control on EntityType or EntitySet level
- [ODATA-47] - Consistently format ABNF rules for human readability
- [ODATA-48] - Consistent typographical conventions for OData specifications
- [ODATA-54] - EnumType/@UnderlyingType: allow Edm.String as underlying type for short code lists that are not numeric.
- [ODATA-55] - Allow Documentation for Schema, EnumType, and Member
- [ODATA-58] - Informative XSD for "metadata:" attributes (HasStream, DataServiceVersion, IsDefaultEntityContainer)
- [ODATA-60] - Allow complex properties or components of complex properties as key parts
- [ODATA-61] - Allow complex properties or components of complex properties as parts of a referential constraint
- [ODATA-71] - Improve addition and subtraction Arithmetic Operators to handle time-related data types
- [ODATA-73] - Retrieve the count of related entities together with the base entity
- [ODATA-74] - Explicitly mention dynamic navigation properties
- [ODATA-75] - Schemas can span across more than one CSDL document
- [ODATA-76] - Edm.Decimal is a floating-point type
- [ODATA-79] - PATCH for properties of complex properties
- [ODATA-81] - Rewrite section 3 Service Root URL for clarity and readability
- [ODATA-82] - Rewording of 4 Resource Path first paragraph
- [ODATA-83] - Rewording of 4 Resource Path second paragraph for clarity and readability
- [ODATA-84] - Define which system query options should be supported per URL pattern
- [ODATA-85] - Move section 19 Informative XSD for CSDL into separate XML (text) file
- [ODATA-86] - Allow TypeAnnotation only to target entity types and complex types
- [ODATA-87] - Consider rewording 1 Introduction, second paragraph
- [ODATA-88] - The term EDMX wrapper should be explicitly declared once.
- [ODATA-90] - Section 2.1: define suffix ";odata=xxx" for application/json and the possible values for xxx
- [ODATA-91] - 2.1: explicitly state which format the server will return in response to each given set of headers
- [ODATA-92] - 3.1.1.2: specify behavior if action overloads exist
- [ODATA-93] - 3.4: add introductory paragraph
- [ODATA-95] - ValueTerms should support a default value
- [ODATA-97] - 10.4.2.4 Action Overload Resolution: resolution is done by binding parameter type
- [ODATA-98] - 3.8 Representing Annotations: avoid the undefined terms "internally" and "externally"
- [ODATA-99] - 3.9 Advertisement for a Function or Action: add example and refer to ABNF rules
- [ODATA-100] - 5.1 Response Body: explain security reasons leading to the object wrapper
- [ODATA-102] - Representing Actions/Functions Bound to Multiple Entities
- [ODATA-104] - Consider supporting nullable complex typed properties
- [ODATA-113] - Remove legacy service operations from URL conventions and ABNF
- [ODATA-114] - Allow /$count path suffix also for collection properties
- [ODATA-115] - Inconsistent use of WSP in system query options
- [ODATA-117] - Case-sensitivity of system query options
- [ODATA-128] - Restrict scheme in OData URIs to http and https
- [ODATA-129] - Explicitly mention dynamic navigation properties in [Core]
- [ODATA-130] - Describe canonical $metadata and $batch URLs in URL conventions
- [ODATA-131] - Canonical URL for media resources
- [ODATA-132] - Support /$count in $filter and $orderby
- [ODATA-135] - Instance Annotations in Atom should use metadata:Annotation element
- [ODATA-137] - Normalize percent-encoded values in URIs before applying ABNF rules
- [ODATA-138] - Remove sections 12 Model Functions and 10.4 Row Types including the subsections
- [ODATA-139] - New system query option $search for free-text search within an entity set
- [ODATA-140] - Describe rules for accessing derived entity and complex types in URLs
- [ODATA-141] - Update non-normative ABNF snippets in prose document to match normative ABNF
- [ODATA-142] - Define URL functions geo.distance, geo.length, geo.intersects, and gettotaloffsetminutes
- [ODATA-143] - Define processing order for system query options
- [ODATA-144] - "Scoping" syntax for $aggregate
- [ODATA-145] - X-HTTP-Method request header
- [ODATA-146] - Add example for inlining expanded entities
- [ODATA-147] - Add example for $inlinecount representation
- [ODATA-149] - Self-link for related and inlined feeds
- [ODATA-150] - Add section 9.2.2 describing behavior if HTTP method is not allowed (HTTP 405)
- [ODATA-151] - 8.2.5 If-None-Match: describe reaction to If-None-Match header in read requests
- [ODATA-153] - Atom: Add examples for all request and response types using a consistent sample OData service
- [ODATA-154] - <Record> constructs must provide a <PropertyValue> child element for each non-nullable property of the record type
- [ODATA-155] - Allow functions to take properties as parameters when used in system query options
- [ODATA-156] - Describe behavior when accessing related entities
- [ODATA-160] - Repair Copy and Paste error in 1.1 Terminology i.e. delete the reference entry to OData-CSDL there
- [ODATA-161] - Clarify and if possible add directions for 'stranded' readers in the ending note of section 1 Introduction
- [ODATA-164] - Consider syntax and rules around client specifying custom aggregation functions for rollups
- [ODATA-168] - Correlate batch request and response parts via the Content-Id header
- [ODATA-171] - Enhance facility listing for editing in Overview
- [ODATA-172] - EntitySet may be qualified with namespace or alias and EntityContainer
- [ODATA-173] - Define Action values for OnDelete element
- [ODATA-177] - Allow entities to be members of multiple entity sets
- [ODATA-178] - Enhance abstract, distinguish its content from 1st paragraph of introduction and edit the payload object listing in 2nd para of 1 Introduction
- [ODATA-180] - Remove Extends attribute from EntityContainer element
- [ODATA-181] - Referencing/reusing a model element from a different schema does not require to "include" this schema via a Using element
- [ODATA-182] - Define the term "model"
- [ODATA-188] - Use <Property> element also for NavigationProperty
- [ODATA-189] - Remove NavigationPropertyBinding
- [ODATA-190] - Remove primitive type Edm.Float as a synonym for Edm.Single
- [ODATA-192] - Define vocabulary term as a replacement for StoreGeneratedPattern attribute
- [ODATA-193] - Allow function imports to return entities from a different service
- [ODATA-195] - Simplify entity set qualification rules for NavigationPropertyBinding
- [ODATA-196] - Remove sections 15.2.6 FunctionReference and 15.2.12 ParameterReference
- [ODATA-197] - Define standard functions for edm:Apply element
- [ODATA-198] - Allow Type="Any" and Type="Collection(Any)" for NavigationProperty elements
- [ODATA-199] - $expand should be allowed to return only ids for already seen objects
- [ODATA-200] - Handling of metadata:type attribute
- [ODATA-203] - Specify Operator Precedence more clearly
- [ODATA-204] - Define namespace versioning policy for XML namespaces
- [ODATA-205] - Merge TypeAnnotation and ValueAnnotation into Annotation
- [ODATA-206] - Rephrasing of section Delta Links in ODQP proposal page 1/2
- [ODATA-207] - Rephrasing of section Requesting Delta Links in ODQP proposal page 2
- [ODATA-208] - Enhancement of "flat heterogeneous" structure definition and reference thereof in section Delta Responses inside ODQP proposal pages 3/4 (and later)
- [ODATA-209] - Replace the term store by service and reduce number of triggerpoints in diagrams in section Client Interaction inside ODQP proposal pages 5/6
- [ODATA-210] - Declare OData object/concept name for tombstone before its usage in Result Maintenance and ATOM format describing sections inside ODQP proposal pages 6 and later
- [ODATA-212] - Define request body format for Actions in Atom and JSON format specifications
- [ODATA-213] - Allow all dynamic expressions of the appropriate type within edm:Collection expressions
- [ODATA-214] - Find consensus on "Additional artifacts"-section of multi component Work Products (and implement accordingly)
- [ODATA-215] - Remove hour(), minute() and second() query functions and add corresponding overloads to the hours(), minutes(), and seconds() functions
- [ODATA-219] - Detail state and procedures in format agnostic description of In-Stream Error handling
- [ODATA-221] - Flatten the message element in the JSON Error Represention (Section 4.18 Representing Errors in a Response)
- [ODATA-225] - Define Functions in Schema; reference in Container using FunctionImport.
- [ODATA-227] - Support of symbolic names in annotations
- [ODATA-228] - Specify $search for free-text search within a OData Service and specify $search for free-text search within an entityContainer
- [ODATA-229] - Allow annotations to target all model elements
- [ODATA-230] - Support use of parameter aliases in $filter and $orderby
- [ODATA-232] - Enhance description of normalization procedures (public comment c201301e00001)
- [ODATA-233] - Change $batch response code from 202 Accepted to 200 OK
- [ODATA-234] - Merge Reference and AnnotationReference element
- [ODATA-240] - Better describe, and possible extend, expected behavior of dealing with async $batch requests
- [ODATA-242] - Allow Path expressions also for annotations targeting an entity container
- [ODATA-243] - Add client preferences for server-driven paging
- [ODATA-244] - Support navigation properties on complex types
- [ODATA-246] - IDs should be dereferenceable URIs
- [ODATA-247] - More clearly define extensibility of Formats
- [ODATA-249] - "Kind" property should be optional for EntitySets in JSON Service Documents
- [ODATA-256] - Simplify numeric data types
- [ODATA-257] - Define standard client-side function for filling URL templates (RFC6570)
- [ODATA-258] - Advertise function imports in service document
- [ODATA-260] - Make explicit that DELETE on an entity may implicitly change links to and from other entities
- [ODATA-263] - Define whether $select=* returns only structural properties or also navigation properties
- [ODATA-264] - Allow omitting parent key(s) in URLs to contained children
- [ODATA-265] - Allow omitting key properties from PUT and PATCH request bodies and from nested entities in deep-insert requests
- [ODATA-266] - Strengthen the requirements for the URL Attribute in edmx:Reference and edmx:AnnotationReference
- [ODATA-267] - Allow Qualifier attribute on Annotation elements within an Annotations element that does NOT specify a Qualifier attribute
- [ODATA-268] - Use http://docs.oasis-open.org/odata/ns/edm as the EDM namespace URL
- [ODATA-269] - Separate Functions and Actions
- [ODATA-271] - Support IsAlwaysBindable through annotation, rather than attribute of function/action
- [ODATA-274] - OData clients should always use PATCH, deprecate PUT
- [ODATA-276] - Fix issues with entity references and rationalize with $links
- [ODATA-277] - Remove Collation attribute
- [ODATA-278] - Introduce vocabulary expression edm:Url
- [ODATA-280] - Support cast segment in $expand
- [ODATA-281] - Keep second() as integer, introduce FractionalSeconds
- [ODATA-282] - Support individual data modification statements within a batch without wrapping in a changeset
- [ODATA-283] - Accept-Charset HTTP Request Header and charset content-type parameter
- [ODATA-284] - Annotating an Annotation
- [ODATA-288] - Change default decimal Scale to variable
- [ODATA-290] - Check the use of SHOULD vs. MUST in Protocol spec
- [ODATA-292] - Questions on POST, PATCH and merge/replace semantics with related entities in composite relationships
- [ODATA-296] - Change tracking may require server-side state, but client cannot advise server to stop tracking in order to allow server to release resources
- [ODATA-297] - State explicitly if Content-Length is required, and if so, for which request types it is required
- [ODATA-298] - Clarify Requesting Changes to entity sets that include Stream properties
- [ODATA-299] - Should Duration be renamed DayTimeDuration in anticipation that we may wish to add YearMonthDuration at a later point?
- [ODATA-300] - Valid Syntax in JSON samples
- [ODATA-302] - Clarify scope uniqueness for EntityContainer name
- [ODATA-303] - Support abstract entity types without key properties
- [ODATA-304] - Add TargetKey attribute to <PropertyRef> within a <ReferentialConstraint>
- [ODATA-305] - Annotations: introduce path segment to address the count of a collection
- [ODATA-309] - CSDL section "The edm:Schema" element should mention edm:Action.
- [ODATA-310] - Second CSDL example fails to set IsDefaultEntityContainer="true" in accordance with section 12.1.2
- [ODATA-311] - Example JSON in CSDL "10.5.3.2 Advertising Currently Available Functions within a Payload" is out of date
- [ODATA-312] - ATOM and JSON formats for Service Document appear to omit information for action imports
- [ODATA-313] - Problem with "Function Overload Resolution" due to null values having ambiguous type
- [ODATA-315] - Entities that may be queryable can be omitted from service document, but then their "url" cannot be specified.
- [ODATA-316] - Services select a default set of properties in absence of $select
- [ODATA-319] - Allow services to include metadata links and metadata ETags into responses
- [ODATA-321] - Use consistent naming for headers
- [ODATA-326] - include-annotations should allow inclusion (or exclusion) of specific terms
- [ODATA-328] - Remove MinDataServiceVersion (OData-MinVersion)
- [ODATA-329] - Approve Editoral Changes
- [ODATA-331] - Ensure that high level grouping expressions like eg. 'create operations' are easily mapped to real actions (HTTP methods, OData expectations)
- [ODATA-332] - Ensure comparability and emphasize differences in directly grokable way for all formats (currently only ATOM and JSON)
- [ODATA-333] - Visualize high level EDM overview through means of small diagrams to aid the reader on understanding base terms
- [ODATA-334] - Integrate conformance concept with careful consideration of versioning semantics (into protocol work product)
- [ODATA-335] - Review results for OData ATOM Format Version 4.0
- [ODATA-337] - Review results for OData JSON Format Version 4.0
- [ODATA-338] - Representation of entity references in odata.metadata annotation
- [ODATA-339] - $inlinecount and $count, do we need both? Could we use $count in select clause as well?
- [ODATA-340] - How to retrieve both the entity references as well as the count of a collection referenced by a navigation property?
- [ODATA-341] - Can we get rid of the optional trailing 'L'/'l' for int64 numbers
- [ODATA-342] - Can we relax the requirement of int64 numbers being represented as strings in the JSON Format for integer numbers that don't lose precision in ECMAScript when represented as numbers?
- [ODATA-343] - Ensure consistent placement and delegation of descritions for presentations of primitive values
- [ODATA-349] - CSDL for Collection types is not clear on nullability of elements
- [ODATA-350] - Clearly describe the service documents role, expected usage and responsibility in comparison with $metadata
- [ODATA-352] - Part II: Review results for OData JSON Format Version 4.0
- [ODATA-353] - Remove <CollectionType> and <TypeRef> elements
- [ODATA-354] - Make Edm. prefix required when referring to built-in types
- [ODATA-358] - Second parameter of the canonical search function should not allow search expressions
- [ODATA-359] - Allow only true and false as boolean values, remove values 1 and 0, make values case-sensitive, all-lowercase
- [ODATA-462] - Support for HTTP verb tunnelling is essential because client libraries may not support PATCH
- [ODATA-805] - Add term to Capabilities vocabulary for supported metadata formats
- [ODATA-841] - Representation of Precision and Scale
- [ODATA-842] - Represent primitive types as JSON Schema formats
- [ODATA-843] - Nullable as anyOf or as OData-specific keyword
- [ODATA-845] - Translate edmx:Reference/edmx:Include into a schema reference
- [ODATA-862] - Represent all type references as JSON Schema types/references
Sub-task
- [ODATA-223] - Specify Service behavior for not implemented functionality
- [ODATA-238] - Restrict values of the Qualifier attribute to QualifiedName values
- [ODATA-293] - Clarify protocol or JSON spec: are servers REQUIRED to support JSON format?
- [ODATA-355] - Define how property paths are represented in key part of URL
Edit/Copy Release Notes
The text area below allows the project release notes to be edited and copied to another document.