| 00000 |
[OASIS Issue Tracker] Created: (ODATA-589) Add a JSON version of the Metadata document |
OASIS Issues Tracker
|
2014-03-03 17:50 |
| 00001 |
[OASIS Issue Tracker] Updated: (ODATA-585) Status response message as carrier for annotations as alternative to 204 No Content |
OASIS Issues Tracker
|
2014-03-04 09:02 |
| 00002 |
Version Control Commit by ralfhandl |
[email protected]
|
2014-03-04 09:35 |
| 00003 |
Version Control Commit by ralfhandl |
[email protected]
|
2014-03-04 09:37 |
| 00004 |
Version Control Commit by ralfhandl |
[email protected]
|
2014-03-04 09:38 |
| 00005 |
Version Control Commit by ralfhandl |
[email protected]
|
2014-03-04 09:44 |
| 00006 |
[OASIS Issue Tracker] Commented: (ODATA-589) Add a JSON version of the Metadata document |
OASIS Issues Tracker
|
2014-03-04 09:48 |
| 00007 |
[OASIS Issue Tracker] Created: (ODATA-590) Leading zeroes in values for $level |
OASIS Issues Tracker
|
2014-03-04 10:46 |
| 00008 |
[OASIS Issue Tracker] Created: (ODATA-591) Part1, examples 36-40: replace "associated" with "related" |
OASIS Issues Tracker
|
2014-03-04 10:48 |
| 00009 |
[OASIS Issue Tracker] Created: (ODATA-592) JSON example 11: "type":"Point" with uppercase P according to GeoJSON spec |
OASIS Issues Tracker
|
2014-03-04 10:50 |
| 00010 |
Version Control Commit by sdrees |
[email protected]
|
2014-03-06 14:34 |
| 00011 |
Groups - Minutes of 2014-02-27 Meeting#67 uploaded |
Stefan Drees
|
2014-03-06 14:35 |
| 00012 |
OData V4.0 and OData JSON Format V4.0 OASIS Standards published |
Chet Ensign
|
2014-03-06 16:01 |
| 00013 |
[OASIS Issue Tracker] Created: (ODATA-593) Stream properties for JSON can indicate mediaContentType but ATOM doesn't allow it |
OASIS Issues Tracker
|
2014-03-09 06:47 |
| 00014 |
[OASIS Issue Tracker] Created: (ODATA-594) Discrepancy between ATOM and JSON formats (GML, GeoJson) for Polygon information content |
OASIS Issues Tracker
|
2014-03-09 06:55 |
| 00015 |
[OASIS Issue Tracker] Created: (ODATA-595) We should define some sort of "profile" to specify which GML elements/attributes are valid with ATOM Geo-types |
OASIS Issues Tracker
|
2014-03-09 07:09 |
| 00016 |
[OASIS Issue Tracker] Created: (ODATA-596) Discrepancy between order of elements for geo-positions between GeoJSON and GML may cause interoperability difficulties. |
OASIS Issues Tracker
|
2014-03-09 07:26 |
| 00017 |
[OASIS Issue Tracker] Created: (ODATA-597) Seeking clarification of naming for GeographyCollection with GeoJSON |
OASIS Issues Tracker
|
2014-03-09 07:29 |
| 00018 |
[OASIS Issue Tracker] Updated: (ODATA-595) We should define some sort of "profile" to specify which GML elements/attributes are valid with ATOM Geo-types |
OASIS Issues Tracker
|
2014-03-09 07:34 |
| 00019 |
[OASIS Issue Tracker] Commented: (ODATA-596) Discrepancy between order of elements for geo-positions between GeoJSON and GML may cause interoperability difficulties. |
OASIS Issues Tracker
|
2014-03-09 08:23 |
| 00020 |
[OASIS Issue Tracker] Created: (ODATA-598) Update JSON RFC reference |
OASIS Issues Tracker
|
2014-03-09 08:33 |
| 00021 |
[OASIS Issue Tracker] Created: (ODATA-599) Let's update the GeoJSON reference |
OASIS Issues Tracker
|
2014-03-09 08:37 |
| 00022 |
[OASIS Issue Tracker] Created: (ODATA-600) Ensure future compatibility by reference to draft-bray-i-json-n (The I-JSON Message Format) |
OASIS Issues Tracker
|
2014-03-09 08:43 |
| 00023 |
[OASIS Issue Tracker] Created: (ODATA-601) Investigate enhancements to interoperability and feature set of OData JSON through JSON-LD |
OASIS Issues Tracker
|
2014-03-09 08:57 |
| 00024 |
[OASIS Issue Tracker] Updated: (ODATA-601) Investigate enhancements to interoperability and feature set of OData JSON through JSON-LD |
OASIS Issues Tracker
|
2014-03-09 09:03 |
| 00025 |
[OASIS Issue Tracker] Updated: (ODATA-597) Seeking clarification of naming for GeographyCollection with GeoJSON |
OASIS Issues Tracker
|
2014-03-10 08:31 |
| 00026 |
[OASIS Issue Tracker] Created: (ODATA-602) Explicitly state what's allowed after /$all |
OASIS Issues Tracker
|
2014-03-10 08:47 |
| 00027 |
[OASIS Issue Tracker] Created: (ODATA-603) Primitive type Edm.Stream: use as type of collection, input parameter, return type |
OASIS Issues Tracker
|
2014-03-10 08:55 |
| 00028 |
[OASIS Issue Tracker] Updated: (ODATA-603) Primitive type Edm.Stream: use as type of collection, input parameter, return type, or underlying type of type definition |
OASIS Issues Tracker
|
2014-03-10 08:55 |
| 00029 |
[OASIS Issue Tracker] Created: (ODATA-604) Add type cast segment for complex types in rules for $select and $expand |
OASIS Issues Tracker
|
2014-03-10 09:02 |
| 00030 |
[OASIS Issue Tracker] Created: (ODATA-605) Annotation target path syntax insufficient to annotate contained entity sets |
OASIS Issues Tracker
|
2014-03-10 09:10 |
| 00031 |
[OASIS Issue Tracker] Updated: (ODATA-604) Add type cast segment for complex types in rules for $select and $expand |
OASIS Issues Tracker
|
2014-03-10 09:11 |
| 00032 |
[OASIS Issue Tracker] Created: (ODATA-606) Specify navigation property binding combined with containment |
OASIS Issues Tracker
|
2014-03-10 09:11 |
| 00033 |
[OASIS Issue Tracker] Updated: (ODATA-593) Stream properties for JSON can indicate mediaContentType but ATOM doesn't allow it |
OASIS Issues Tracker
|
2014-03-10 09:13 |
| 00034 |
[OASIS Issue Tracker] Updated: (ODATA-593) Stream properties for JSON can indicate mediaContentType but ATOM doesn't allow it |
OASIS Issues Tracker
|
2014-03-10 09:13 |
| 00035 |
[OASIS Issue Tracker] Updated: (ODATA-595) We should define some sort of "profile" to specify which GML elements/attributes are valid with ATOM Geo-types |
OASIS Issues Tracker
|
2014-03-10 09:13 |
| 00036 |
[OASIS Issue Tracker] Created: (ODATA-607) Section 4.5.4: explicitly state that @odata.count can be applied to expanded to-many navigation properties with server-driven paging |
OASIS Issues Tracker
|
2014-03-10 09:17 |
| 00037 |
[OASIS Issue Tracker] Created: (ODATA-608) Explicitly state that the path segment /$count can be combined with $search and $filter, and that the calculated count is identical to $count=true |
OASIS Issues Tracker
|
2014-03-10 09:29 |
| 00038 |
[OASIS Issue Tracker] Created: (ODATA-609) Section 11.4.4 Upsert: key values in URL win over key values in request body |
OASIS Issues Tracker
|
2014-03-10 09:36 |
| 00039 |
[OASIS Issue Tracker] Created: (ODATA-610) 11.4.4: Upsert and server-generated keys |
OASIS Issues Tracker
|
2014-03-10 09:39 |
| 00040 |
[OASIS Issue Tracker] Created: (ODATA-611) Explicitly state that the service root URL ends with a forward-slash |
OASIS Issues Tracker
|
2014-03-10 09:42 |
| 00041 |
[OASIS Issue Tracker] Created: (ODATA-612) Consistently use "edit link" and "edit URL" |
OASIS Issues Tracker
|
2014-03-10 09:42 |
| 00042 |
[OASIS Issue Tracker] Created: (ODATA-613) Allow POST to entity sets using the delta-response format |
OASIS Issues Tracker
|
2014-03-10 09:50 |
| 00043 |
[OASIS Issue Tracker] Updated: (ODATA-613) Allow POST to entity sets using the delta-response format |
OASIS Issues Tracker
|
2014-03-10 09:50 |
| 00044 |
[OASIS Issue Tracker] Created: (ODATA-614) Allow $expand on POST in combination with return=representation to specify the response shape |
OASIS Issues Tracker
|
2014-03-10 09:52 |
| 00045 |
[OASIS Issue Tracker] Created: (ODATA-615) Allow DELETE with $filter on collections to delete all (and only) the matching entities |
OASIS Issues Tracker
|
2014-03-10 09:52 |
| 00046 |
[OASIS Issue Tracker] Created: (ODATA-616) Allow POST to collections of complex types, and DELETE with $filter |
OASIS Issues Tracker
|
2014-03-10 09:53 |
| 00047 |
[OASIS Issue Tracker] Created: (ODATA-617) Allow eq/ne comparison of instances of same structured (complex or entity) type, allow eq/ne comparison with null for 0..1 nav props |
OASIS Issues Tracker
|
2014-03-10 09:55 |
| 00048 |
[OASIS Issue Tracker] Updated: (ODATA-617) Allow eq/ne comparison of instances of same structured (complex or entity) type, allow eq/ne comparison with null for 0..1 nav props |
OASIS Issues Tracker
|
2014-03-10 09:55 |
| 00049 |
[OASIS Issue Tracker] Created: (ODATA-618) Allow using term names in positions that allow type names |
OASIS Issues Tracker
|
2014-03-10 09:57 |
| 00050 |
[OASIS Issue Tracker] Created: (ODATA-619) Attach action and function signatures to terms, i.e. make a term definition an interface definition |
OASIS Issues Tracker
|
2014-03-10 10:03 |
| 00051 |
[OASIS Issue Tracker] Created: (ODATA-620) Replace "scalar type" with "primitive type" and "scalar property" with "structural property" |
OASIS Issues Tracker
|
2014-03-11 08:34 |
| 00052 |
Reminder: Sponsor quote deadline for OData 4.0 Press Release |
Carol Geyer
|
2014-03-11 13:58 |
| 00053 |
OData Extension for Data Aggregation V4.0 published |
Chet Ensign
|
2014-03-11 18:54 |
| 00054 |
FW: [odata] OData V4.0 and OData JSON Format V4.0 OASIS Standards published |
Ram Jeyaraman (MS OPEN TECH)
|
2014-03-11 19:15 |
| 00055 |
[OASIS Issue Tracker] Commented: (ODATA-614) Allow $expand on POST in combination with return=representation to specify the response shape |
OASIS Issues Tracker
|
2014-03-11 19:48 |
| 00056 |
[OASIS Issue Tracker] Commented: (ODATA-614) Allow $expand on POST in combination with return=representation to specify the response shape |
OASIS Issues Tracker
|
2014-03-12 08:18 |
| 00057 |
[OASIS Issue Tracker] Created: (ODATA-621) Clarify: Specifying an unbound function with overloads in a function import should import all overloads of that function to the entity container |
OASIS Issues Tracker
|
2014-03-12 18:21 |
| 00058 |
[OASIS Issue Tracker] Created: (ODATA-622) Allow comparison of geo types, binary to null. |
OASIS Issues Tracker
|
2014-03-12 18:27 |
| 00059 |
[OASIS Issue Tracker] Created: (ODATA-623) Update of key properties: be more specific |
OASIS Issues Tracker
|
2014-03-13 10:41 |
| 00060 |
[OASIS Issue Tracker] Updated: (ODATA-623) 11:4.3: be more specific on updating key properties |
OASIS Issues Tracker
|
2014-03-13 11:53 |
| 00061 |
[OASIS Issue Tracker] Updated: (ODATA-623) 11:4.3: be more specific on updating key properties |
OASIS Issues Tracker
|
2014-03-13 11:53 |
| 00062 |
Agenda for OData TC meeting 2014.03.13 |
Ram Jeyaraman (MS OPEN TECH)
|
2014-03-13 14:52 |
| 00063 |
[OASIS Issue Tracker] Created: (ODATA-624) Clarify that (clients and) services may include additional format parameters in Content-Type header. |
OASIS Issues Tracker
|
2014-03-13 19:36 |
| 00064 |
OData v4 PR plan |
Ram Jeyaraman (MS OPEN TECH)
|
2014-03-14 23:57 |
| 00065 |
Version Control Commit by sdrees |
[email protected]
|
2014-03-15 09:47 |
| 00066 |
Groups - Minutes of 2014-02-27 Meeting#67 modified |
Stefan Drees
|
2014-03-15 09:48 |
| 00067 |
Groups - Minutes of 2014-03-13 Meeting#68 uploaded |
Stefan Drees
|
2014-03-15 09:52 |
| 00068 |
Version Control Commit by sdrees |
[email protected]
|
2014-03-15 10:12 |
| 00069 |
Groups - Minutes of 2014-03-13 Meeting#68 uploaded |
Stefan Drees
|
2014-03-15 10:13 |
| 00070 |
Press release to announce OData 4.0 approval |
Carol Geyer
|
2014-03-17 15:54 |
| 00071 |
We made it to the front page of slashdot ;-) |
Stefan Drees
|
2014-03-18 06:37 |
| 00072 |
Re: [odata] We made it to the front page of slashdot ;-) |
Stefan Drees
|
2014-03-18 06:43 |
| 00073 |
Press coverage newsticker at heise.de |
Stefan Drees
|
2014-03-19 06:20 |
| 00074 |
[OASIS Issue Tracker] (ODATA-625) Add example for UrlRef in attribute notation |
OASIS Issues Tracker
|
2014-03-20 06:46 |
| 00075 |
[OASIS Issue Tracker] (ODATA-626) Security:services should consider what media types they support |
OASIS Issues Tracker
|
2014-03-26 05:53 |
| 00076 |
[OASIS Issue Tracker] (ODATA-626) Security:services should consider what media types they support |
OASIS Issues Tracker
|
2014-03-26 05:55 |
| 00077 |
[OASIS Issue Tracker] (ODATA-627) Security: Returning 404 (Not Found) versus 401 (unauthorized) could leak information |
OASIS Issues Tracker
|
2014-03-26 06:02 |
| 00078 |
[OASIS Issue Tracker] (ODATA-628) Security: Service implementors should consider timing-based information leakage attacks |
OASIS Issues Tracker
|
2014-03-26 06:08 |
| 00079 |
[OASIS Issue Tracker] (ODATA-629) Security: Returning Core.Permission'None' could be information leakage |
OASIS Issues Tracker
|
2014-03-26 06:19 |
| 00080 |
[OASIS Issue Tracker] (ODATA-630) Consider making odata the default namespace for annotations |
OASIS Issues Tracker
|
2014-03-26 06:26 |
| 00081 |
[OASIS Issue Tracker] (ODATA-631) How do annotations that target entity sets work against singletons/containment? |
OASIS Issues Tracker
|
2014-03-26 06:28 |
| 00082 |
[OASIS Issue Tracker] (ODATA-632) "Core.OptimisticConcurrencyControl" should be "Core.OptimisticConcurrency" |
OASIS Issues Tracker
|
2014-03-26 06:35 |
| 00083 |
[odata] Agenda for OData TC meeting 2014-03-27 |
Handl, Ralf
|
2014-03-26 12:40 |
| 00084 |
[OASIS Issue Tracker] (ODATA-623) 11:4.3: be more specific on updating key properties |
OASIS Issues Tracker
|
2014-03-27 03:14 |
| 00085 |
[OASIS Issue Tracker] (ODATA-623) 11:4.3: be more specific on updating key properties |
OASIS Issues Tracker
|
2014-03-27 03:14 |
| 00086 |
[OASIS Issue Tracker] (ODATA-633) Rule pct-encoded-unescaped unintentionally omits hex pairs starting with 7 |
OASIS Issues Tracker
|
2014-03-27 08:05 |
| 00087 |
Re: [odata] Agenda for OData TC meeting 2014-03-27 |
Stefan Drees
|
2014-03-27 14:15 |
| 00088 |
[OASIS Issue Tracker] (ODATA-634) Specify the behaviour when a non-nullable property with no default value is omitted from a PUT |
OASIS Issues Tracker
|
2014-03-27 15:11 |
| 00089 |
[OASIS Issue Tracker] (ODATA-570) Clearify behavior of edm:UrlRef expression |
OASIS Issues Tracker
|
2014-03-27 15:44 |
| 00090 |
[OASIS Issue Tracker] (ODATA-603) Primitive type Edm.Stream: use as type of collection, input parameter, return type, or underlying type of type definition |
OASIS Issues Tracker
|
2014-03-27 15:50 |
| 00091 |
[OASIS Issue Tracker] (ODATA-605) Annotation target path syntax insufficient to annotate contained entity sets |
OASIS Issues Tracker
|
2014-03-27 15:52 |
| 00092 |
[OASIS Issue Tracker] (ODATA-610) 11.4.4: Upsert and server-generated keys |
OASIS Issues Tracker
|
2014-03-27 16:09 |
| 00093 |
[OASIS Issue Tracker] (ODATA-623) 11.4.3: be more specific on updating key properties |
OASIS Issues Tracker
|
2014-03-27 16:13 |
| 00094 |
[OASIS Issue Tracker] (ODATA-623) 11.4.3: be more specific on updating key properties |
OASIS Issues Tracker
|
2014-03-27 16:16 |
| 00095 |
[OASIS Issue Tracker] (ODATA-624) Clarify that (clients and) services may include additional format parameters in Content-Type header. |
OASIS Issues Tracker
|
2014-03-27 16:20 |
| 00096 |
Groups - Minutes of 2014-03-13 Meeting#68 modified |
Stefan Drees
|
2014-03-27 22:17 |
| 00097 |
[OASIS Issue Tracker] (ODATA-635) Clarify if a PUT request allowed to change the odata.type of the entity (public comment c201403e00002) |
OASIS Issues Tracker
|
2014-03-27 22:31 |
| 00098 |
[OASIS Issue Tracker] (ODATA-635) Clarify if a PUT request allowed to change the odata.type of the entity (public comment c201403e00002) |
OASIS Issues Tracker
|
2014-03-27 22:33 |
| 00099 |
[OASIS Issue Tracker] (ODATA-635) Clarify if a PUT request is allowed to change the odata.type of the entity (public comment c201403e00002) |
OASIS Issues Tracker
|
2014-03-27 22:37 |
| 00100 |
[OASIS Issue Tracker] (ODATA-636) Clarify that complex types can only be passed to functions through parameter aliases |
OASIS Issues Tracker
|
2014-03-28 18:06 |
| 00101 |
[OASIS Issue Tracker] (ODATA-636) Clarify that complex types and arrays can only be passed to functions through parameter aliases |
OASIS Issues Tracker
|
2014-03-28 18:09 |
| 00102 |
Version Control Commit by sdrees |
[email protected]
|
2014-04-01 05:42 |
| 00103 |
Groups - Minutes of 2014-03-27 Meeting#69 uploaded |
Stefan Drees
|
2014-04-01 05:44 |
