[ https://issues.oasis-open.org/browse/ODATA-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralf Handl updated ODATA-764:
-----------------------------
Fix Version/s: V4.0_CSD04
Affects Version/s: V4.0_CS02
(was: V4.0_OS)
> Need clarification of valid character values for Edm.String in relation to ATOM (XML 1.0)
> -----------------------------------------------------------------------------------------
>
> Key: ODATA-764
> URL: https://issues.oasis-open.org/browse/ODATA-764
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Improvement
> Components: OData ATOM Format, OData Protocol
> Affects Versions: V4.0_CS02
> Reporter: Evan Ireland
> Fix For: V4.0_CSD04
>
>
> OData CSDL spec states that Edm.String is a "Sequence of UTF-8 characters". However some characters (e.g. ASCII control characters < 32 other than tab, newline, carriage return) are not valid in XML 1.0 (all except NUL are valid in XML 1.1 by the way).
> So there are some valid OData String characters not transmittable using ATOM.
> We ran into this recently with a client which was uploading a stack trace (from C#) that was the result of a client side exception (the client was attempting to create a "log record" entity at the server). The client's stack trace text contained a backspace character (which was actually the reason for the client's failure, so therefore it was important content).
> The client successfully uploaded this information to the server (a proxy) using JSON, then the proxy server tried to use XML to further upload that data to a backend server using XML, which failed due to XML 1.0 limitations (backspace not being transmissable).
> This would appear to indicate that ATOM (with XML 1.0) is not suitable for some legal values of type Edm.String. Even with XML 1.1, the NUL character is not transmissable.
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
