Wikidata talk:Database reports/Constraint violations/P225

From Wikidata
Jump to navigation Jump to search

Constraint violation of taxon name (P225) View with SQID

Archive

List[edit]

cf. @Wikispecies

genera[edit]

There are over five thousand generic names that are used both under the ICZN and the ICNafp, some of these are:

a[edit]

b[edit]

c[edit]

d-f[edit]

g-h[edit]

i-l[edit]

m-q[edit]

r-s[edit]

t-z[edit]

subgenera[edit]

There are also a number of entries of a genus and a subgenus (that is, "coordinate" names, with the same spelling, same date, same type. Only for animals):

species[edit]

There is also a handful of species:

asymmetrical[edit]

different taxonomies[edit]

The same name used for differently circumscribed taxa:

known problem cases (unresolved)[edit]

weird[edit]

weird, but different[edit]

violations of Wikipedia policy (at least 50% fictitious taxa)[edit]

violations

first heading[edit]

Add them simply that way. --Succu (talk) 10:49, 26 November 2013 (UTC)[reply]

It may be that this would work very well, but readability is very poor. - Brya (talk) 11:55, 26 November 2013 (UTC)[reply]

Hemihomonyms?[edit]

@Brya, Succu: Would it be useful to record them directly via a new property that could be named "hemihomonym"? [1] There is the Hemihomonyms database, but maybe we could generate our own one. Korg (talk) 01:45, 11 October 2016 (UTC)[reply]

These are not hemihomonyms, but rather potential combinations. - Brya (talk) 02:49, 11 October 2016 (UTC)[reply]
Ok, I see, but are there still real hemihomonyms or the concept is questionable? Maybe you're referrring to their conditional nature, so names shouldn't be labelled as such? Korg (talk) 11:19, 11 October 2016 (UTC)[reply]
Yes and no. There is no formal concept "hemihomonym", but the term is in informal use. IIRC there are actually two different informal concepts "hemihomonym" (or rather, two areas where they occur) ... - Brya (talk) 16:25, 11 October 2016 (UTC)[reply]
Thank you for the clarification. Korg (talk) 21:56, 11 October 2016 (UTC)[reply]