commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Tompkins (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TEXT-21) Have a clear distinction between Edit Distance, String Similarity, Score, Metric, etc
Date Thu, 17 Nov 2016 12:15:58 GMT

     [ https://issues.apache.org/jira/browse/TEXT-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rob Tompkins resolved TEXT-21.
------------------------------
       Resolution: Implemented
         Assignee: Rob Tompkins  (was: Bruno P. Kinoshita)
    Fix Version/s: 1.0

> 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: Rob Tompkins
>             Fix For: 1.0
>
>
> 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