MétaCan
Menu
Back to cohort
Record W4381513722 · doi:10.1002/tax.12944

(253) Proposal to clarify the option in Art. 7.11 for equivalency to “here designated”

2023· article· en· W4381513722 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueTaxon · 2023
Typearticle
Languageen
FieldComputer Science
TopicLaw, AI, and Intellectual Property
Canadian institutionsRoyal Ontario Museum
Fundersnot available
KeywordsMeaning (existential)Type (biology)AdjectiveCode (set theory)LinguisticsPhraseRank (graph theory)MathematicsWord (group theory)Value (mathematics)Function (biology)NounPhilosophyComputer scienceCombinatoricsProgramming languageEpistemologyStatistics

Abstract

fetched live from OpenAlex

Article 7.11 of the Shenzhen Code (Turland & al. in Regnum Veg. 159. 2018) defines several criteria that must be satisfied for effective designation of a type for a name at or below the rank of genus in the absence of a holotype or original type. Two of these requirements stipulate that the typifying author must employ specific language to achieve this. They must include “the term ‘type’ (typus) or an equivalent” and, after 1 January 2001, they must include “the phrase ‘designated here’ (hic designatus) or an equivalent”. Both of these requirements allow “equivalent” terms or phrases to substitute for the stipulated word(s), and this can lead to differing interpretations as to what is, or is not, considered “equivalent”. By its definition, to be “equivalent” something must be (as a noun), or have the property of being (as an adjective), equal to something else in value, amount, function, meaning, etc. (Oxford Languages, https://www.google.com/search?as_epq=equivalent). This word is widely used elsewhere in the body of the Code, some 30 times under other Articles, in 24 instances (e.g. Art. 8.2: “equivalent preparation”; Art. 10.1: “full equivalent of its type”; also Art. 19.4: “equivalent to that type”; Art. 22.2: “equivalent to exclusion of the type”; Art. 52 Note 3: “equivalent to citation of the name itself”; Art. F.3 Note 2: “equivalent to original material”; Art. H.6.1: “equivalent to a condensed formula”; etc.) specifying what is to be considered equivalent in meaning or effect to something defined elsewhere in this or another Code. A single case (Art. 11.9: “equivalent rank”) is clear enough and requires no further comment. In four remaining cases, which, as in Art. 7.11, likewise stipulate that a specific term must be used, the Code provides further guidance on what the employed equivalent term should be (Art. 16 Note 1: “their equivalents in modern languages”; Art. 9.23 & 40.6: “its abbreviation, or its equivalent in a modern language”). This implies that to include a term equivalent to “type”, the term employed must either be an appropriate abbreviation or be linguistically equivalent, i.e. have the same meaning in another language. Its lack of linguistic equivalence may be the reason *Ex. 16 under Art. 7.11 (“‘standard species’ […] treated as equivalent to ‘type’”) became a voted Example. Under Art. 7.11, Ex. 12 suggests that only a “linguistic equivalent” can replace the phrase “designated here” in the last part of the Article. There are other English expressions, or their equivalents in other modern languages, that would seem to easily meet this criterion, such as “selected here”, “chosen here” or “established here”, which imply an active step having been taken by an author to designate a type in that place. But what about more passive phrases like “indicated here” or “delineated here”? As pointed out by Turland & al. (in Taxon 69: 626–627. 2020) the Code itself makes a distinction between a type designation and a type indication, the latter lacking the explicit nature of the former, so should these be equivalent phrases? And what about active phrases having slightly different meaning, such as “accepted here”, or in the case of a second- or later-step typification a phrase like “restricted here” or “narrowed here”, or when a previous typification was imprecise: “clarified here” or “detailed here”? Or phrases like “altered here”, “corrected here”, “modified here” or “superseded here” when the previous typification was ineffective or improper? Given the plausible acceptability of many alternative phrases that might not be considered equivalent to “designated here”, what seems to be necessary in order to determine if a type designation has been achieved on or after 1 January 2001 is the author's usage of some expression that will demonstrate their clear intent to carry out an act of typification in that place. This reflects the Rapporteurs’ comment (Greuter & Hawksworth in Taxon 48: 75. 1999) on the original proposal that it “would eliminate for the future the risk of ‘incidental type designations’ which has often caused difficulties in the past”. We therefore propose the following amendment: “7.11. For purposes of priority (Art. 9.19, 9.20, and 10.5), designation of a type is achieved only if the type is definitely accepted as such by the typifying author, if the type element is clearly indicated by direct citation including the term “type” (typus) or an equivalent, and, on or after 1 January 2001, if the typification statement includes the phrase “designated here” (hic designatus) or an equivalent a similar expression demonstrating the author's intent to designate a type there.”

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.901
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.001

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.060
GPT teacher head0.287
Teacher spread0.227 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it