| Re: [odata] Agenda for OData TC meeting 2013.05.02 |
2 |
2013-05-01 |
| [OASIS Issue Tracker] Commented: (ODATA-301) Guidance around data authorization model and secure authenticated access to an OData Service |
6 |
2013-05-01 |
| Subminor tweak ... ? |
1 |
2013-05-01 |
| Version Control Commit by sdrees |
13 |
2013-05-01 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDEz?= =?UTF-8?B?LTA0LTI1LzI2IE1lZXRpbmcjMzQgRjJG?= =?UTF-8?B?IHVwbG9hZGVk?= |
2 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-31) Section 9.1.3: Describe call choreography for 202 Accepted (Async responses) |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-37) UPSERT: allow PUT and PATCH to the URL of a not yet existing entity to create this entity |
2 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-42) 8.2.5 If-None-Match: clarify use of If-None-Match in data modification or action requests |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-68) Describe representation of ReferenceTypes in responses |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-111) Define supported numeric promotions |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-124) For round-tripping values, what precision must agents support for DateTime(Offset), and are leap seconds permitted? |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-139) New system query option $search for free-text search within an entity set |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-159) Handling inline attachments in requests/responses |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-204) Define namespace versioning policy for XML namespaces |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-222) free-text search within a property |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-228) Specify $search for free-text search within a OData Service and specify $search for free-text search within an entityContainer |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-230) Support use of parameter aliases in $filter and $orderby |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-232) Enhance description of normalization procedures (public comment c201301e00001) |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-244) Support navigation properties on complex types |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-246) IDs should be dereferenceable URIs |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-248) Define required/optional format(s) for OData |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-258) Advertise function imports in service document |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-260) Make explicit that DELETE on an entity may implicitly change links to and from other entities |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-263) Define whether $select=* returns only structural properties or also navigation properties |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-264) Allow omitting parent key(s) in URLs to contained children |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-266) Strengthen the requirements for the URL Attribute in edmx:Reference and edmx:AnnotationReference |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-267) Allow Qualifier attribute on Annotation elements within an Annotations element that does NOT specify a Qualifier attribute |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-270) Collections of Edm.PrimitiveType are problematic in JSON |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-271) Support IsAlwaysBindable through annotation, rather than attribute of function/action |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-274) OData clients should always use PATCH, deprecate PUT |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-275) Clarify whether binding parameters for actions and functions can be nullable |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-276) Fix issues with entity references and rationalize with $links |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-277) Remove Collation attribute |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-279) Define URL conventions for addressing functions and function imports |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-280) Support cast segment in $expand |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-281) Keep second() as integer, introduce FractionalSeconds |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-283) Accept-Charset HTTP Request Header and charset content-type parameter |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-284) Annotating an Annotation |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-285) Section 4.7: explicitly mention which property types allow appending /$value |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-288) Change default decimal Scale to variable |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-292) Questions on POST, PATCH and merge/replace semantics with related entities in composite relationships |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-297) State explicitly if Content-Length is required, and if so, for which request types it is required |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-300) Valid Syntax in JSON samples |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-302) Clarify scope uniqueness for EntityContainer name |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-303) Support abstract entity types without key properties |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-304) Add TargetKey attribute to <PropertyRef> within a <ReferentialConstraint> |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-305) Annotations: introduce path segment to address the count of a collection |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-306) Batch Request processing: Define server behavior, if one or more request(s) didn't succeed |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-307) Return odata.etag in collections also for odata=minimalmetadata |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-308) Clarify whether format parameters odata.metadata and odata.streaming may be ignored by services |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-312) ATOM and JSON formats for Service Document appear to omit information for action imports |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-313) Problem with "Function Overload Resolution" due to null values having ambiguous type |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-315) Entities that may be queryable can be omitted from service document, but then their "url" cannot be specified. |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-318) Explicitly state which calendar Date and DateTimeOffset use |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-319) Allow services to include metadata links and metadata ETags into responses |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-320) Should use /@<annotation-name> to reference applied annotations |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-321) Use consistent naming for headers |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-322) Define how nested service documents are supported |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-324) Support external metadata references in payload |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-325) Clarify what aliases can be used in instance annotations |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-327) Service MUST only return async if return-async is specified |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-328) Remove MinDataServiceVersion (OData-MinVersion) |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-338) Representation of entity references in odata.metadata annotation |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-348) Require the use of <edmx:Include> to pull in specific namespaces from <edmx:Reference> |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-349) CSDL for Collection types is not clear on nullability of elements |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Updated: (ODATA-350) Clearly describe the service documents role, expected usage and responsibility in comparison with $metadata |
2 |
2013-05-01 |
| Half an hour later ... |
1 |
2013-05-01 |
| Voting member status update |
6 |
2013-05-02 |
| [OASIS Issue Tracker] Updated: (ODATA-102) Representing Actions/Functions Bound to Multiple Entities |
2 |
2013-05-02 |
| Version Control Commit by ralfhandl |
63 |
2013-05-02 |
| [OASIS Issue Tracker] Updated: (ODATA-351) Define ID, ReadLink and EditLink in Part 1: Protocol, define representation in Atom and JSON |
5 |
2013-05-02 |
| [OASIS Issue Tracker] Updated: (ODATA-301) Guidance around data authorization model and secure authenticated access to an OData Service |
3 |
2013-05-02 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDEz?= =?UTF-8?B?LTA0LTI1LzI2IE1lZXRpbmcjMzQgRjJG?= =?UTF-8?B?IG1vZGlmaWVk?= |
1 |
2013-05-02 |
| RE: [odata] Groups - Minutes of 2013-04-25/26 Meeting#34 F2F modified |
1 |
2013-05-02 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDEz?= =?UTF-8?B?LTA1LTAyIE1lZXRpbmcjMzUgdXBsb2Fk?= =?UTF-8?B?ZWQ=?= |
1 |
2013-05-02 |
| Processed 38 issues, state now has been updated in JIRA |
1 |
2013-05-02 |
| Your 30-day Public Reviews of OData, OData Atom Format and OData JSON Format have been announced |
1 |
2013-05-02 |
| 30-day Public Review for OData, OData Atom Format and OData JSON Format, V4.0 |
1 |
2013-05-02 |
| [OASIS Issue Tracker] Created: (ODATA-366) Clarify whether server-generated properties can be omitted in POST, even if they are not nullable |
1 |
2013-05-03 |
| [OASIS Issue Tracker] Created: (ODATA-367) Explicitly state that server MAY expand results beyond what's requested with $expand |
1 |
2013-05-03 |
| [OASIS Issue Tracker] Created: (ODATA-368) Deep insert: if server responds with 201 Created it MUST respond with at least the expansion depth of the insert operation |
1 |
2013-05-03 |
| [OASIS Issue Tracker] Created: (ODATA-369) POST to navigation link with binding information leading to a different "parent" is invalid |
1 |
2013-05-03 |
| [OASIS Issue Tracker] Updated: (ODATA-368) Deep insert: if server responds with 201 Created it MUST respond with at least the expansion depth of the insert operation |
2 |
2013-05-03 |
| [OASIS Issue Tracker] Updated: (ODATA-366) Clarify whether server-generated properties can be omitted in POST, even if they are not nullable |
3 |
2013-05-03 |
| [OASIS Issue Tracker] Created: (ODATA-370) Disallow Nullable facet for collection-valued properties |
1 |
2013-05-03 |
| [OASIS Issue Tracker] Commented: (ODATA-370) Disallow Nullable facet for collection-valued properties |
1 |
2013-05-05 |
| [OASIS Issue Tracker] Commented: (ODATA-364) Remove restriction that a property MUST NOT have the same name as its containing type |
10 |
2013-05-06 |
| [OASIS Issue Tracker] Commented: (ODATA-366) Clarify whether server-generated properties can be omitted in POST, even if they are not nullable |
1 |
2013-05-06 |
| [OASIS Issue Tracker] Commented: (ODATA-346) Order of child elements of <edm:Collection> is significant |
1 |
2013-05-06 |
| [OASIS Issue Tracker] Commented: (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 |
6 |
2013-05-06 |
| [OASIS Issue Tracker] Commented: (ODATA-164) Consider syntax and rules around client specifying custom aggregation functions for rollups |
1 |
2013-05-06 |
| =?UTF-8?B?R3JvdXBzIC0gT0RhdGEgRXh0ZW5zaW9u?= =?UTF-8?B?IGZvciBEYXRhIEFnZ3JlZ2F0aW9uIFZl?= =?UTF-8?B?cnNpb24gNC4wIHVwbG9hZGVk?= |
1 |
2013-05-07 |
| [OASIS Issue Tracker] Updated: (ODATA-164) Consider syntax and rules around client specifying custom aggregation functions for rollups |
1 |
2013-05-07 |
| [OASIS Issue Tracker] Created: (ODATA-371) Clearly describe behavior of PUT for structural and navigation properties |
1 |
2013-05-07 |
| [OASIS Issue Tracker] Created: (ODATA-372) Addressing Derived Types |
1 |
2013-05-07 |
| [OASIS Issue Tracker] Updated: (ODATA-372) Addressing Derived Types |
2 |
2013-05-07 |
| [OASIS Issue Tracker] Created: (ODATA-373) Add boolean expressions that can be used in <edm:If> |
1 |
2013-05-07 |
| [OASIS Issue Tracker] Updated: (ODATA-373) Add boolean expressions that can be used in <edm:If> |
5 |
2013-05-07 |
| [OASIS Issue Tracker] Commented: (ODATA-372) Addressing Derived Types |
3 |
2013-05-07 |
| [OASIS Issue Tracker] Commented: (ODATA-316) Allow omitting properties with null or default values from responses |
2 |
2013-05-07 |
| [OASIS Issue Tracker] Issue Comment Edited: (ODATA-372) Addressing Derived Types |
1 |
2013-05-07 |
| [OASIS Issue Tracker] Created: (ODATA-374) Supporting heterogeneous return types in a service operation response |
1 |
2013-05-07 |
| [OASIS Issue Tracker] Updated: (ODATA-374) Returning heterogeneous types for a function call |
4 |
2013-05-07 |
| [OASIS Issue Tracker] Commented: (ODATA-374) Returning heterogeneous types for a function call |
3 |
2013-05-07 |
| [OASIS Issue Tracker] Created: (ODATA-375) Allow querying collections of complex type instances similar to querying collections of entities |
1 |
2013-05-07 |
| [OASIS Issue Tracker] Updated: (ODATA-165) Support Cross-joins |
3 |
2013-05-07 |
| [OASIS Issue Tracker] Created: (ODATA-376) Navigation link representation for navigation properties of complex type instances |
1 |
2013-05-07 |
| [OASIS Issue Tracker] Updated: (ODATA-152) JSON: Add examples for all request and response types using a consistent sample OData service |
1 |
2013-05-07 |
| [OASIS Issue Tracker] Updated: (ODATA-153) Atom: Add examples for all request and response types using a consistent sample OData service |
2 |
2013-05-07 |
| [OASIS Issue Tracker] Issue Comment Edited: (ODATA-364) Remove restriction that a property MUST NOT have the same name as its containing type |
1 |
2013-05-07 |
| [OASIS Issue Tracker] Updated: (ODATA-364) Explicitly state that the restriction that a property MUST NOT have the same name as its containing type only applies to directly declared properties |
3 |
2013-05-07 |
| TC Admin comments on OData CSPRD01s |
2 |
2013-05-07 |
| [OASIS Issue Tracker] Commented: (ODATA-351) Define ID, ReadLink and EditLink in Part 1: Protocol, define representation in Atom and JSON |
8 |
2013-05-07 |
| [OASIS Issue Tracker] Updated: (ODATA-346) Order of child elements of <edm:Collection> MUST be preserved |
6 |
2013-05-07 |
| Agenda for OData TC meeting 2013.05.09 |
2 |
2013-05-07 |
| [OASIS Issue Tracker] Created: (ODATA-377) Fix broken links in CSD01 documents |
1 |
2013-05-07 |
| [OASIS Issue Tracker] Updated: (ODATA-377) Fix broken links in CSD01 documents (public comment c201305e00001) |
1 |
2013-05-07 |
| [OASIS Issue Tracker] Created: (ODATA-378) Support relative IRIs for ids in JSON |
1 |
2013-05-07 |
| [OASIS Issue Tracker] Updated: (ODATA-219) Detail state and procedures in format agnostic description of In-Stream Error handling |
2 |
2013-05-08 |
| Vacation Absence Request/Notice May 30, June 06 |
1 |
2013-05-08 |
| [OASIS Issue Tracker] Commented: (ODATA-378) Support relative IRIs for ids in JSON |
1 |
2013-05-08 |
| [OASIS Issue Tracker] Updated: (ODATA-378) Support relative IRIs for ids in JSON |
2 |
2013-05-08 |
| Fwd: [odata-comment] Specification of $count for "Delta Responses" |
3 |
2013-05-08 |
| [OASIS Issue Tracker] Updated: (ODATA-377) Fix broken links in CSD01 documents |
2 |
2013-05-08 |
| [OASIS Issue Tracker] Created: (ODATA-379) Ensure consistency and clear description in specification of $count for 'Delta Responses' (public comment c201305e00000) |
1 |
2013-05-08 |
| [OASIS Issue Tracker] Updated: (ODATA-379) Ensure consistency and clear description in specification of $count for 'Delta Responses' (public comment c201305e00000) |
6 |
2013-05-09 |
| [OASIS Issue Tracker] Updated: (ODATA-371) Clearly describe behavior of PUT for structural and navigation properties |
2 |
2013-05-09 |
| [OASIS Issue Tracker] Updated: (ODATA-365) Rename edm:AssertType to edm:Cast and clarify behavior of edm:Cast and cast() |
4 |
2013-05-09 |
| [OASIS Issue Tracker] Commented: (ODATA-364) Explicitly state that the restriction that a property MUST NOT have the same name as its containing type only applies to directly declared properties |
2 |
2013-05-09 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDEz?= =?UTF-8?B?LTA1LTAyIE1lZXRpbmcjMzUgbW9kaWZp?= =?UTF-8?B?ZWQ=?= |
1 |
2013-05-09 |
| [OASIS Issue Tracker] Created: (ODATA-380) Insert a section in protocol (and similar in JSON and ATOM) named "Security Considerations" |
1 |
2013-05-09 |
| [OASIS Issue Tracker] Updated: (ODATA-380) Insert a section in protocol (and similar in JSON and ATOM) named 'Security Considerations' (before 'Conformance') |
6 |
2013-05-09 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDEz?= =?UTF-8?B?LTA1LTA5IE1lZXRpbmcjMzYgdXBsb2Fk?= =?UTF-8?B?ZWQ=?= |
2 |
2013-05-09 |
| Processed 16 issues in meeting#36 on 2013-05-09 |
1 |
2013-05-09 |
| =?UTF-8?B?R3JvdXBzIC0gRXZlbnQgIk9EYXRhIFRD?= =?UTF-8?B?IFdlZWtseSBNZWV0aW5nIiBtb2RpZmll?= =?UTF-8?B?ZA==?= |
1 |
2013-05-09 |
| 5th OData TC face-to-face meeting |
1 |
2013-05-09 |
| [OASIS Issue Tracker] Issue Comment Edited: (ODATA-301) Guidance around data authorization model and secure authenticated access to an OData Service |
1 |
2013-05-11 |
| [OASIS Issue Tracker] Created: (ODATA-381) Hanging paragraphs - all current csprd01 documents |
1 |
2013-05-11 |
| [OASIS Issue Tracker] Created: (ODATA-382) Conformance clauses need to refer to sections defining aspects of conformance and do so uniformly |
1 |
2013-05-11 |
| [OASIS Issue Tracker] Commented: (ODATA-381) Hanging paragraphs - all current csprd01 documents |
3 |
2013-05-11 |
| [OASIS Issue Tracker] Created: (ODATA-383) Examples, distinguishing from normative text |
1 |
2013-05-11 |
| [OASIS Issue Tracker] Commented: (ODATA-382) Conformance clauses need to refer to sections defining aspects of conformance and do so uniformly |
1 |
2013-05-11 |
| [OASIS Issue Tracker] Created: (ODATA-384) Normative text needs to be typographically distinct from examples |
1 |
2013-05-11 |
| [OASIS Issue Tracker] Created: (ODATA-385) Overview wording suggestion |
1 |
2013-05-11 |
| [OASIS Issue Tracker] Created: (ODATA-386) odata-v4.0-csprd01-part1-protocol, 3 Data Model, appears to be an unnumbered list of definitions, with annotations defined in a separate subsection - suggest new format, etc. |
1 |
2013-05-11 |
| [OASIS Issue Tracker] Issue Comment Edited: (ODATA-381) Hanging paragraphs - all current csprd01 documents |
1 |
2013-05-12 |
| [OASIS Issue Tracker] Commented: (ODATA-385) Overview wording suggestion |
1 |
2013-05-12 |
| [OASIS Issue Tracker] Issue Comment Edited: (ODATA-385) Overview wording suggestion |
1 |
2013-05-12 |
| [OASIS Issue Tracker] Created: (ODATA-387) Replace (at least) the second example in Section 13 of the CSDL document (public comment c201305e00002) |
1 |
2013-05-13 |
| Fwd: [odata-comment] DiscontinuedProducts is a really bad example |
1 |
2013-05-13 |
| [OASIS Issue Tracker] Updated: (ODATA-387) Replace (at least) the second example in Section 13 of the CSDL document (public comment c201305e00002) |
6 |
2013-05-13 |
| [OASIS Issue Tracker] Created: (ODATA-388) Rename "when" to "odata.when" and allow it in added/changed entities |
1 |
2013-05-13 |
| [OASIS Issue Tracker] Updated: (ODATA-388) Rename "when" to "odata.when" and allow it in added/changed entities |
2 |
2013-05-13 |
| [OASIS Issue Tracker] Created: (ODATA-389) Use odata.kind values "Entity" and "deletedEntity" instead of "Entry" and "deletedEntry" |
1 |
2013-05-13 |
| [OASIS Issue Tracker] Updated: (ODATA-389) Use odata.kind values "Entity" and "deletedEntity" instead of "Entry" and "deletedEntry" |
1 |
2013-05-13 |
| [OASIS Issue Tracker] Updated: (ODATA-389) JSON: use odata.kind values "Entity" and "deletedEntity" |
2 |
2013-05-13 |
| [OASIS Issue Tracker] Commented: (ODATA-389) JSON: use odata.kind values "Entity" and "deletedEntity" |
1 |
2013-05-13 |
| [OASIS Issue Tracker] Updated: (ODATA-389) JSON: use odata.kind values "Entity" and "deletedEntity", Atom: use metadata:link and metadata:deleted-link |
1 |
2013-05-13 |
| [OASIS Issue Tracker] Commented: (ODATA-387) Replace (at least) the second example in Section 13 of the CSDL document (public comment c201305e00002) |
8 |
2013-05-13 |
| [OASIS Issue Tracker] Updated: (ODATA-385) Overview wording suggestion |
5 |
2013-05-13 |
| [OASIS Issue Tracker] Commented: (ODATA-386) odata-v4.0-csprd01-part1-protocol, 3 Data Model, appears to be an unnumbered list of definitions, with annotations defined in a separate subsection - suggest new format, etc. |
2 |
2013-05-13 |
| [OASIS Issue Tracker] Updated: (ODATA-384) Normative text needs to be typographically distinct from examples |
6 |
2013-05-13 |
| [OASIS Issue Tracker] Updated: (ODATA-383) Examples, distinguishing from normative text |
1 |
2013-05-13 |
| [OASIS Issue Tracker] Updated: (ODATA-382) Conformance clauses need to refer to sections defining aspects of conformance and do so uniformly |
4 |
2013-05-13 |
| [OASIS Issue Tracker] Updated: (ODATA-316) Allow omitting properties with null or default values from responses |
1 |
2013-05-14 |
| [OASIS Issue Tracker] Updated: (ODATA-376) Navigation link representation for navigation properties of complex type instances |
1 |
2013-05-14 |
| [OASIS Issue Tracker] Commented: (ODATA-383) Examples, distinguishing from normative text |
3 |
2013-05-14 |
| [OASIS Issue Tracker] Commented: (ODATA-377) Fix broken links in CSD01 documents |
2 |
2013-05-14 |
| [OASIS Issue Tracker] Updated: (ODATA-370) Disallow Nullable facet for collection-valued properties |
1 |
2013-05-14 |
| [OASIS Issue Tracker] Updated: (ODATA-369) POST to navigation link with binding information leading to a different "parent" is invalid |
1 |
2013-05-14 |
| [OASIS Issue Tracker] Updated: (ODATA-367) Explicitly state that server MAY expand results beyond what's requested with $expand |
1 |
2013-05-14 |
| [OASIS Issue Tracker] Updated: (ODATA-375) Allow querying collections of complex type instances similar to querying collections of entities |
2 |
2013-05-14 |
| [OASIS Issue Tracker] Updated: (ODATA-386) odata-v4.0-csprd01-part1-protocol, 3 Data Model, appears to be an unnumbered list of definitions, with annotations defined in a separate subsection - suggest new format, etc. |
1 |
2013-05-14 |
| [OASIS Issue Tracker] Commented: (ODATA-346) Order of child elements of <edm:Collection> MUST be preserved |
4 |
2013-05-14 |
| [OASIS Issue Tracker] Created: (ODATA-390) Additional description of use of GeoJSON in OData JSON. |
1 |
2013-05-14 |
| [OASIS Issue Tracker] Commented: (ODATA-390) Additional description of use of GeoJSON in OData JSON. |
2 |
2013-05-14 |
| [OASIS Issue Tracker] Issue Comment Edited: (ODATA-346) Order of child elements of <edm:Collection> MUST be preserved |
3 |
2013-05-14 |
| =?UTF-8?B?R3JvdXBzIC0gVEMgdGltZWxpbmUgdXBs?= =?UTF-8?B?b2FkZWQ=?= |
1 |
2013-05-15 |
| Agenda for OData TC meeting 2013.05.16 |
4 |
2013-05-15 |
| [OASIS Issue Tracker] Issue Comment Edited: (ODATA-390) Additional description of use of GeoJSON in OData JSON. |
1 |
2013-05-15 |
| [OASIS Issue Tracker] Created: (ODATA-391) Add query function defined(PropertyPath) to determine whether an instance has a dynamic property of that name |
1 |
2013-05-15 |
| [OASIS Issue Tracker] Updated: (ODATA-391) Add query function defined(PropertyPath) to determine whether an instance has a property of that name |
1 |
2013-05-15 |
| =?UTF-8?B?cmVxdWVzdCBhIGxlYXZlIG9mIGFic2Vu?= =?UTF-8?B?Y2U=?= |
1 |
2013-05-15 |
| RE: [odata] request a leave of absence |
1 |
2013-05-15 |
| [OASIS Issue Tracker] Created: (ODATA-392) Expanded Navigation Properties should be implicitly added to $select |
1 |
2013-05-15 |
| [OASIS Issue Tracker] Commented: (ODATA-388) Rename "when" to "odata.when" and allow it in added/changed entities |
1 |
2013-05-16 |
| [OASIS Issue Tracker] Updated: (ODATA-390) Additional description of use of GeoJSON in OData JSON. |
3 |
2013-05-16 |
| [OASIS Issue Tracker] Updated: (ODATA-388) Remove "when" from OData-specific items in delta responses |
4 |
2013-05-16 |
| [OASIS Issue Tracker] Commented: (ODATA-391) Add query function defined(PropertyPath) to determine whether an instance has a property of that name |
3 |
2013-05-16 |
| [OASIS Issue Tracker] Created: (ODATA-393) Allow querying collections of primitive type instances similar to other collections |
1 |
2013-05-16 |
| [OASIS Issue Tracker] Created: (ODATA-394) Introduce path segment /$all for search on service and entity container level |
1 |
2013-05-16 |
| [OASIS Issue Tracker] Updated: (ODATA-394) Introduce path segment /$all for search on service and entity container level |
4 |
2013-05-16 |
| [OASIS Issue Tracker] Created: (ODATA-395) Simplify rule for implicit values of enumeration members |
1 |
2013-05-16 |
| [OASIS Issue Tracker] Commented: (ODATA-395) Simplify rule for implicit values of enumeration members |
6 |
2013-05-16 |
| [OASIS Issue Tracker] Created: (ODATA-396) Partner attribute of edm:NavigationProperty is a property path, not a SimpleIdentifier |
1 |
2013-05-16 |
| =?UTF-8?B?R3JvdXBzIC0gT0RhdGEgQVRPTSBGb3Jt?= =?UTF-8?B?YXQgVmVyc2lvbiA0LjAgdXBsb2FkZWQ=?= |
3 |
2013-05-16 |
| =?UTF-8?B?R3JvdXBzIC0gT0RhdGEgSlNPTiBGb3Jt?= =?UTF-8?B?YXQgVmVyc2lvbiA0LjAgdXBsb2FkZWQ=?= |
3 |
2013-05-16 |
| =?UTF-8?B?R3JvdXBzIC0gT0RhdGEgQ29yZSBQYXJ0?= =?UTF-8?B?IDM6IENTREwsIFZlcnNpb24gNC4wIHVw?= =?UTF-8?B?bG9hZGVk?= |
4 |
2013-05-16 |
| =?UTF-8?B?R3JvdXBzIC0gT0RhdGEgQ29yZSBQYXJ0?= =?UTF-8?B?IDI6IFVSTCBDb252ZW50aW9ucywgVmVy?= =?UTF-8?B?c2lvbiA0LjAgdXBsb2FkZWQ=?= |
3 |
2013-05-16 |
| =?UTF-8?B?R3JvdXBzIC0gT0RhdGEgQ29yZSBQYXJ0?= =?UTF-8?B?IDE6IFByb3RvY29sLCBWZXJzaW9uIDQu?= =?UTF-8?B?MCB1cGxvYWRlZA==?= |
3 |
2013-05-16 |
| [OASIS Issue Tracker] Commented: (ODATA-393) Allow querying collections of primitive type instances similar to other collections |
2 |
2013-05-16 |
| [OASIS Issue Tracker] Updated: (ODATA-393) Allow querying collections of primitive type instances similar to other collections |
4 |
2013-05-16 |
| [OASIS Issue Tracker] Created: (ODATA-397) Lazy loading of Annotations: Add optional Attribute "TargetNamespace" to edmx:IncludeAnnotations element |
1 |
2013-05-16 |
| [OASIS Issue Tracker] Updated: (ODATA-397) Lazy loading of Annotations: Add optional Attribute "TargetNamespace" to edmx:IncludeAnnotations element |
6 |
2013-05-16 |
| Regrets for May 16th 2013 |
1 |
2013-05-16 |
| [OASIS Issue Tracker] Issue Comment Edited: (ODATA-351) Define ID, ReadLink and EditLink in Part 1: Protocol, define representation in Atom and JSON |
1 |
2013-05-16 |
| =?UTF-8?B?R3JvdXBzIC0gQWN0aW9uIEl0ZW0gIlBy?= =?UTF-8?B?ZXBhcmUgV29ya2luZyBEcmFmdCAwMSAo?= =?UTF-8?B?V0QwMSkgdmVyc2lvbiBvZiBPRGF0YSBF?= =?UTF-8?B?eHRlbnNpb24gZm9yIFRlbXBvcmFsIERh?= =?UTF-8?B?dGEiIE1vZGlmaWVk?= |
1 |
2013-05-16 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDEz?= =?UTF-8?B?LTA1LTA5IE1lZXRpbmcjMzYgbW9kaWZp?= =?UTF-8?B?ZWQ=?= |
1 |
2013-05-16 |
| =?UTF-8?B?R3JvdXBzIC0gQWN0aW9uIEl0ZW0gIlBy?= =?UTF-8?B?ZXBhcmUgV29ya2luZyBEcmFmdCAwMSAo?= =?UTF-8?B?V0QwMSkgdmVyc2lvbiBvZiBPRGF0YSBF?= =?UTF-8?B?eHRlbnNpb24gZm9yIFhNTCBEYXRhIiBN?= =?UTF-8?B?b2RpZmllZA==?= |
2 |
2013-05-16 |
| =?UTF-8?B?R3JvdXBzIC0gQWN0aW9uIEl0ZW0gIlBy?= =?UTF-8?B?ZXBhcmUgV29ya2luZyBEcmFmdCAwMSAo?= =?UTF-8?B?V0QwMSkgdmVyc2lvbiBvZiBPRGF0YSBF?= =?UTF-8?B?eHRlbnNpb24gZm9yIEpTT04gRGF0YSIg?= =?UTF-8?B?TW9kaWZpZWQ=?= |
1 |
2013-05-16 |
| Processed 16 issues in meeting#37 on 2013-05-16 |
1 |
2013-05-16 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDEz?= =?UTF-8?B?LTA1LTE2IE1lZXRpbmcjMzcgdXBsb2Fk?= =?UTF-8?B?ZWQ=?= |
1 |
2013-05-16 |
| =?windows-1252?Q?Starter_Document_for_What=92s_New_in_OData_Version_4?= =?windows-1252?Q?=2E0?= |
1 |
2013-05-16 |
| [OASIS Issue Tracker] Updated: (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 |
1 |
2013-05-16 |
| [OASIS Issue Tracker] Updated: (ODATA-396) Partner attribute of edm:NavigationProperty is a property path, not a SimpleIdentifier |
2 |
2013-05-16 |
| [OASIS Issue Tracker] Updated: (ODATA-392) Expanded Navigation Properties should be implicitly added to $select |
1 |
2013-05-17 |
| =?UTF-8?B?R3JvdXBzIC0gV2hhdMKScyBOZXcgaW4gTw==?= =?UTF-8?B?RGF0YSBWZXJzaW9uIDQuMCB1cGxvYWRl?= =?UTF-8?B?ZA==?= |
2 |
2013-05-17 |
| [OASIS Issue Tracker] Updated: (ODATA-383) Number all examples in all documents |
5 |
2013-05-17 |
| [OASIS Issue Tracker] Issue Comment Edited: (ODATA-395) Simplify rule for implicit values of enumeration members |
1 |
2013-05-17 |
| [OASIS Issue Tracker] Updated: (ODATA-391) Add query function isdefined(PropertyPath) to determine whether an instance has a property of that name |
3 |
2013-05-18 |
| validity of next links in paginated results |
2 |
2013-05-18 |
| JSON on it's way to a first class citizen in the std-world |
1 |
2013-05-19 |
| [OASIS Issue Tracker] Created: (ODATA-398) Defined "GetByID" canonical function |
1 |
2013-05-20 |
| [OASIS Issue Tracker] Updated: (ODATA-398) Defined "GetByID" canonical function as a path segment |
1 |
2013-05-20 |
| [OASIS Issue Tracker] Updated: (ODATA-398) Define "GetByID" canonical function as a path segment |
1 |
2013-05-20 |
| [OASIS Issue Tracker] Commented: (ODATA-398) Define "GetByID" canonical function as a path segment |
2 |
2013-05-21 |
| [OASIS Issue Tracker] Issue Comment Edited: (ODATA-398) Define "GetByID" canonical function as a path segment |
1 |
2013-05-21 |
| [OASIS Issue Tracker] Commented: (ODATA-394) Introduce path segment /$all for search on service and entity container level |
1 |
2013-05-21 |
| [OASIS Issue Tracker] Updated: (ODATA-295) Services should be able to "advertise" what form of change tracking they support |
6 |
2013-05-21 |
| [OASIS Issue Tracker] Created: (ODATA-399) Describe expected life cycle management of next-links inside 11.2.4.7 Server-Driven Paging |
1 |
2013-05-21 |
| [OASIS Issue Tracker] Updated: (ODATA-399) Describe expected life cycle management of next-links inside 11.2.4.7 Server-Driven Paging |
4 |
2013-05-21 |
| [OASIS Issue Tracker] Created: (ODATA-400) Allow JSON values also in common expressions, not only in parameter aliases |
1 |
2013-05-21 |
| [OASIS Issue Tracker] Commented: (ODATA-295) Services should be able to "advertise" what form of change tracking they support |
2 |
2013-05-21 |
| [OASIS Issue Tracker] Updated: (ODATA-398) Define canonical function as a path segment that allows retrieving an entity by its id |
5 |
2013-05-22 |
| [OASIS Issue Tracker] Commented: (ODATA-398) Define canonical function as a path segment that allows retrieving an entity by its id |
6 |
2013-05-22 |
| Version Control Commit by martin.zurmuehl |
1 |
2013-05-22 |
| Agenda for OData TC meeting 2013.05.23 |
1 |
2013-05-22 |
| Update: Agenda for OData TC meeting 2013.05.23 |
6 |
2013-05-22 |
| [OASIS Issue Tracker] Updated: (ODATA-400) Allow JSON values also in common expressions, not only in parameter aliases |
3 |
2013-05-22 |
| [OASIS Issue Tracker] Created: (ODATA-401) Replace "substringof" canonical function with "contains" |
1 |
2013-05-22 |
| [OASIS Issue Tracker] Created: (ODATA-402) Require services to support $expand on navigation properties |
1 |
2013-05-22 |
| [OASIS Issue Tracker] Created: (ODATA-403) Meachnism to advertise conformance level |
1 |
2013-05-22 |
| [OASIS Issue Tracker] Updated: (ODATA-403) Mechanism to advertise conformance level of OData services |
5 |
2013-05-22 |
| [OASIS Issue Tracker] Updated: (ODATA-402) Require services to support $expand on navigation properties |
4 |
2013-05-22 |
| [OASIS Issue Tracker] Created: (ODATA-404) Make Capabilities vocabulary a part of OData 4.0 |
1 |
2013-05-22 |
| [OASIS Issue Tracker] Updated: (ODATA-126) Metadata as an OData service |
2 |
2013-05-22 |
| Update 2: Agenda for OData TC meeting 2013.05.23 |
1 |
2013-05-23 |
| [OASIS Issue Tracker] Created: (ODATA-405) Deep Updates (public comment c201305e00008) |
1 |
2013-05-23 |
| [OASIS Issue Tracker] Created: (ODATA-406) Attribute ContainsTarget (public comment c201305e00009) |
1 |
2013-05-23 |
| [OASIS Issue Tracker] Created: (ODATA-407) Navigation Properties in Complex Types (public comment c201305e00012) |
1 |
2013-05-23 |
| Three public comments mapped to issues and to be inserted into todays agenda as usual |
1 |
2013-05-23 |
| [OASIS Issue Tracker] Updated: (ODATA-407) Navigation Properties in Complex Types (public comment c201305e00012) |
5 |
2013-05-23 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDEz?= =?UTF-8?B?LTA1LTE2IE1lZXRpbmcjMzcgbW9kaWZp?= =?UTF-8?B?ZWQ=?= |
1 |
2013-05-23 |
| [OASIS Issue Tracker] Updated: (ODATA-405) Deep Updates (public comment c201305e00008) |
2 |
2013-05-23 |
| [OASIS Issue Tracker] Updated: (ODATA-316) Services MUST NOT omit structural properties from responses unless asked to do so via $select |
1 |
2013-05-23 |
| [OASIS Issue Tracker] Updated: (ODATA-404) Make Capabilities vocabulary a part of OData 4.0 |
3 |
2013-05-23 |
| Processed 28 issues in meeting#38 on 2013-05-23 |
1 |
2013-05-23 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDEz?= =?UTF-8?B?LTA1LTIzIE1lZXRpbmcjMzggdXBsb2Fk?= =?UTF-8?B?ZWQ=?= |
1 |
2013-05-23 |
| [OASIS Issue Tracker] Created: (ODATA-408) 11.2.3 OData services MAY/SHOULD/MUST expose their data model |
1 |
2013-05-23 |
| [OASIS Issue Tracker] Created: (ODATA-409) 11.3.3.1 conflicts with conformance for intermediate and advanced OData |
1 |
2013-05-23 |
| [OASIS Issue Tracker] Updated: (ODATA-408) 11.2.3 OData services MAY/SHOULD/MUST expose their data model |
1 |
2013-05-23 |
| [OASIS Issue Tracker] Updated: (ODATA-409) 11.3.3.1 conflicts with conformance for intermediate and advanced OData |
1 |
2013-05-23 |
| [OASIS Issue Tracker] Updated: (ODATA-406) Attribute ContainsTarget (public comment c201305e00009) |
3 |
2013-05-23 |
| [OASIS Issue Tracker] Updated: (ODATA-401) Replace "substringof" canonical function with "contains" |
2 |
2013-05-23 |
| [OASIS Issue Tracker] Updated: (ODATA-395) Simplify rule for implicit values of enumeration members |
2 |
2013-05-23 |
| [OASIS Issue Tracker] Created: (ODATA-410) Consider moving terms OptimisticConcurrencyControl and AcceptableMediaTypes from Core to Capabilities |
1 |
2013-05-24 |
| [OASIS Issue Tracker] Commented: (ODATA-405) Deep Updates (public comment c201305e00008) |
5 |
2013-05-24 |
| [OASIS Issue Tracker] Commented: (ODATA-406) Attribute ContainsTarget (public comment c201305e00009) |
2 |
2013-05-24 |
| [OASIS Issue Tracker] Issue Comment Edited: (ODATA-406) Attribute ContainsTarget (public comment c201305e00009) |
2 |
2013-05-24 |
| [OASIS Issue Tracker] Created: (ODATA-411) Reconsider placement and semantics of OnDelete element |
1 |
2013-05-24 |
| [OASIS Issue Tracker] Updated: (ODATA-287) Consider adding a primitive type that corresponds with JSR 310 (JDK 1.8 time API) ZonedDateTime |
2 |
2013-05-28 |
| [OASIS Issue Tracker] Created: (ODATA-412) Consistent representation of empty values |
1 |
2013-05-28 |
| [OASIS Issue Tracker] Updated: (ODATA-290) Check the use of SHOULD vs. MUST in Protocol spec |
1 |
2013-05-28 |
| [OASIS Issue Tracker] Created: (ODATA-413) Conformance clause, part 3, CSDL, appears to require conformance to other parts of the specification. |
1 |
2013-05-28 |
| [OASIS Issue Tracker] Created: (ODATA-414) Fix syntax for deleting links to support containment |
1 |
2013-05-28 |
| [OASIS Issue Tracker] Created: (ODATA-415) Use of "MUST," "MAY," "SHOULD," etc in Part 3 CSDL definitions |
1 |
2013-05-28 |
| [OASIS Issue Tracker] Commented: (ODATA-412) Consistent representation of empty values |
1 |
2013-05-28 |
| [OASIS Issue Tracker] Created: (ODATA-416) Non-normative text in conformance 3.1 of part 1 |
1 |
2013-05-29 |
| Agenda for OData TC meeting 2013.05.30 |
4 |
2013-05-29 |
| [OASIS Issue Tracker] Commented: (ODATA-410) Consider moving terms OptimisticConcurrencyControl and AcceptableMediaTypes from Core to Capabilities |
1 |
2013-05-29 |
| [OASIS Issue Tracker] Updated: (ODATA-410) Consider moving terms OptimisticConcurrencyControl and AcceptableMediaTypes from Core to Capabilities |
1 |
2013-05-29 |
| [OASIS Issue Tracker] Updated: (ODATA-412) Consistent representation of empty values |
5 |
2013-05-29 |
| [OASIS Issue Tracker] Commented: (ODATA-415) Use of "MUST," "MAY," "SHOULD," etc in Part 3 CSDL definitions |
1 |
2013-05-29 |
| [OASIS Issue Tracker] Updated: (ODATA-220) Please consider the restoration of DateTime (without offset) |
2 |
2013-05-29 |
| [OASIS Issue Tracker] Created: (ODATA-417) Define content negotiation and default format for paths ending in /$value, /$count, /$metadata and /$batch |
1 |
2013-05-29 |
| [OASIS Issue Tracker] Created: (ODATA-418) Navigation Property Binding for Named Entities |
1 |
2013-05-29 |
| [OASIS Issue Tracker] Updated: (ODATA-418) EntitySet attribute or NavigationPropertyBinding child elements for Named Entities (edm:Entity) |
6 |
2013-05-29 |
| [OASIS Issue Tracker] Created: (ODATA-419) Specify ETag handling more precisely |
1 |
2013-05-29 |
| [OASIS Issue Tracker] Created: (ODATA-420) Response codes 404 and 405: MUST instead of SHOULD |
1 |
2013-05-29 |
| [OASIS Issue Tracker] Updated: (ODATA-411) Reconsider placement and semantics of OnDelete element |
4 |
2013-05-29 |
| [OASIS Issue Tracker] Updated: (ODATA-419) Specify ETag handling more precisely |
1 |
2013-05-29 |
| [OASIS Issue Tracker] Created: (ODATA-421) Remove odata.kind from JSON and add metadata URL templates for link, deletedLink, and deletedEntity |
1 |
2013-05-29 |
| [OASIS Issue Tracker] Created: (ODATA-422) Add metadata URL to representations of entity references, define format for collections of references |
1 |
2013-05-29 |
| [OASIS Issue Tracker] Updated: (ODATA-413) Replace conformance clauses in URL and CSDL with references to Protocol |
1 |
2013-05-29 |
| [OASIS Issue Tracker] Updated: (ODATA-420) Response codes 404 and 405: MUST instead of SHOULD |
5 |
2013-05-29 |
| [OASIS Issue Tracker] Updated: (ODATA-381) Hanging paragraphs - all current csprd01 documents |
1 |
2013-05-29 |
| [OASIS Issue Tracker] Commented: (ODATA-418) EntitySet attribute or NavigationPropertyBinding child elements for Named Entities (edm:Entity) |
2 |
2013-05-30 |
| [OASIS Issue Tracker] Commented: (ODATA-420) Response codes 404 and 405: MUST instead of SHOULD |
2 |
2013-05-30 |
| [OASIS Issue Tracker] Updated: (ODATA-414) Fix syntax for deleting links to support containment |
5 |
2013-05-30 |
| [OASIS Issue Tracker] Updated: (ODATA-262) Specify how OData services can be protected against cross-site request forgery (CSRF or XSRF) |
1 |
2013-05-30 |
| [OASIS Issue Tracker] Commented: (ODATA-380) Insert a section in protocol (and similar in JSON and ATOM) named 'Security Considerations' (before 'Conformance') |
1 |
2013-05-30 |
| [OASIS Issue Tracker] Issue Comment Edited: (ODATA-420) Response codes 404 and 405: MUST instead of SHOULD |
1 |
2013-05-30 |
| [OASIS Issue Tracker] Commented: (ODATA-262) Specify how OData services can be protected against cross-site request forgery (CSRF or XSRF) |
2 |
2013-05-30 |
| [OASIS Issue Tracker] Updated: (ODATA-417) Define content negotiation and default format for paths ending in /$value, /$count, /$metadata and /$batch |
6 |
2013-05-30 |
| [OASIS Issue Tracker] Commented: (ODATA-413) Replace conformance clauses in URL and CSDL with references to Protocol |
1 |
2013-05-30 |
| Processed 15 issues in meeting#39 on 2013-05-30 |
1 |
2013-05-30 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDEz?= =?UTF-8?B?LTA1LTIzIE1lZXRpbmcjMzggbW9kaWZp?= =?UTF-8?B?ZWQ=?= |
1 |
2013-05-30 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDEz?= =?UTF-8?B?LTA1LTMwIE1lZXRpbmcjMzkgdXBsb2Fk?= =?UTF-8?B?ZWQ=?= |
1 |
2013-05-30 |
| [OASIS Issue Tracker] Updated: (ODATA-422) Add metadata URL to representations of entity references, define format for collections of references |
4 |
2013-05-31 |
| [OASIS Issue Tracker] Updated: (ODATA-421) Remove odata.kind from JSON and add metadata URL templates for link, deletedLink, and deletedEntity |
3 |
2013-05-31 |
| [OASIS Issue Tracker] Created: (ODATA-423) Rename edm:Entity to edm:NamedEntity and its Type attribute to EntityType |
1 |
2013-05-31 |
| [OASIS Issue Tracker] Commented: (ODATA-423) Rename edm:Entity to edm:NamedEntity and its Type attribute to EntityType |
1 |
2013-05-31 |
| [OASIS Issue Tracker] Updated: (ODATA-423) Rename edm:Entity to edm:SingletonEntity and its Type attribute to EntityType |
1 |
2013-05-31 |
