Next in thread → Next in month →

[OASIS Issue Tracker] (CAMP-227) 7.3.3.1.2 String - Sort ordering is not meaningfully defined

From
OASIS Issues Tracker <>
Date
2017-08-24T19:25:04+00:00
ID
Thread
[OASIS Issue Tracker] (CAMP-227) 7.3.3.1.2 String - Sort ordering is not meaningfully defined
[ https://issues.oasis-open.org/browse/CAMP-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67220#comment-67220 ] 

Anish Karmarkar commented on CAMP-227:
--------------------------------------

On the 2017-08-03 telcon (https://www.oasis-open.org/apps/org/workgroup/camp/download.php/61348/20170803Minutes.txt) the TC agreed to the following:

original text "Based on the binary comparison of the Unicode characters in the String."
proposed resolution: replace text with "Based on unicode collation algorithm [ref]"
ref is: http://www.unicode.org/reports/tr10/tr10-36.html


> 7.3.3.1.2 String - Sort ordering is not meaningfully defined
> ------------------------------------------------------------
>
>                 Key: CAMP-227
>                 URL: https://issues.oasis-open.org/browse/CAMP-227
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>         Environment: Technical
>            Reporter: Chet Ensign
>
> 7.3.3.1.2 String reads:
> *****
> Based on the binary comparison of the Unicode characters in the String.
> *****
> This is not a meaningful definition of sort order for Unicode characters, or in the words of Unicode® Technical Standard #10 UNICODE COLLATION ALGORITHM, http://unicode.org/reports/tr10/, 
> *****
> The position of characters in the Unicode code charts does not specify their sort order.
> *****
> Collation (sorting) is a complex issue and covered by Unicode® Technical Standard #10 UNICODE COLLATION ALGORITHM in great detail. 
> Ad hoc attempts to define Unicode collation lead to bad ends. 



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
Next in thread → Next in month →