commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruno P. Kinoshita (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TEXT-21) Have a clear distinction between Edit Distance, String Similarity, Score, Metric, etc
Date Wed, 12 Oct 2016 07:59:20 GMT

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

Bruno P. Kinoshita commented on TEXT-21:
----------------------------------------

Similar libraries with distance/similarity/metrics.

* https://github.com/Simmetrics/simmetrics
* https://github.com/tdebatty/java-string-similarity/

> Have a clear distinction between Edit Distance, String Similarity, Score, Metric, etc
> -------------------------------------------------------------------------------------
>
>                 Key: TEXT-21
>                 URL: https://issues.apache.org/jira/browse/TEXT-21
>             Project: Commons Text
>          Issue Type: Improvement
>            Reporter: Bruno P. Kinoshita
>            Assignee: Bruno P. Kinoshita
>
> From LANG-1269.
> A user reported a nomenclature issue in [lang], which occurs in [text] as well.
> Currently we have an interface called EditDistance, with the following implementations:
> * CosineDistance
> * HammingDistance
> * JaroWrinklerDistance
> * and LevenshteinDistance
> JaroWrinkler is actually a similarity score, and not a distance. We have other classes
in the oact.similarity package too.
> * CosineSimilarity
> * FuzzyScore
> We need to provide users a clear distinction on what we call an edit distance, similarity
or score.



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

Mime
View raw message