| Version Control Commit by sdrees |
7 |
2013-04-03 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDEz?= =?UTF-8?B?LTAzLTIxIE1lZXRpbmcjMzAgdXBsb2Fk?= =?UTF-8?B?ZWQ=?= |
1 |
2013-04-03 |
| RE: Voting member status update |
4 |
2013-04-03 |
| [OASIS Issue Tracker] Created: (ODATA-322) Define how nested service documents are supported |
1 |
2013-04-03 |
| [OASIS Issue Tracker] Created: (ODATA-323) InlineCount should just be boolean |
1 |
2013-04-03 |
| [OASIS Issue Tracker] Created: (ODATA-324) Support external metadata references in payload |
1 |
2013-04-03 |
| [OASIS Issue Tracker] Updated: (ODATA-322) Define how nested service documents are supported |
7 |
2013-04-03 |
| [OASIS Issue Tracker] Created: (ODATA-325) Clarify what aliases can be used in instance annotations |
1 |
2013-04-03 |
| [OASIS Issue Tracker] Created: (ODATA-326) include-annotations should allow inclusion (or exclusion) of specific terms |
1 |
2013-04-03 |
| [OASIS Issue Tracker] Updated: (ODATA-317) Allow multiple reads in the same transaction |
2 |
2013-04-03 |
| [OASIS Issue Tracker] Updated: (ODATA-326) include-annotations should allow inclusion (or exclusion) of specific terms |
4 |
2013-04-04 |
| Agenda for OData TC meeting 2013.04.04 |
1 |
2013-04-04 |
| [OASIS Issue Tracker] Commented: (ODATA-317) Allow multiple reads in the same transaction |
3 |
2013-04-04 |
| [OASIS Issue Tracker] Commented: (ODATA-323) InlineCount should just be boolean |
2 |
2013-04-04 |
| [OASIS Issue Tracker] Issue Comment Edited: (ODATA-317) Allow multiple reads in the same transaction |
1 |
2013-04-04 |
| [OASIS Issue Tracker] Commented: (ODATA-298) Clarify Requesting Changes to entity sets that include Stream properties |
6 |
2013-04-04 |
| [OASIS Issue Tracker] Commented: (ODATA-326) include-annotations should allow inclusion (or exclusion) of specific terms |
1 |
2013-04-04 |
| [OASIS Issue Tracker] Commented: (ODATA-321) Use consistent naming for headers |
1 |
2013-04-04 |
| [OASIS Issue Tracker] Commented: (ODATA-313) Problem with "Function Overload Resolution" due to null values having ambiguous type |
1 |
2013-04-04 |
| [OASIS Issue Tracker] Commented: (ODATA-320) Should use /@<annotation-name> to reference applied annotations |
1 |
2013-04-04 |
| =?UTF-8?B?R3JvdXBzIC0gRXZlbnQgIk9EYXRhIFRD?= =?UTF-8?B?IFdlZWtseSBNZWV0aW5nIiBtb2RpZmll?= =?UTF-8?B?ZA==?= |
1 |
2013-04-04 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDEz?= =?UTF-8?B?LTAzLTIxIE1lZXRpbmcjMzAgbW9kaWZp?= =?UTF-8?B?ZWQ=?= |
1 |
2013-04-04 |
| [OASIS Issue Tracker] Updated: (ODATA-306) Batch Request processing: Define server behavior, if one or more request(s) didn't succeed |
3 |
2013-04-04 |
| Ralf Handl has shared a folder with you |
16 |
2013-04-04 |
| [OASIS Issue Tracker] Updated: (ODATA-271) Support IsAlwaysBindable through annotation, rather than attribute of function/action |
2 |
2013-04-04 |
| [OASIS Issue Tracker] Updated: (ODATA-315) Entities that may be queryable can be omitted from service document, but then their "url" cannot be specified. |
4 |
2013-04-04 |
| [OASIS Issue Tracker] Updated: (ODATA-319) Allow services to include metadata links and metadata ETags into responses |
4 |
2013-04-04 |
| [OASIS Issue Tracker] Updated: (ODATA-308) Clarify whether format parameters odata.metadata and odata.streaming may be ignored by services |
2 |
2013-04-04 |
| [OASIS Issue Tracker] Updated: (ODATA-313) Problem with "Function Overload Resolution" due to null values having ambiguous type |
2 |
2013-04-04 |
| [OASIS Issue Tracker] Updated: (ODATA-321) Use consistent naming for headers |
1 |
2013-04-04 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDEz?= =?UTF-8?B?LTA0LTA0IE1lZXRpbmcjMzEgdXBsb2Fk?= =?UTF-8?B?ZWQ=?= |
1 |
2013-04-04 |
| [OASIS Issue Tracker] Commented: (ODATA-315) Entities that may be queryable can be omitted from service document, but then their "url" cannot be specified. |
3 |
2013-04-04 |
| [OASIS Issue Tracker] Created: (ODATA-327) Service MUST only return async if return-async is specified |
1 |
2013-04-04 |
| [OASIS Issue Tracker] Updated: (ODATA-263) Define whether $select=* returns only data properties or also navigation properties |
1 |
2013-04-05 |
| [OASIS Issue Tracker] Updated: (ODATA-320) Should use /@<annotation-name> to reference applied annotations |
2 |
2013-04-05 |
| [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-04-05 |
| [OASIS Issue Tracker] Updated: (ODATA-295) Services should be able to "advertise" what form of change tracking they support |
1 |
2013-04-05 |
| [OASIS Issue Tracker] Updated: (ODATA-255) Consider adding support for requesting flattened results |
1 |
2013-04-05 |
| Please comment on the Atom and JSON format specifications |
1 |
2013-04-05 |
| [OASIS Issue Tracker] Created: (ODATA-328) Remove MinDataServiceVersion (OData-MinVersion) |
1 |
2013-04-05 |
| =?UTF-8?B?R3JvdXBzIC0gT0RhdGEgQ29yZSBQYXJ0?= =?UTF-8?B?IDE6IFByb3RvY29sLCBWZXJzaW9uIDQu?= =?UTF-8?B?MCB1cGxvYWRlZA==?= |
7 |
2013-04-05 |
| [OASIS Issue Tracker] Created: (ODATA-329) Approve Editoral Changes |
1 |
2013-04-05 |
| [OASIS Issue Tracker] Commented: (ODATA-329) Approve Editoral Changes |
1 |
2013-04-06 |
| [OASIS Issue Tracker] Issue Comment Edited: (ODATA-329) Approve Editoral Changes |
2 |
2013-04-06 |
| Review of sky driven revisions of Core, ATOM and JSON working well, right? |
1 |
2013-04-08 |
| Agenda for OData TC meeting 2013.04.11 |
1 |
2013-04-10 |
| Update: Agenda for OData TC meeting 2013.04.11 |
1 |
2013-04-10 |
| [OASIS Issue Tracker] Created: (ODATA-330) Define whether null values come first or last with $orderby asc |
1 |
2013-04-11 |
| [OASIS Issue Tracker] Created: (ODATA-331) Ensure that hig level grouping expressions like eg. 'create actions' are easily mapped to real actions (HTTP methods, OData expectations) |
1 |
2013-04-11 |
| [OASIS Issue Tracker] Updated: (ODATA-331) Ensure that high level grouping expressions like eg. 'create actions' are easily mapped to real actions (HTTP methods, OData expectations) |
1 |
2013-04-11 |
| [OASIS Issue Tracker] Created: (ODATA-332) Ensure comparability and emphasize differences in directly grokable way for all formats (currently only ATOM and JSON) |
1 |
2013-04-11 |
| [OASIS Issue Tracker] Created: (ODATA-333) Visualize high level EDM overview through means of small diagrams to aid the reader on understanding base terms |
1 |
2013-04-11 |
| [OASIS Issue Tracker] Updated: (ODATA-333) Visualize high level EDM overview through means of small diagrams to aid the reader on understanding base terms |
1 |
2013-04-11 |
| meeting support for issue processing |
1 |
2013-04-11 |
| [OASIS Issue Tracker] Created: (ODATA-334) Integrate conformance concept with careful consideration of versioing semantics (into protocol work product) |
1 |
2013-04-11 |
| [OASIS Issue Tracker] Updated: (ODATA-334) Integrate conformance concept with careful consideration of versioning semantics (into protocol work product) |
3 |
2013-04-11 |
| [OASIS Issue Tracker] Created: (ODATA-335) Review results for OData ATOM Format Version 4.0 |
1 |
2013-04-11 |
| [OASIS Issue Tracker] Updated: (ODATA-335) Review results for OData ATOM Format Version 4.0 |
2 |
2013-04-11 |
| [OASIS Issue Tracker] Created: (ODATA-336) Be more generous on accepting values for the $format query option |
1 |
2013-04-11 |
| [OASIS Issue Tracker] Created: (ODATA-337) Review results for OData JSON Format Version 4.0 |
1 |
2013-04-11 |
| [OASIS Issue Tracker] Updated: (ODATA-337) Review results for OData JSON Format Version 4.0 |
4 |
2013-04-11 |
| =?UTF-8?B?R3JvdXBzIC0gT0RhdGEgQVRPTSBGb3Jt?= =?UTF-8?B?YXQgVmVyc2lvbiA0LjAgdXBsb2FkZWQ=?= |
5 |
2013-04-11 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDEz?= =?UTF-8?B?LTA0LTA0IE1lZXRpbmcjMzEgbW9kaWZp?= =?UTF-8?B?ZWQ=?= |
1 |
2013-04-11 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDEz?= =?UTF-8?B?LTA0LTExIE1lZXRpbmcjMzIgdXBsb2Fk?= =?UTF-8?B?ZWQ=?= |
2 |
2013-04-11 |
| [OASIS Issue Tracker] Created: (ODATA-338) Representation of entity references in odata.metadata annotation |
1 |
2013-04-12 |
| [OASIS Issue Tracker] Created: (ODATA-339) $inlinecount and $count, do we need both? Could we use $count in select clause as well? |
1 |
2013-04-12 |
| [OASIS Issue Tracker] Created: (ODATA-340) How to retrieve both the entity references as well as the count of a collection referenced by a navigation property? |
1 |
2013-04-12 |
| [OASIS Issue Tracker] Created: (ODATA-341) Can we get rid of the trailing 'L' for int64 numbers |
1 |
2013-04-12 |
| [OASIS Issue Tracker] Created: (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? |
1 |
2013-04-12 |
| [OASIS Issue Tracker] Updated: (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? |
3 |
2013-04-12 |
| [OASIS Issue Tracker] Commented: (ODATA-304) Add TargetKey attribute to <PropertyRef> within a <ReferentialConstraint> |
1 |
2013-04-12 |
| [OASIS Issue Tracker] Updated: (ODATA-263) Define whether $select=* returns only structural properties or also navigation properties |
3 |
2013-04-12 |
| =?UTF-8?B?R3JvdXBzIC0gT0RhdGEgQ29yZSBQYXJ0?= =?UTF-8?B?IDM6IENTREwsIFZlcnNpb24gNC4wIHVw?= =?UTF-8?B?bG9hZGVk?= |
10 |
2013-04-12 |
| Version Control Commit by ralfhandl |
29 |
2013-04-12 |
| [OASIS Issue Tracker] Created: (ODATA-343) Ensure consistent placement and delegation of descritions for presentations of primitive values |
1 |
2013-04-12 |
| [OASIS Issue Tracker] Created: (ODATA-344) Rewrite of current 6.1.2 The Type Attribute and 6.2 into single subsection |
1 |
2013-04-12 |
| [OASIS Issue Tracker] Updated: (ODATA-344) Rewrite of current 6.1.2 The Type Attribute and 6.2 into single subsection |
1 |
2013-04-12 |
| [OASIS Issue Tracker] Commented: (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? |
3 |
2013-04-12 |
| Version Control Commit by martin.zurmuehl |
4 |
2013-04-12 |
| [OASIS Issue Tracker] Commented: (ODATA-341) Can we get rid of the trailing 'L' for int64 numbers |
2 |
2013-04-12 |
| [OASIS Issue Tracker] Issue Comment Edited: (ODATA-341) Can we get rid of the trailing 'L' for int64 numbers |
2 |
2013-04-12 |
| [OASIS Issue Tracker] Commented: (ODATA-344) Rewrite of current 6.1.2 The Type Attribute and 6.2 into single subsection |
1 |
2013-04-12 |
| [OASIS Issue Tracker] Updated: (ODATA-341) Can we get rid of the optional trailing 'L'/'l' for int64 numbers |
3 |
2013-04-12 |
| [OASIS Issue Tracker] Commented: (ODATA-341) Can we get rid of the optional trailing 'L'/'l' for int64 numbers |
4 |
2013-04-12 |
| [OASIS Issue Tracker] Updated: (ODATA-344) Software change mode artifacts 101 - Rewrite of current 6.1.2 The Type Attribute and 6.2 into single subsection |
2 |
2013-04-15 |
| [OASIS Issue Tracker] Commented: (ODATA-340) How to retrieve both the entity references as well as the count of a collection referenced by a navigation property? |
2 |
2013-04-16 |
| [OASIS Issue Tracker] Created: (ODATA-345) Specify which nested query options can be used when expanding only references, and adapt syntax |
1 |
2013-04-16 |
| [OASIS Issue Tracker] Created: (ODATA-346) Define meaning of collection-valued structural properties to be ordered "List" or "Array" |
1 |
2013-04-16 |
| [OASIS Issue Tracker] Commented: (ODATA-345) Specify which nested query options can be used when expanding only references, and adapt syntax |
3 |
2013-04-16 |
| [OASIS Issue Tracker] Updated: (ODATA-340) How to retrieve both the entity references as well as the count of a collection referenced by a navigation property? |
3 |
2013-04-16 |
| [OASIS Issue Tracker] Commented: (ODATA-335) Review results for OData ATOM Format Version 4.0 |
2 |
2013-04-16 |
| [OASIS Issue Tracker] Commented: (ODATA-346) Define meaning of collection-valued structural properties to be ordered "List" or "Array" |
3 |
2013-04-16 |
| [OASIS Issue Tracker] Commented: (ODATA-316) Allow omitting properties with null or default values from responses |
1 |
2013-04-16 |
| [OASIS Issue Tracker] Issue Comment Edited: (ODATA-316) Allow omitting properties with null or default values from responses |
1 |
2013-04-16 |
| [OASIS Issue Tracker] Commented: (ODATA-338) Representation of entity references in odata.metadata annotation |
1 |
2013-04-16 |
| [OASIS Issue Tracker] Commented: (ODATA-336) Be more generous on accepting values for the $format query option |
1 |
2013-04-16 |
| [OASIS Issue Tracker] Updated: (ODATA-345) Specify which nested query options can be used when expanding only references, and adapt syntax |
2 |
2013-04-17 |
| [OASIS Issue Tracker] Created: (ODATA-347) RFC and W3C citation content and formats in odata-atom-format-v4.0-wd01-2013-03-19-with-comments, odata-json-format-v4.0-wd01-2013-03-19-with-comments and odata-core-v4.0-wd01-part1-protocol-2013-4-5-with-comments |
1 |
2013-04-17 |
| membership status change |
2 |
2013-04-17 |
| [OASIS Issue Tracker] Created: (ODATA-348) Require the use of <edmx:Include> to pull in specific namespaces from <edmx:Reference> |
1 |
2013-04-17 |
| Agenda for OData TC meeting 2013.04.18 |
1 |
2013-04-17 |
| [OASIS Issue Tracker] Created: (ODATA-349) CSDL for Collection types is not clear on nullability of elements |
1 |
2013-04-18 |
| [OASIS Issue Tracker] Commented: (ODATA-322) Define how nested service documents are supported |
1 |
2013-04-18 |
| [OASIS Issue Tracker] Updated: (ODATA-348) Require the use of <edmx:Include> to pull in specific namespaces from <edmx:Reference> |
3 |
2013-04-18 |
| [OASIS Issue Tracker] Issue Comment Edited: (ODATA-322) Define how nested service documents are supported |
1 |
2013-04-18 |
| [OASIS Issue Tracker] Updated: (ODATA-346) Order of child elements of <edm:Collection> is significant |
2 |
2013-04-18 |
| [OASIS Issue Tracker] Created: (ODATA-350) Clearly describe the service document role, it's expected usage and also in comparison with $metadata |
1 |
2013-04-18 |
| [OASIS Issue Tracker] Updated: (ODATA-350) Clearly describe the service documents role, expected usage and responsibility in comparison with $metadata |
3 |
2013-04-18 |
| [OASIS Issue Tracker] Created: (ODATA-351) Define ID, ReadLink and EditLink in Part 1: Protocol, define representation in Atom and JSON |
1 |
2013-04-18 |
| [OASIS Issue Tracker] Updated: (ODATA-351) Define ID, ReadLink and EditLink in Part 1: Protocol, define representation in Atom and JSON |
2 |
2013-04-18 |
| [OASIS Issue Tracker] Created: (ODATA-352) Part II: Review results for OData JSON Format Version 4.0 |
1 |
2013-04-18 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDEz?= =?UTF-8?B?LTA0LTExIE1lZXRpbmcjMzIgbW9kaWZp?= =?UTF-8?B?ZWQ=?= |
1 |
2013-04-18 |
| =?UTF-8?B?R3JvdXBzIC0gT0RhdGEgRXh0ZW5zaW9u?= =?UTF-8?B?IGZvciBEYXRhIEFnZ3JlZ2F0aW9uIFZl?= =?UTF-8?B?cnNpb24gNC4wIHVwbG9hZGVk?= |
2 |
2013-04-18 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDEz?= =?UTF-8?B?LTA0LTE4IE1lZXRpbmcjMzMgdXBsb2Fk?= =?UTF-8?B?ZWQ=?= |
1 |
2013-04-18 |
| Agenda for OData TC F2F meeting April 25-26, 2013 |
3 |
2013-04-18 |
| =?UTF-8?B?R3JvdXBzIC0gRXZlbnQgIkZvdXJ0aCBG?= =?UTF-8?B?YWNlLXRvLUZhY2UgTWVldGluZyBPQVNJ?= =?UTF-8?B?UyBPRGF0YSBUZWNobmljYWwgQ29tbWl0?= =?UTF-8?B?dGVlIiBtb2RpZmllZA==?= |
3 |
2013-04-18 |
| [OASIS Issue Tracker] Updated: (ODATA-329) Approve Editoral Changes |
1 |
2013-04-19 |
| =?UTF-8?B?R3JvdXBzIC0gT0RhdGEgSlNPTiBGb3Jt?= =?UTF-8?B?YXQgVmVyc2lvbiA0LjAgdXBsb2FkZWQ=?= |
5 |
2013-04-19 |
| [OASIS Issue Tracker] Updated: (ODATA-352) Part II: Review results for OData JSON Format Version 4.0 |
3 |
2013-04-19 |
| [OASIS Issue Tracker] Created: (ODATA-353) Remove <Collection> and <TypeRef> elements |
1 |
2013-04-19 |
| [OASIS Issue Tracker] Commented: (ODATA-327) Service MUST only return async if return-async is specified |
4 |
2013-04-19 |
| [OASIS Issue Tracker] Updated: (ODATA-353) Remove <CollectionType> and <TypeRef> elements |
2 |
2013-04-19 |
| [OASIS Issue Tracker] Updated: (ODATA-328) Remove MinDataServiceVersion (OData-MinVersion) |
1 |
2013-04-19 |
| [OASIS Issue Tracker] Updated: (ODATA-327) Service MUST only return async if return-async is specified |
1 |
2013-04-19 |
| [OASIS Issue Tracker] Created: (ODATA-354) Make Edm. prefix required when referring to built-in types |
1 |
2013-04-20 |
| [OASIS Issue Tracker] Created: (ODATA-355) Define how property paths are represented in key part of URL |
1 |
2013-04-20 |
| [OASIS Issue Tracker] Updated: (ODATA-355) Define how property paths are represented in key part of URL |
8 |
2013-04-20 |
| [OASIS Issue Tracker] Issue Comment Edited: (ODATA-335) Review results for OData ATOM Format Version 4.0 |
1 |
2013-04-22 |
| [OASIS Issue Tracker] Updated: (ODATA-307) Return odata.etag in collections also for odata=minimalmetadata |
1 |
2013-04-22 |
| [OASIS Issue Tracker] Updated: (ODATA-324) Support external metadata references in payload |
2 |
2013-04-22 |
| [OASIS Issue Tracker] Updated: (ODATA-325) Clarify what aliases can be used in instance annotations |
1 |
2013-04-23 |
| [OASIS Issue Tracker] Updated: (ODATA-224) Fill out Capabilities sections of an OData Service |
1 |
2013-04-23 |
| [OASIS Issue Tracker] Updated: (ODATA-48) Consistent typographical conventions for OData specifications |
1 |
2013-04-23 |
| [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-04-23 |
| [OASIS Issue Tracker] Updated: (ODATA-332) Ensure comparability and emphasize differences in directly grokable way for all formats (currently only ATOM and JSON) |
1 |
2013-04-23 |
| [OASIS Issue Tracker] Updated: (ODATA-343) Ensure consistent placement and delegation of descritions for presentations of primitive values |
1 |
2013-04-23 |
| [OASIS Issue Tracker] Updated: (ODATA-331) Ensure that high level grouping expressions like eg. 'create operations' are easily mapped to real actions (HTTP methods, OData expectations) |
2 |
2013-04-23 |
| =?UTF-8?B?R3JvdXBzIC0gT0RhdGEgQ29yZSBQYXJ0?= =?UTF-8?B?IDI6IFVSTCBDb252ZW50aW9ucywgVmVy?= =?UTF-8?B?c2lvbiA0LjAgdXBsb2FkZWQ=?= |
5 |
2013-04-23 |
| [OASIS Issue Tracker] Updated: (ODATA-164) Consider syntax and rules around client specifying custom aggregation functions for rollups |
1 |
2013-04-24 |
| [OASIS Issue Tracker] Updated: (ODATA-349) CSDL for Collection types is not clear on nullability of elements |
1 |
2013-04-24 |
| [OASIS Issue Tracker] Commented: (ODATA-333) Visualize high level EDM overview through means of small diagrams to aid the reader on understanding base terms |
1 |
2013-04-24 |
| [OASIS Issue Tracker] Updated: (ODATA-126) Metadata as an OData service |
2 |
2013-04-24 |
| [OASIS Issue Tracker] Updated: (ODATA-239) Allowing expressions to be passed as parameters to (super) functions |
3 |
2013-04-24 |
| [OASIS Issue Tracker] Commented: (ODATA-126) Metadata as an OData service |
2 |
2013-04-24 |
| OData v4 release date |
3 |
2013-04-24 |
| [OASIS Issue Tracker] Updated: (ODATA-336) Be more generous on accepting values for the $format query option |
2 |
2013-04-24 |
| [OASIS Issue Tracker] Created: (ODATA-356) Review the changes in the latest version of Working Drafts |
1 |
2013-04-24 |
| [OASIS Issue Tracker] Updated: (ODATA-323) InlineCount should just be boolean |
3 |
2013-04-24 |
| [OASIS Issue Tracker] Updated: (ODATA-339) $inlinecount and $count, do we need both? Could we use $count in select clause as well? |
4 |
2013-04-24 |
| [OASIS Issue Tracker] Created: (ODATA-357) Use GeoJSON to format geo types in JSON |
1 |
2013-04-24 |
| [OASIS Issue Tracker] Created: (ODATA-358) Second parameter of the canonical search function should not allow search expressions |
1 |
2013-04-25 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDEz?= =?UTF-8?B?LTA0LTE4IE1lZXRpbmcjMzMgbW9kaWZp?= =?UTF-8?B?ZWQ=?= |
1 |
2013-04-25 |
| [OASIS Issue Tracker] Created: (ODATA-359) Allow yes, true and no, false as boolean values, remove 1 and 0 as boolean values, make values case-insensitive |
1 |
2013-04-25 |
| [OASIS Issue Tracker] Updated: (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 |
3 |
2013-04-25 |
| [OASIS Issue Tracker] Updated: (ODATA-359) Allow only true and false as boolean values, remove values 1 and 0, make values case-sensitive, all-lowercase |
3 |
2013-04-25 |
| [OASIS Issue Tracker] Updated: (ODATA-354) Make Edm. prefix required when referring to built-in types |
3 |
2013-04-25 |
| [OASIS Issue Tracker] Created: (ODATA-360) Remove edm:documentation element from [CSDL] |
1 |
2013-04-25 |
| [OASIS Issue Tracker] Updated: (ODATA-298) Clarify Requesting Changes to entity sets that include Stream properties |
2 |
2013-04-25 |
| [OASIS Issue Tracker] Created: (ODATA-361) Remove requirement that annotations come after all defined properties in CSDL |
1 |
2013-04-25 |
| [OASIS Issue Tracker] Created: (ODATA-362) Accept the application of several issues applied in the latest work product revisions in one grouping motion |
1 |
2013-04-25 |
| [OASIS Issue Tracker] Updated: (ODATA-362) Accept the application of several issues applied in the latest work product revisions in one grouping motion |
1 |
2013-04-25 |
| [OASIS Issue Tracker] Updated: (ODATA-362) Accept the application of 61 of the 64 issues applied in the latest work product revisions in one grouping motion |
2 |
2013-04-25 |
| [OASIS Issue Tracker] Updated: (ODATA-361) Remove requirement that annotations come after all defined properties in CSDL |
2 |
2013-04-25 |
| [OASIS Issue Tracker] Updated: (ODATA-360) Remove edm:documentation element from [CSDL] |
4 |
2013-04-25 |
| [OASIS Issue Tracker] Updated: (ODATA-357) Use GeoJSON to format geo types in JSON |
1 |
2013-04-25 |
| [OASIS Issue Tracker] Updated: (ODATA-356) Review the changes in the latest version of Working Drafts |
1 |
2013-04-25 |
| Please have a look at task issue ODATA-362, so we can resolve it tomorrow during day two |
2 |
2013-04-25 |
| [OASIS Issue Tracker] Updated: (ODATA-358) Second parameter of the canonical search function should not allow search expressions |
4 |
2013-04-25 |
| [OASIS Issue Tracker] Updated: (ODATA-248) Define required/optional format(s) for OData |
1 |
2013-04-25 |
| [OASIS Issue Tracker] Commented: (ODATA-358) Second parameter of the canonical search function should not allow search expressions |
1 |
2013-04-25 |
| [OASIS Issue Tracker] Updated: (ODATA-338) Representation of entity references in odata.metadata annotation |
2 |
2013-04-25 |
| [OASIS Issue Tracker] Updated: (ODATA-330) Define whether null values come first or last with $orderby asc |
1 |
2013-04-25 |
| [OASIS Issue Tracker] Updated: (ODATA-223) Specify Service behavior for not implemented functionality |
1 |
2013-04-25 |
| [OASIS Issue Tracker] Updated: (ODATA-240) Better describe, and possible extend, expected behavior of dealing with async $batch requests |
3 |
2013-04-25 |
| [OASIS Issue Tracker] Created: (ODATA-363) specifiying selected properties in metadataurl is broken |
1 |
2013-04-26 |
| [OASIS Issue Tracker] Updated: (ODATA-363) specifiying selected properties in metadataurl is broken |
2 |
2013-04-26 |
| [OASIS Issue Tracker] Updated: (ODATA-357) Use GeoJSON in JSON and GML in Atom to represent geo types |
2 |
2013-04-26 |
| =?UTF-8?B?R3JvdXBzIC0gT0RhdGEgV0QwMSB1cGxv?= =?UTF-8?B?YWRlZA==?= |
1 |
2013-04-26 |
| =?UTF-8?B?R3JvdXBzIC0gT0RhdGEgSlNPTiBXRDAx?= =?UTF-8?B?IHVwbG9hZGVk?= |
2 |
2013-04-26 |
| =?UTF-8?B?R3JvdXBzIC0gT0RhdGEgQXRvbSBXRDAx?= =?UTF-8?B?IHVwbG9hZGVk?= |
1 |
2013-04-26 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDEz?= =?UTF-8?B?LTA0LTI1LzI2IE1lZXRpbmcjMzQgRjJG?= =?UTF-8?B?IHVwbG9hZGVk?= |
1 |
2013-04-26 |
| [OASIS Issue Tracker] Issue Comment Edited: (ODATA-126) Metadata as an OData service |
1 |
2013-04-29 |
| =?UTF-8?B?R3JvdXBzIC0gT0RhdGEtVEMgMjAxMy0w?= =?UTF-8?B?NS0wMiBEYXRhIEFnZ3JlZ2F0aW9uLnBw?= =?UTF-8?B?dHggdXBsb2FkZWQ=?= |
1 |
2013-04-29 |
| Agenda for OData TC meeting 2013.05.02 |
1 |
2013-04-30 |
| [OASIS Issue Tracker] Updated: (ODATA-222) free-text search within a property |
1 |
2013-04-30 |
| [OASIS Issue Tracker] Created: (ODATA-364) Remove restriction that a property MUST NOT have the same name as its containing type |
1 |
2013-04-30 |
| [OASIS Issue Tracker] Updated: (ODATA-364) Remove restriction that a property MUST NOT have the same name as its containing type |
1 |
2013-04-30 |
| [OASIS Issue Tracker] Created: (ODATA-365) Rename edm:AssertType to edm:CastToType and clearify behaviour |
1 |
2013-04-30 |
| [OASIS Issue Tracker] Updated: (ODATA-365) Rename edm:AssertType to edm:CastToType and clearify behaviour |
2 |
2013-04-30 |
| [OASIS Issue Tracker] Updated: (ODATA-365) Rename edm:AssertType to edm:Cast and clearify behaviour |
1 |
2013-04-30 |
| [OASIS Issue Tracker] Updated: (ODATA-365) Rename edm:AssertType to edm:Cast and clarify behavior of edm:Cast and cast() |
1 |
2013-04-30 |
| [OASIS Issue Tracker] Updated: (ODATA-301) Guidance around data authorization model and secure authenticated access to an OData Service |
2 |
2013-04-30 |
