OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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


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

Michael Pizzo updated ODATA-734:
--------------------------------

    Proposal: 
We agreed in 2014-11-13 that the facet is meant to represent the set of characters that the service is able to support for this property.

Further investigation is required to understand whether we can make Unicode==NotAscii or if we need to deprecate the facet and add a capabilities vocabulary term.

This facet is intended to describe possible limitations with what the service is able to support for persisting properties.

If the service is able to support conversions from Unicode to (an underlying) character set, then it should report Unicode=true. 

If the service is only able to support conversions from ASCII to an underlying character set, then it should report Unicode=false.

> 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)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]