[OASIS Issue Tracker] Updated: (ODATA-466) Edm.Binary should be base64-encoded (as with OData V3), not base16-encoded (as per current ABNF)

odata · September 2013 · 5 messages · back to month

# Subject From Date
00192 [OASIS Issue Tracker] Updated: (ODATA-466) Edm.Binary should be base64-encoded (as with OData V3), not base16-encoded (as per current ABNF) OASIS Issues Tracker 2013-09-23 22:19
00198 [OASIS Issue Tracker] Updated: (ODATA-466) Edm.Binary should be base64-encoded (as with OData V3), not base16-encoded (as per current ABNF) OASIS Issues Tracker 2013-09-24 05:55
00317 [OASIS Issue Tracker] Updated: (ODATA-466) Edm.Binary should be base64-encoded (as with OData V3), not base16-encoded (as per current ABNF) OASIS Issues Tracker 2013-09-27 14:25
00321 [OASIS Issue Tracker] Updated: (ODATA-466) Edm.Binary should be base64-encoded (as with OData V3), not base16-encoded (as per current ABNF) OASIS Issues Tracker 2013-09-27 15:12
00323 [OASIS Issue Tracker] Updated: (ODATA-466) Edm.Binary should be base64-encoded (as with OData V3), not base16-encoded (as per current ABNF) OASIS Issues Tracker 2013-09-27 15:15