[ 
https://issues.apache.org/jira/browse/COMMONSRDF-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824368#comment-15824368
 ] 

ASF GitHub Bot commented on COMMONSRDF-51:
------------------------------------------

Github user stain commented on the issue:

    https://github.com/apache/commons-rdf/pull/30
  
    There seems to be consensus on 
http://lists.w3.org/Archives/Public/public-rdf-comments/2017Jan/thread.html and 
http://lists.w3.org/Archives/Public/semantic-web/2017Jan/thread.html in the 
_Are literal language tags case sensitive?_ threads that it is not meant to be 
a change from RDF 1.0 - that language tags should still be compared case 
insensitively.
    
    That should be inline with what this PR suggests - case insensitive in 
`.equals()` and `.hashCode()`
    
    Do you agree on that line, @afs and @ansell ..?


> RDF-1.1 specifies that language tags need to be compared using lower-case
> -------------------------------------------------------------------------
>
>                 Key: COMMONSRDF-51
>                 URL: https://issues.apache.org/jira/browse/COMMONSRDF-51
>             Project: Apache Commons RDF
>          Issue Type: Bug
>          Components: api
>    Affects Versions: 0.3.0
>            Reporter: Peter Ansell
>            Assignee: Stian Soiland-Reyes
>
> The [RDF-1.1 specification states that the [value space of Literal language 
> tags is 
> lowercase|https://www.w3.org/TR/rdf11-concepts/#section-Graph-Literal], which 
> does not conflict with the case-insensitive specification in BCP47. The 
> Literal.equals and Literal.hashCode API contracts should specify that 
> language tags must be compared using lowercase, even if they are otherwise 
> stored and returned as upper-case by getLanguageTag. The API currently has 
> incorrect language by saying "character-by-character" for language tag 
> comparisons, as that implies case-sensitive comparisons are used.
> The lowercasing must also be done using a locale that is consistent (known 
> example where lowercase and uppercase do not roundtrip as expected for 
> US-ASCII characters is Turkish [1]), so I would recommend actually stating 
> that .toLowerCase(Locale.ENGLISH) is used.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to