Export - CSV (All fields)
Export - CSV (Current fields)
ODATA-875
Use of $ref for referencing elements in a JSON Schema
Translate @Core.Description annotations into JSON Schema description keywordsODATA-862
Represent all type references as JSON Schema types/references
Add annotations for Min/Max/Pattern
Translate edmx:Reference/edmx:Include into a schema reference
Nullable as anyOf or as OData-specific keyword
Represent primitive types as JSON Schema formats
Representation of Precision and Scale
Add term to Capabilities vocabulary for supported metadata formatsODATA-589
Add a JSON version of the Metadata document
Support for HTTP verb tunnelling is essential because client libraries may not support PATCHODATA-372
Addressing Derived Types
specifiying selected properties in metadataurl is broken
Accept the application of 61 of the 64 issues applied in the latest work product revisions in one grouping motion
Remove requirement that annotations come after all defined properties in CSDL
Remove edm:documentation element from [CSDL]
Allow only true and false as boolean values, remove values 1 and 0, make values case-sensitive, all-lowercase
Second parameter of the canonical search function should not allow search expressions
Use GeoJSON in JSON and GML in Atom to represent geo types
Review the changes in the latest version of Working DraftsODATA-355
Define how property paths are represented in key part of URL
Make Edm. prefix required when referring to built-in types
Remove <CollectionType> and <TypeRef> elements
Part II: Review results for OData JSON Format Version 4.0
Clearly describe the service documents role, expected usage and responsibility in comparison with $metadata
CSDL for Collection types is not clear on nullability of elements
Require the use of <edmx:Include> to pull in specific namespaces from <edmx:Reference>
Specify which nested query options can be used when expanding only references, and adapt syntax
Software change mode artifacts 101 - Rewrite of current 6.1.2 The Type Attribute and 6.2 into single subsection
Ensure consistent placement and delegation of descritions for presentations of primitive values
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?
Can we get rid of the optional trailing 'L'/'l' for int64 numbers
How to retrieve both the entity references as well as the count of a collection referenced by a navigation property?
$inlinecount and $count, do we need both? Could we use $count in select clause as well?
Representation of entity references in odata.metadata annotation
Review results for OData JSON Format Version 4.0
Be more generous on accepting values for the $format query option
Review results for OData ATOM Format Version 4.0
Integrate conformance concept with careful consideration of versioning semantics (into protocol work product)
Visualize high level EDM overview through means of small diagrams to aid the reader on understanding base terms
Ensure comparability and emphasize differences in directly grokable way for all formats (currently only ATOM and JSON)
Ensure that high level grouping expressions like eg. 'create operations' are easily mapped to real actions (HTTP methods, OData expectations)
Define whether null values come first or last with $orderby asc
Approve Editoral Changes
Remove MinDataServiceVersion (OData-MinVersion)
Service MUST only return async if return-async is specified
include-annotations should allow inclusion (or exclusion) of specific terms
Clarify what aliases can be used in instance annotations
Support external metadata references in payload
InlineCount should just be boolean
Define how nested service documents are supported
Use consistent naming for headers
Should use /@<annotation-name> to reference applied annotations
Allow services to include metadata links and metadata ETags into responses
Explicitly state which calendar Date and DateTimeOffset use
Services select a default set of properties in absence of $select
Entities that may be queryable can be omitted from service document, but then their "url" cannot be specified.
Please clarify the meaning of filter functions applied to DateTimeOffset values
Problem with "Function Overload Resolution" due to null values having ambiguous type
ATOM and JSON formats for Service Document appear to omit information for action imports
Example JSON in CSDL "10.5.3.2 Advertising Currently Available Functions within a Payload" is out of date
Second CSDL example fails to set IsDefaultEntityContainer="true" in accordance with section 12.1.2
CSDL section "The edm:Schema" element should mention edm:Action.
Clarify whether format parameters odata.metadata and odata.streaming may be ignored by services
Return odata.etag in collections also for odata=minimalmetadata
Batch Request processing: Define server behavior, if one or more request(s) didn't succeed
Annotations: introduce path segment to address the count of a collection
Add TargetKey attribute to <PropertyRef> within a <ReferentialConstraint>
Support abstract entity types without key properties
Clarify scope uniqueness for EntityContainer name
Valid Syntax in JSON samples
Should Duration be renamed DayTimeDuration in anticipation that we may wish to add YearMonthDuration at a later point?
Clarify Requesting Changes to entity sets that include Stream properties
State explicitly if Content-Length is required, and if so, for which request types it is required
Change tracking may require server-side state, but client cannot advise server to stop tracking in order to allow server to release resources
Clarify protocol or JSON spec: are servers REQUIRED to support JSON format?
Questions on POST, PATCH and merge/replace semantics with related entities in composite relationships
Check the use of SHOULD vs. MUST in Protocol spec
Change default decimal Scale to variable
Need clarity about JSON encoding of Single and Double (and the applicability or not of ABNF rules) particularly for NaN, INF and -INF
Section 4.7: explicitly mention which property types allow appending /$value
Annotating an Annotation
Accept-Charset HTTP Request Header and charset content-type parameter
Support individual data modification statements within a batch without wrapping in a changeset
Keep second() as integer, introduce FractionalSeconds
Support cast segment in $expand
Define URL conventions for addressing functions and function imports
Introduce vocabulary expression edm:Url
Remove Collation attribute
Fix issues with entity references and rationalize with $links
Clarify whether binding parameters for actions and functions can be nullable
OData clients should always use PATCH, deprecate PUT
Clarify whether derived types MUST introduce new properties
Remove FixedLength facet
Support IsAlwaysBindable through annotation, rather than attribute of function/action
Collections of Edm.PrimitiveType are problematic in JSON
Separate Functions and Actions
Use http://docs.oasis-open.org/odata/ns/edm as the EDM namespace URL
Allow Qualifier attribute on Annotation elements within an Annotations element that does NOT specify a Qualifier attribute
Strengthen the requirements for the URL Attribute in edmx:Reference and edmx:AnnotationReference
Allow omitting key properties from PUT and PATCH request bodies and from nested entities in deep-insert requests
Allow omitting parent key(s) in URLs to contained children
Define whether $select=* returns only structural properties or also navigation properties
Improve section 10.2.3.8 The $format System Query Option
Make explicit that DELETE on an entity may implicitly change links to and from other entities
Advertise function imports in service document
Define standard client-side function for filling URL templates (RFC6570)
Simplify numeric data types
Selection of individual properties in [ATOM] should not include property name
Clients should be prepared to handle unadvertised properties
Clarify ordering of instance annotations in [ATOM] and [JSON]
Clarify, within [ATOM], that complex types can be annotated
For instance annotations in Atom, "Annotation" element, "Type", "Term" and "Target" attributes should be lower case
"Kind" property should be optional for EntitySets in JSON Service Documents
Define required/optional format(s) for OData
More clearly define extensibility of Formats
IDs should be dereferenceable URIs
any() and all() are missing from Core Part I/Protocol and Core Part 2/URL Conventions
Support navigation properties on complex types
Add client preferences for server-driven paging
Allow Path expressions also for annotations targeting an entity container
Consistently require annotations to be placed at the end of the annotated CSDL element
Better describe, and possible extend, expected behavior of dealing with async $batch requests
Allowing expressions to be passed as parameters to (super) functions
Restrict values of the Qualifier attribute to QualifiedName values
Require type usage to always specify a qualified name for types other than the built-in primitive types
Define maximum length of namespace names and simple identifiers
Limit primitive types allowed as key parts to the "sufficiently discrete" types
Merge Reference and AnnotationReference element
Change $batch response code from 202 Accepted to 200 OK
Enhance description of normalization procedures (public comment c201301e00001)
Define how to specify enumeration values in annotations
Support use of parameter aliases in $filter and $orderby
Allow annotations to target all model elements
Specify $search for free-text search within a OData Service and specify $search for free-text search within an entityContainer
Support of symbolic names in annotations
Clarify that the root of the Path attribute of a <PropertyValue> element is rooted at the containing entity
Define Functions in Schema; reference in Container using FunctionImport.
Fill out Capabilities sections of an OData Service
Specify Service behavior for not implemented functionality
free-text search within a property
Flatten the message element in the JSON Error Represention (Section 4.18 Representing Errors in a Response)
Detail state and procedures in format agnostic description of In-Stream Error handling
Remove doubled last paragraph in section 8.5.2 The Preference-Applied Header
property facets in ValueTerm element
Allow edm:Documentation element in edm:TypeDefinition and edm:Annotations element
Remove hour(), minute() and second() query functions and add corresponding overloads to the hours(), minutes(), and seconds() functions
Find consensus on "Additional artifacts"-section of multi component Work Products (and implement accordingly)
Allow all dynamic expressions of the appropriate type within edm:Collection expressions
Define request body format for Actions in Atom and JSON format specifications
Correct the sample inside section "JSON DeltaQuery Result Example" inside ODQP proposal pages 9/10
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
Replace the term store by service and reduce number of triggerpoints in diagrams in section Client Interaction inside ODQP proposal pages 5/6
Enhancement of "flat heterogeneous" structure definition and reference thereof in section Delta Responses inside ODQP proposal pages 3/4 (and later)
Rephrasing of section Requesting Delta Links in ODQP proposal page 2
Rephrasing of section Delta Links in ODQP proposal page 1/2
Merge TypeAnnotation and ValueAnnotation into Annotation
Define namespace versioning policy for XML namespaces
Specify Operator Precedence more clearly
Custom Mapping to Atom Elements not defined
Allow specifying a list of acceptable media types for media entities and named resource properties
Handling of metadata:type attribute
$expand should be allowed to return only ids for already seen objects
Allow Type="Any" and Type="Collection(Any)" for NavigationProperty elements
Define standard functions for edm:Apply element
Remove sections 15.2.6 FunctionReference and 15.2.12 ParameterReference
Simplify entity set qualification rules for NavigationPropertyBinding
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
Allow function imports to return entities from a different service
Define vocabulary term as a replacement for StoreGeneratedPattern attribute
Create subsections for attributes consistently as appropriate throughout [CSDL] document
Remove primitive type Edm.Float as a synonym for Edm.Single
Remove NavigationPropertyBinding
Use <Property> element also for NavigationProperty
Need to remove references to associations and associationsets from protocol doc
Multiple navigationpropertybindings for the same navigation property should be prohibited
Nullable attribute should be required to be false for collection valued navigation properties.
Relationships in CSDL examples should include Partner attribute
The same navigation property should not be specified in multiple $expands
Define the term "model"
Referencing/reusing a model element from a different schema does not require to "include" this schema via a Using element
Remove Extends attribute from EntityContainer element
Adapt OData inter document references to new work product structuring of core
Enhance abstract, distinguish its content from 1st paragraph of introduction and edit the payload object listing in 2nd para of 1 Introduction
Allow entities to be members of multiple entity sets
Re-Order Ref-Entries in Section 1.2 Normative References
Define IsAlwaysBindable attribute for FunctionImport element
Core Part 2: 1 Introduction, 1.1 Terminology, 1.2 Normative References and 3 ServiceRootURL somehow mixed up in view "final version"
Define Action values for OnDelete element
EntitySet may be qualified with namespace or alias and EntityContainer
Enhance facility listing for editing in Overview
Core Part 1: 1.1 Terminology and 1.2 Normative References somehow mixed up in view "final version"
Representation of named entities in the service document
Correlate batch request and response parts via the Content-Id header
1.1 Terminology and 1.2 Normative References somehow mixed up in view "final version"
Inconsistent lifted operators for $filter
Consider syntax and rules around client specifying custom aggregation functions for rollups
Clarify, in OData Protocol, that $skip and $top are not allowed to be appended to a next link
Define OASIS XML namespaces for data: and metadata: in Atom payloads
Clarify and if possible add directions for 'stranded' readers in the ending note of section 1 Introduction
{"errorMessages":["jqlTooComplex"],"errors":{}}
[{"id":-1,"name":"My open issues","jql":"assignee = currentUser() AND resolution = Unresolved order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-2,"name":"Reported by me","jql":"reporter = currentUser() order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-4,"name":"All issues","jql":"order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-5,"name":"Open issues","jql":"resolution = Unresolved order by priority DESC,updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-9,"name":"Done issues","jql":"statusCategory = Done order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-3,"name":"Viewed recently","jql":"issuekey in issueHistory() order by lastViewed DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-6,"name":"Created recently","jql":"created >= -1w order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-7,"name":"Resolved recently","jql":"resolutiondate >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-8,"name":"Updated recently","jql":"updated >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false}]
0.3
0