[OASIS Issue Tracker] (ODATA-734) Unicode Facet is inadequate

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/ODATA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52944#comment-52944 ] 

Michael Pizzo commented on ODATA-734:
-------------------------------------

We think it unlikely that client code would check the desired string against the allowable characters of the returned codepage. More likely the client would try the request and then the service would return a 500-range error with a descriptive error message saying that the string contained unsupported characters.

So there is probably not a lot of value in adding an annotation for codepage.

That leaves the question of how we deal with the existing Unicode facet.

Proposal: Services return TRUE if strings support characters outside of the ASCII character set and FALSE if only characters within the ASCII set are supported.

> Unicode Facet is inadequate
> ---------------------------
>
>                 Key: ODATA-734
>                 URL: https://issues.oasis-open.org/browse/ODATA-734
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData CSDL
>    Affects Versions: V4.0_OS
>            Reporter: Matthew Borges
>            Priority: Minor
>             Fix For: V4.0_ERRATA03
>
>
> The Unicode facet appears to be inadequate to handle all possible character sets.  The facet is set to true for unicode character sets and false for ASCII.  The problem is that there exists character sets (such as windows-1252) that is neither unicode nor ASCII.
> In addition, we should also clarify the meaning of the facet in terms of what it applies to.  Does it apply to the character set that is used when the string is on the wire, or the character set in the underlying data store?  My understanding is that it is the character set of the underlying data store, but others may have a different understanding.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)