You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 17, 2023. It is now read-only.
...This references names that I am not seeing in the JSON response. Perhaps this is covered in #209 but I thought it would be lower-hanging fruit to just update those strings in the existing docs.
The text was updated successfully, but these errors were encountered:
JRice
changed the title
Documentation for canonicalForm
Documentation for canonicalName
Jan 28, 2019
@JRice you probably did not see these names because in Go version of gnparser (they are called CanonicalName->simple and CanonicalName->full in contrast with Scala parser. The reason for chaning was omitting hybrid signs in simple for named hybrids. Many times people omit hybrid sign for named hybrids, and we do want to match Iris germanica and Iris x germanica using simple canonical form. So simple form is for matching purposes, and full form is for presentation purposes.
We changed the name because valueRanked now includes named hybrids, and its semantic meaning drifted as a result. I added an issue for Go parser https://gitlab.com/gogna/gnparser/issues/44
https://github.com/GlobalNamesArchitecture/gnparser/blob/master/README.rst#getting-the-simplest-possible-canonical-form
...This references names that I am not seeing in the JSON response. Perhaps this is covered in #209 but I thought it would be lower-hanging fruit to just update those strings in the existing docs.
The text was updated successfully, but these errors were encountered: