| [OASIS Issue Tracker] Created: (ODATA-589) Add a JSON version of the Metadata document |
1 |
2014-03-03 |
| [OASIS Issue Tracker] Updated: (ODATA-585) Status response message as carrier for annotations as alternative to 204 No Content |
1 |
2014-03-04 |
| Version Control Commit by ralfhandl |
4 |
2014-03-04 |
| [OASIS Issue Tracker] Commented: (ODATA-589) Add a JSON version of the Metadata document |
1 |
2014-03-04 |
| [OASIS Issue Tracker] Created: (ODATA-590) Leading zeroes in values for $level |
1 |
2014-03-04 |
| [OASIS Issue Tracker] Created: (ODATA-591) Part1, examples 36-40: replace "associated" with "related" |
1 |
2014-03-04 |
| [OASIS Issue Tracker] Created: (ODATA-592) JSON example 11: "type":"Point" with uppercase P according to GeoJSON spec |
1 |
2014-03-04 |
| Version Control Commit by sdrees |
4 |
2014-03-06 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDE0?= =?UTF-8?B?LTAyLTI3IE1lZXRpbmcjNjcgdXBsb2Fk?= =?UTF-8?B?ZWQ=?= |
1 |
2014-03-06 |
| OData V4.0 and OData JSON Format V4.0 OASIS Standards published |
2 |
2014-03-06 |
| [OASIS Issue Tracker] Created: (ODATA-593) Stream properties for JSON can indicate mediaContentType but ATOM doesn't allow it |
1 |
2014-03-09 |
| [OASIS Issue Tracker] Created: (ODATA-594) Discrepancy between ATOM and JSON formats (GML, GeoJson) for Polygon information content |
1 |
2014-03-09 |
| [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 |
1 |
2014-03-09 |
| [OASIS Issue Tracker] Created: (ODATA-596) Discrepancy between order of elements for geo-positions between GeoJSON and GML may cause interoperability difficulties. |
1 |
2014-03-09 |
| [OASIS Issue Tracker] Created: (ODATA-597) Seeking clarification of naming for GeographyCollection with GeoJSON |
1 |
2014-03-09 |
| [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 |
2 |
2014-03-09 |
| [OASIS Issue Tracker] Commented: (ODATA-596) Discrepancy between order of elements for geo-positions between GeoJSON and GML may cause interoperability difficulties. |
1 |
2014-03-09 |
| [OASIS Issue Tracker] Created: (ODATA-598) Update JSON RFC reference |
1 |
2014-03-09 |
| [OASIS Issue Tracker] Created: (ODATA-599) Let's update the GeoJSON reference |
1 |
2014-03-09 |
| [OASIS Issue Tracker] Created: (ODATA-600) Ensure future compatibility by reference to draft-bray-i-json-n (The I-JSON Message Format) |
1 |
2014-03-09 |
| [OASIS Issue Tracker] Created: (ODATA-601) Investigate enhancements to interoperability and feature set of OData JSON through JSON-LD |
1 |
2014-03-09 |
| [OASIS Issue Tracker] Updated: (ODATA-601) Investigate enhancements to interoperability and feature set of OData JSON through JSON-LD |
1 |
2014-03-09 |
| [OASIS Issue Tracker] Updated: (ODATA-597) Seeking clarification of naming for GeographyCollection with GeoJSON |
1 |
2014-03-10 |
| [OASIS Issue Tracker] Created: (ODATA-602) Explicitly state what's allowed after /$all |
1 |
2014-03-10 |
| [OASIS Issue Tracker] Created: (ODATA-603) Primitive type Edm.Stream: use as type of collection, input parameter, return type |
1 |
2014-03-10 |
| [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 |
1 |
2014-03-10 |
| [OASIS Issue Tracker] Created: (ODATA-604) Add type cast segment for complex types in rules for $select and $expand |
1 |
2014-03-10 |
| [OASIS Issue Tracker] Created: (ODATA-605) Annotation target path syntax insufficient to annotate contained entity sets |
1 |
2014-03-10 |
| [OASIS Issue Tracker] Updated: (ODATA-604) Add type cast segment for complex types in rules for $select and $expand |
1 |
2014-03-10 |
| [OASIS Issue Tracker] Created: (ODATA-606) Specify navigation property binding combined with containment |
1 |
2014-03-10 |
| [OASIS Issue Tracker] Updated: (ODATA-593) Stream properties for JSON can indicate mediaContentType but ATOM doesn't allow it |
2 |
2014-03-10 |
| [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 |
1 |
2014-03-10 |
| [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 |
1 |
2014-03-10 |
| [OASIS Issue Tracker] Created: (ODATA-609) Section 11.4.4 Upsert: key values in URL win over key values in request body |
1 |
2014-03-10 |
| [OASIS Issue Tracker] Created: (ODATA-610) 11.4.4: Upsert and server-generated keys |
1 |
2014-03-10 |
| [OASIS Issue Tracker] Created: (ODATA-611) Explicitly state that the service root URL ends with a forward-slash |
1 |
2014-03-10 |
| [OASIS Issue Tracker] Created: (ODATA-612) Consistently use "edit link" and "edit URL" |
1 |
2014-03-10 |
| [OASIS Issue Tracker] Created: (ODATA-613) Allow POST to entity sets using the delta-response format |
1 |
2014-03-10 |
| [OASIS Issue Tracker] Updated: (ODATA-613) Allow POST to entity sets using the delta-response format |
1 |
2014-03-10 |
| [OASIS Issue Tracker] Created: (ODATA-614) Allow $expand on POST in combination with return=representation to specify the response shape |
1 |
2014-03-10 |
| [OASIS Issue Tracker] Created: (ODATA-615) Allow DELETE with $filter on collections to delete all (and only) the matching entities |
1 |
2014-03-10 |
| [OASIS Issue Tracker] Created: (ODATA-616) Allow POST to collections of complex types, and DELETE with $filter |
1 |
2014-03-10 |
| [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 |
1 |
2014-03-10 |
| [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 |
1 |
2014-03-10 |
| [OASIS Issue Tracker] Created: (ODATA-618) Allow using term names in positions that allow type names |
1 |
2014-03-10 |
| [OASIS Issue Tracker] Created: (ODATA-619) Attach action and function signatures to terms, i.e. make a term definition an interface definition |
1 |
2014-03-10 |
| [OASIS Issue Tracker] Created: (ODATA-620) Replace "scalar type" with "primitive type" and "scalar property" with "structural property" |
1 |
2014-03-11 |
| Reminder: Sponsor quote deadline for OData 4.0 Press Release |
1 |
2014-03-11 |
| OData Extension for Data Aggregation V4.0 published |
1 |
2014-03-11 |
| [OASIS Issue Tracker] Commented: (ODATA-614) Allow $expand on POST in combination with return=representation to specify the response shape |
2 |
2014-03-11 |
| [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 |
1 |
2014-03-12 |
| [OASIS Issue Tracker] Created: (ODATA-622) Allow comparison of geo types, binary to null. |
1 |
2014-03-12 |
| [OASIS Issue Tracker] Created: (ODATA-623) Update of key properties: be more specific |
1 |
2014-03-13 |
| [OASIS Issue Tracker] Updated: (ODATA-623) 11:4.3: be more specific on updating key properties |
2 |
2014-03-13 |
| Agenda for OData TC meeting 2014.03.13 |
1 |
2014-03-13 |
| [OASIS Issue Tracker] Created: (ODATA-624) Clarify that (clients and) services may include additional format parameters in Content-Type header. |
1 |
2014-03-13 |
| OData v4 PR plan |
1 |
2014-03-14 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDE0?= =?UTF-8?B?LTAyLTI3IE1lZXRpbmcjNjcgbW9kaWZp?= =?UTF-8?B?ZWQ=?= |
1 |
2014-03-15 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDE0?= =?UTF-8?B?LTAzLTEzIE1lZXRpbmcjNjggdXBsb2Fk?= =?UTF-8?B?ZWQ=?= |
2 |
2014-03-15 |
| Press release to announce OData 4.0 approval |
1 |
2014-03-17 |
| We made it to the front page of slashdot ;-) |
2 |
2014-03-18 |
| Press coverage newsticker at heise.de |
1 |
2014-03-19 |
| [OASIS Issue Tracker] (ODATA-625) Add example for UrlRef in attribute notation |
1 |
2014-03-20 |
| [OASIS Issue Tracker] (ODATA-626) Security:services should consider what media types they support |
2 |
2014-03-26 |
| [OASIS Issue Tracker] (ODATA-627) Security: Returning 404 (Not Found) versus 401 (unauthorized) could leak information |
1 |
2014-03-26 |
| [OASIS Issue Tracker] (ODATA-628) Security: Service implementors should consider timing-based information leakage attacks |
1 |
2014-03-26 |
| [OASIS Issue Tracker] (ODATA-629) Security: Returning Core.Permission'None' could be information leakage |
1 |
2014-03-26 |
| [OASIS Issue Tracker] (ODATA-630) Consider making odata the default namespace for annotations |
1 |
2014-03-26 |
| [OASIS Issue Tracker] (ODATA-631) How do annotations that target entity sets work against singletons/containment? |
1 |
2014-03-26 |
| [OASIS Issue Tracker] (ODATA-632) "Core.OptimisticConcurrencyControl" should be "Core.OptimisticConcurrency" |
1 |
2014-03-26 |
| [odata] Agenda for OData TC meeting 2014-03-27 |
2 |
2014-03-26 |
| [OASIS Issue Tracker] (ODATA-623) 11:4.3: be more specific on updating key properties |
2 |
2014-03-27 |
| [OASIS Issue Tracker] (ODATA-633) Rule pct-encoded-unescaped unintentionally omits hex pairs starting with 7 |
1 |
2014-03-27 |
| [OASIS Issue Tracker] (ODATA-634) Specify the behaviour when a non-nullable property with no default value is omitted from a PUT |
1 |
2014-03-27 |
| [OASIS Issue Tracker] (ODATA-570) Clearify behavior of edm:UrlRef expression |
1 |
2014-03-27 |
| [OASIS Issue Tracker] (ODATA-603) Primitive type Edm.Stream: use as type of collection, input parameter, return type, or underlying type of type definition |
1 |
2014-03-27 |
| [OASIS Issue Tracker] (ODATA-605) Annotation target path syntax insufficient to annotate contained entity sets |
1 |
2014-03-27 |
| [OASIS Issue Tracker] (ODATA-610) 11.4.4: Upsert and server-generated keys |
1 |
2014-03-27 |
| [OASIS Issue Tracker] (ODATA-623) 11.4.3: be more specific on updating key properties |
2 |
2014-03-27 |
| [OASIS Issue Tracker] (ODATA-624) Clarify that (clients and) services may include additional format parameters in Content-Type header. |
1 |
2014-03-27 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDE0?= =?UTF-8?B?LTAzLTEzIE1lZXRpbmcjNjggbW9kaWZp?= =?UTF-8?B?ZWQ=?= |
1 |
2014-03-27 |
| [OASIS Issue Tracker] (ODATA-635) Clarify if a PUT request allowed to change the odata.type of the entity (public comment c201403e00002) |
2 |
2014-03-27 |
| [OASIS Issue Tracker] (ODATA-635) Clarify if a PUT request is allowed to change the odata.type of the entity (public comment c201403e00002) |
1 |
2014-03-27 |
| [OASIS Issue Tracker] (ODATA-636) Clarify that complex types can only be passed to functions through parameter aliases |
1 |
2014-03-28 |
| [OASIS Issue Tracker] (ODATA-636) Clarify that complex types and arrays can only be passed to functions through parameter aliases |
1 |
2014-03-28 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiAyMDE0?= =?UTF-8?B?LTAzLTI3IE1lZXRpbmcjNjkgdXBsb2Fk?= =?UTF-8?B?ZWQ=?= |
1 |
2014-04-01 |
