[OASIS Issue Tracker] Updated: (ODATA-466) Please clarify whether Edm.Binary is really intended to be base16-encoded in accordance with ABNF, or if it should be base64-encoded as with OData V3

odata · September 2013 · 3 messages · back to month · +1 message in 1 other month

# Subject From Date
00186 [OASIS Issue Tracker] Updated: (ODATA-466) Please clarify whether Edm.Binary is really intended to be base16-encoded in accordance with ABNF, or if it should be base64-encoded as with OData V3 OASIS Issues Tracker 2013-09-23 19:15
00187 [OASIS Issue Tracker] Updated: (ODATA-466) Please clarify whether Edm.Binary is really intended to be base16-encoded in accordance with ABNF, or if it should be base64-encoded as with OData V3 OASIS Issues Tracker 2013-09-23 19:55
00190 [OASIS Issue Tracker] Updated: (ODATA-466) Please clarify whether Edm.Binary is really intended to be base16-encoded in accordance with ABNF, or if it should be base64-encoded as with OData V3 OASIS Issues Tracker 2013-09-23 20:15