wiki-archive/twiki/data/UBIF/LinneanCoreDefinitions.txt,v

head	1.35;
access;
symbols;
locks; strict;
comment	@# @;


1.35
date	2011.09.23.17.03.14;	author GregorHagedorn;	state Exp;
branches;
next	1.34;

1.34
date	2007.03.06.17.30.00;	author TWikiGuest;	state Exp;
branches;
next	1.33;

1.33
date	2006.05.16.21.01.27;	author GregorHagedorn;	state Exp;
branches;
next	1.32;

1.32
date	2006.05.10.08.57.51;	author GregorHagedorn;	state Exp;
branches;
next	1.31;

1.31
date	2005.03.21.22.42.31;	author JenniferForman;	state Exp;
branches;
next	1.30;

1.30
date	2005.01.12.18.00.00;	author FrankBungartz;	state Exp;
branches;
next	1.29;

1.29
date	2005.01.12.14.56.48;	author FrankBungartz;	state Exp;
branches;
next	1.28;

1.28
date	2004.12.16.15.39.44;	author GregorHagedorn;	state Exp;
branches;
next	1.27;

1.27
date	2004.11.19.14.37.24;	author GregorHagedorn;	state Exp;
branches;
next	1.26;

1.26
date	2004.11.16.17.48.48;	author GregorHagedorn;	state Exp;
branches;
next	1.25;

1.25
date	2004.11.16.10.32.25;	author GregorHagedorn;	state Exp;
branches;
next	1.24;

1.24
date	2004.11.12.16.36.11;	author NozomiJamesYtow;	state Exp;
branches;
next	1.23;

1.23
date	2004.11.09.15.07.41;	author GregorHagedorn;	state Exp;
branches;
next	1.22;

1.22
date	2004.11.07.08.39.21;	author NozomiJamesYtow;	state Exp;
branches;
next	1.21;

1.21
date	2004.11.05.23.33.00;	author NozomiJamesYtow;	state Exp;
branches;
next	1.20;

1.20
date	2004.11.04.14.09.00;	author GregorHagedorn;	state Exp;
branches;
next	1.19;

1.19
date	2004.11.04.11.20.00;	author GregorHagedorn;	state Exp;
branches;
next	1.18;

1.18
date	2004.11.04.10.04.34;	author GregorHagedorn;	state Exp;
branches;
next	1.17;

1.17
date	2004.11.02.20.00.00;	author NozomiJamesYtow;	state Exp;
branches;
next	1.16;

1.16
date	2004.11.01.12.09.00;	author GregorHagedorn;	state Exp;
branches;
next	1.15;

1.15
date	2004.11.01.11.09.28;	author NozomiJamesYtow;	state Exp;
branches;
next	1.14;

1.14
date	2004.11.01.09.17.27;	author GregorHagedorn;	state Exp;
branches;
next	1.13;

1.13
date	2004.10.31.19.52.00;	author GregorHagedorn;	state Exp;
branches;
next	1.12;

1.12
date	2004.10.31.09.03.00;	author GregorHagedorn;	state Exp;
branches;
next	1.11;

1.11
date	2004.10.31.06.01.00;	author RichardPyle;	state Exp;
branches;
next	1.10;

1.10
date	2004.10.31.04.56.29;	author NozomiJamesYtow;	state Exp;
branches;
next	1.9;

1.9
date	2004.10.31.03.29.49;	author RichardPyle;	state Exp;
branches;
next	1.8;

1.8
date	2004.10.31.01.25.00;	author NozomiJamesYtow;	state Exp;
branches;
next	1.7;

1.7
date	2004.10.30.23.59.00;	author NozomiJamesYtow;	state Exp;
branches;
next	1.6;

1.6
date	2004.10.30.23.20.05;	author GregorHagedorn;	state Exp;
branches;
next	1.5;

1.5
date	2004.10.30.21.30.00;	author RichardPyle;	state Exp;
branches;
next	1.4;

1.4
date	2004.10.30.19.17.36;	author NozomiJamesYtow;	state Exp;
branches;
next	1.3;

1.3
date	2004.10.30.17.55.00;	author RichardPyle;	state Exp;
branches;
next	1.2;

1.2
date	2004.10.30.01.41.53;	author NozomiJamesYtow;	state Exp;
branches;
next	1.1;

1.1
date	2004.10.29.21.53.00;	author RichardPyle;	state Exp;
branches;
next	;


desc
@none
@


1.35
log
@none
@
text
@%META:TOPICINFO{author="GregorHagedorn" date="1316797394" format="1.1" version="1.35"}%
%META:TOPICPARENT{name="LinneanCore"}%
---+!! %TOPIC%

These are some definitions proposed for use in further discussion.  Note that the word "name" is not on this list without some sort of qualification. We should all try to avoid using the word "name" without an explicit context. All definitions assume the scope of nomenclature defined for <nop>LinneanCore's domain, which is *tentatively* the Code-governed scientific names, plus possibly Trade Names, plus possibly some non-code-governed extensions of code-governed names [races, etc.], plus Linnean-type names used above the rank of Family (not technically governed by the Codes of Nomenclature -- at least not ICZN/ICBN.  Please feel free to comment/amend/etc., using the topics provided at the end of each definition. - 30 Oct 2004

#RankDefinition
   <b>Rank</b>: A specific, most-precise taxonomic rank (including intermediate ranks, such as "Subgenus", "Subspecies", etc.). See [[TaxonomicRankEnum][TaxonomicRankEnum]]. -- [[TaxonomicRankDiscussion][Discussion]]

#RankGroupDefinition
   <b>Rank-group</b>: The "full" ranking groups. Within the context of Codes of nomenclature, these include only "Family-group", "Genus-group", and "Species-group".  However, we will also need to deal with "Order-group", "Class-group", "Phylum-group", and "Kingdom-group" entities as well. Although "Phylum-group" is Zoo-centric, "Division" is used for different [[#RankDefinition][ranks]] by different disciplines (even different sub-disciplines within Zoology), and "Phylum" is only used for one [[#RankDefinition][ranks]]. Therefore, it makes more sense to use "Phylum-group", "Phylum", "Subphylum", etc. -- and assume that these are all precisely synonymous with the botanical "Division" equivalencies. -- [[LCRankGroupDiscussion][Discussion]]

#NameDefinition
   <b>Name</b>: A relationship between a name-literal (and hence name-string) and a named-object.  It is recommeded to avoid this word as possible, but sometime inevitable.

#NameLiteralDefinition
   <b>Name-literal</b>: A literal word (or words) designating at least one object.  A single name-literal may designate multiple objects (homonymy) and multiple name-literals may designate single object (synonymy).  A name-literal is an abstraction of a set of [[#NameUsageDefinition][name-usages]].  A [[#NameStringDefinition][name-string]] is an electronic representation of a name-literal.  A name-literal may have [[#VariantSpellingDefinition][variant spellings]]; each variant is represented by a [[#NameStringDefinition][name-string]]. -- [[LCNameLiteralDiscussion][Discussion]]

#NameStringDefinition
   <b>Name-string</b>:  The Unicode string equivalent of [[#NameLiteralDefinition][name-literal]] printed on paper or represented in an electronic document to indicate a scientific name within the scope of <nop>LinneanCore's domain. It does *not* include authorship, but does include markup such as parentheses around infrageneric/supraspecific [[#NameUnitDefinition][Name-units]], and infraspecific rank terms (e.g., subsp., var., f. etc.). -- [[LCNameStringDiscussion][Discussion]]

#NameStringWithAuthorshipDefinition
   <b>Name-string&nbsp;with&nbsp;authorship</b>: A [[#NameStringDefinition][Name-string]] that includes the Code-appropriate authorships embedded within the [[#NameStringDefinition][name-string]]. -- [[LCNameStringDiscussionWithAuthorship][Discussion]]

#NameUnitDefinition
   <b>Name-unit</b>: A portion of a multi-part [[#NameStringDefinition][name-string]] that constitutes one discrete [[#RankDefinition][Rank]]. There do not appear to be any cases where a single name-unit would contain a space (" "), but it may include a hyphen ("-") or other characters outside the standard letters.  It is a token composing name-string, technically. -- [[LCNameUnitDiscussion][Discussion]]

#NameUsageDefinition
   <b>Name-usage</b>: The appearance of a [[#NameStringDefinition][Name-string]] within a [[#ReferenceDefinition][Reference]]. -- [[LCNameUsageDiscussion][Discussion]]

---

(Here some preliminary attempt by Gregor to clarify the Protonym/Basionym confusion, therefore for the moment not alphabetical:)

#BasionymDefinition
   <b>Basionym</b>: A role a name can have in relation to another name which is explicitly based upon the basionym name. Specifically, in genus or rank changing recombinations ("comb. nov.", "stat. nov.") the new name is based on a basionym name. The basionym of a name is always a [[#ProtonymDefinition][Protonym]] (= [[#OriginalNameDefinition][Original Name]] or [[#ReplacementNameDefinition][Replacement Name]]). The role of the basionym is very similar to the role of the [[#ReplacedSynonymDefinition][Replaced Synonym]] in the case of "nom. nov.". [[LCProtonymDiscussion][Discussion]] <!-- [[#BasionymDefinition][Basionym]] -->

#BasalNameDefinition
   <b>Basal&nbsp;Name</b>&nbsp;or&nbsp;<b>basonym</b>:  A role name for a name in a nomenclatural relationship, including [[#BasionymDefinition][Basionym]] and [[#ReplacedSynonymDefinition][Replaced Synonym]]. -- [[LCProtonymDiscussion][Discussion]] <!-- [[#BasalNameDefinition][Basal Name]] -->

<b>Comment by F. Bungartz, Botanische Staatssammlung M<>nchen, 12. January 2005</b>:
This seperate definition distinguishing basal name from basionym does not make any sense to me! Basonym, Basinym and Basionym are only spelling variants of essentially the same (see Dictionary of Fungi, 9th edition, 2001, page 61)! I do not understand the comment in the Discussion, that the Basionym (with "i") is supposedly the oldest Basal Name (= Basonym, without "i"). There are never several basal name! Every recombination goes back to the earliest legitimate name, which acts as a basal name (= basionym, basonym, basinym). To suggest that there is a succession of several basal names is nonsence (at least in Botanical Nomenclature). If the Zoological Nomenclature does not know the term basionym, how can it recognize the term basonym? This hardly makes sense.

#ReplacedSynonymDefinition
   <b>Replaced&nbsp;Synonym</b>: A role a name can have in relation to another name which is explicitly based upon the replaced synonym name. For example, if genus or rank changing recombinations would result in the creation of homonyms, a new epithet name has to be introduced to replace the previous epithet of the "Replaced Synonym". The replaced&nbsp;synonym of a name is always a [[#ProtonymDefinition][Protonym]] (= [[#OriginalNameDefinition][Original Name]] or [[#ReplacementNameDefinition][Replacement Name]]). This role is very close to a [[#BasionymDefinition][Basionym]], but ICBN (33.3) avoids the term basionym and uses this term instead. [[LCProtonymDiscussion][Discussion]] <!-- [[#ReplacedSynonymDefinition][Replaced Synonym]] -->

#ReplacementNameDefinition
   <b>Replacement&nbsp;Name</b>: A new name that replaces an existing name (= [[#ReplacedSynonymDefinition][Replaced Synonym]]). [[LCProtonymDiscussion][Discussion]] <!-- [[#ReplacementNameDefinition][Replacement Name]] -->


#OriginalNameDefinition
   <b>Original&nbsp;Name</b>: A name that introduces a new epithet and originally designates a type specimen (or other typification, including iconotype etc.). Multiple original names may accidentially based on the same type specimen. However, cases where a name is explicitly based to an older name (comb. nov,, stat. nov., nom. nov.) should not be considered original names. -- [[LCProtonymDiscussion][Discussion]] <!-- [[#OriginalNameDefinition][Original Name]] -->

#ProtonymDefinition
   <b>Protonym</b>: A name that introduced a new epithet the first time. This is the case in [[#OriginalNameDefinition][Original Names]] (not based on previously published nomenclatural names) and in the case of [[#ReplacementNameDefinition][Replacement Names]] (= "nom. nov.", = avowed substitute). -- [[LCProtonymDiscussion][Discussion]] <!-- [[#ProtonymDefinition][Protonym]] -->

<b>Comment by F. Bungartz, Botanische Staatssammlung M<>nchen, 12. January 2005</b>:

This definition is NOT in accordance with the concept of a protonym as originally introduced by Donk (1960, original citations see below). Donk emphasizes that a protonym is a name that has effectively, but not validly been published. The definition given here, at the Linnean Core Website, does not make any statement about the way a protonym was published. On the contrary, it only suggests, that ANY name that ever was introduced for the first time is a protonym. This is not correct. Original names that have both been effectively and validly published are not protonyms, even though the definition presented here would just suggest that. Also, Replacement Names (= "nom. nov.", = avowed substitute) can be published both effectively as well as validly. Therefore, both Original Names as well as Replacement Names are NOT necessarily identical with protonyms!!!

In my opinion there is no reason to treat both Original Name and Replacement Name under one common definition. They are not the same and have little in common! An Original Name is ANY first name ever introduced for a species. It is only available for use if effectively AND validly published. However, any original name may nevertheless constitute a later homonym, i.e., if it is LITERALLY the same name as another name, which was previously effectively and validly published, but obviously based on a different type. In that case the particular name (the later homonym) is illegitimate and a new name may be introduced as a legitimate Replacement Name (= Replacement Name for an Original Name). This kind of Replacement Name will persist in all new combinations, i.e., it will become a Basionym for any new combination that takes place.

A second, very different case, is the introduction of a replacement name if otherwise a new combination would create an illegitimate name (= Replacement Name for an illegitimate New Combination). This is the case for a species epithet that cannot be transferred into another genus because this would there create a name identical to a name that already exists. This second kind of Replacement Name (a combination with a new species epithet) will disappear as soon as another combination is made. Thus, this second kind of Replacement Name will never become a Basionym because any a second recombination has to use the original epithet instead of the newly introduced epithet.


If indeed it is necessary to recognize a term that combines both Original Name and Replacement Name, I would suggest to use "Earliest Legitimate Name". The earliest legitimate name is a name that is effectively and validly published AND has no earlier homonym. It will most often be an original name but it may also be a replacement name of an original name that was a later homonym.


Below the relevant citations for protonym...


Dictionary of Fungi (9th edition, 2001, page 427): 

"...
Protonym (in nomenclature), a name effectively but not validly published after the starting point for the group.
..."

Donk, Persoonia 1: 175, (1960, page 175): 

"...
Protonym. Neither a devalidated nor validly published, though effectively published, name, taken up and validly published afterwards.
..."
and before, Donk, Persoonia 1: 175, (1960, page 174):
"...
Devalidated names are those names that would have been validly published if no later starting-points had been introduced.
..."



#NewCombinationDefinition
   <b>New&nbsp;combination</b>: A re-use of a previously-existing [[#ProtonymDefinition][Protonym]] (= [[#OriginalNameDefinition][Original Name]] or [[#ReplacementNameDefinition][Replacement Names]]) in a different nomenclatural context.  In the botany world these are thought of as discrete "names", separate from their [[#ProtonymDefinition][protonyms]]; but in Zoology they are usually thought of as merely different contextual usages of a pre-existing "name" ([[#ProtonymDefinition][protonym]]).  Although ICZN does not have any rules to determine which "revised contextual usages" of pre-existing [[#ProtonymDefinition][protonyms]] constitute an "official" New Combination, in most cases it will be more or less unambiguously determinable who first placed a pre-existing species epithet into a different nomenclatural context. In any case, New combinations ONLY in the context of a particular kind of usage that represents a subsequent use of a pre-existing [[#ProtonymDefinition][protonym]] in a novel nomenclatural context (e.g., the first placement of an existing species epithet into a different genus than the epithet was originally described in (i.e., the nomenclatural context of it's [[#ProtonymDefinition][Protonym]]). -- [[LCNewCombinationDiscussion][Discussion]]

---

#VariantSpellingDefinition
   <b>Variant&nbsp;spelling</b>: This term refers to variant spellings (i.e., slightly different [[#LCNameStringDiscussion][Name-strings]]) used for what is otherwise a pre-existing [[#ProtonymDefinition][Protonym]] or [[#NewCombinationDefinition][New Combination]].  These include intentional variations (e.g., alternate gender forms of Species-group epithets), as well as unintentional variations (i.e., [[#LapsusDefinition][Lapsus]]). Variant spellings exist ONLY in the context of a [[#NameUsageDefinition][Name-usage]]. -- [[LCVariantSpellingDiscussion][Discussion]]

#LapsusDefinition
   <b>Lapsus</b>: A particular kind of [[#VariantSpellingDefinition][Variant spelling]] that represents an unintentional alternate [[#NameStringDefinition][Name-string]] (e. g., typographical error). -- [[LCLapsusDiscussion][Discussion]]
 
#ReferenceDefinition
   <b>Reference</b>: Any form of DOCUMENTED date-stamped instance of one or more Authors (Agents).  This is broadly defined to include forms of documentation outside the context of [[#PublicationDefinition][Publications]]. "Documented" means that at least one physical (paper) or "permanent" electronic representation/facsimilie of information presented by Agent-Authors at a specific date/time is archived somewhere. Besides [[#PublicationDefinition][Publications]], these can include things like written personal communication (or archived representation of verbal personal communication), specimen labels, field notebooks, etc., etc. -- [[LCReferenceDiscussion][Discussion]]

#DocumentationDefinition
   <b>Documentation</b>: Synonym of the [[#ReferenceDefinition][Reference]] with less ambiguity; the word 'reference' is also used as relationship, just like the word 'name' can be used either name-string or name-object-relationship. -- Discussion on [[LCReferenceDiscussion][Reference]] and [[LCPublicationDiscussion][Publication]]

#PublicationDefinition
   <b>Publication</b>: A special subset of [[#ReferenceDefinition][References]] that have been "published" in some way (perhaps best to define "publication" in accordance with ICZN/ICBN rules governing publications????) -- [[LCPublicationDiscussion][Discussion]]

#UnpublishedDocumentationDefinition
   <b>Unpublished&nbsp;Documentation</b>: Permanently documented information (e.g. on paper, in digital format) that has not been published to a wider audience. This includes letters, laboratory or field books. It does not include forms of information attribution like "pers. comm.", which are not documented in any way. (Gregor) -- [[LCUnpublishedDocumentationDiscussion][Discussion]]

---

(see also LinneanCoreSomePrivateConceptDefinitions)@


1.34
log
@Added topic name via script
@
text
@d1 2
a4 2
%META:TOPICINFO{author="GregorHagedorn" date="1147813287" format="1.1" version="1.33"}%
%META:TOPICPARENT{name="LinneanCore"}%
d8 1
a8 1
   <b>Rank</b>: A specific, most-precise taxonomic rank (including intermediate ranks, such as "Subgenus", "Subspecies", etc.). See [[http://wiki.cs.umb.edu/twiki/pub/UBIF/EnumeratedValues/UBIF-Docu-Enumerations.html#TaxonomicRankEnum][TaxonomicRankEnum]]. -- [[TaxonomicRankDiscussion][Discussion]]
@


1.33
log
@none
@
text
@d1 2
@


1.32
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="GregorHagedorn" date="1147251471" format="1.1" version="1.32"}%
d6 1
a6 1
   <b>Rank</b>: A specific, most-precise taxonomic rank (including intermediate ranks, such as "Subgenus", "Subspecies", etc.). See [[http://wiki.cs.umb.edu/twiki/pub/UBIF/EnumeratedValues/UBIF-Docu-Enumerations.html#TaxonomicRankEnum][TaxonomicRankEum]]. -- [[TaxonomicRankDiscussion][Discussion]]
d113 1
a113 1
(see also LinneanCoreSomePrivateConceptDefinitions)
@


1.31
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="JenniferForman" date="1111444951" format="1.0" version="1.31"}%
d6 1
a6 1
	<b>Rank</b>: A specific, most-precise taxonomic rank (including intermediate ranks, such as "Subgenus", "Subspecies", etc.). See [[http://wiki.cs.umb.edu/twiki/pub/UBIF/EnumerationTypes/UBIF-Docu-Enumerations.html#TaxonomicRankEnum][TaxonomicRankEum]]. -- [[TaxonomicRankDiscussion][Discussion]]
d9 1
a9 1
	<b>Rank-group</b>: The "full" ranking groups. Within the context of Codes of nomenclature, these include only "Family-group", "Genus-group", and "Species-group".  However, we will also need to deal with "Order-group", "Class-group", "Phylum-group", and "Kingdom-group" entities as well. Although "Phylum-group" is Zoo-centric, "Division" is used for different [[#RankDefinition][ranks]] by different disciplines (even different sub-disciplines within Zoology), and "Phylum" is only used for one [[#RankDefinition][ranks]]. Therefore, it makes more sense to use "Phylum-group", "Phylum", "Subphylum", etc. -- and assume that these are all precisely synonymous with the botanical "Division" equivalencies. -- [[LCRankGroupDiscussion][Discussion]]
d12 1
a12 1
	<b>Name</b>: A relationship between a name-literal (and hence name-string) and a named-object.  It is recommeded to avoid this word as possible, but sometime inevitable.
d15 1
a15 1
	<b>Name-literal</b>: A literal word (or words) designating at least one object.  A single name-literal may designate multiple objects (homonymy) and multiple name-literals may designate single object (synonymy).  A name-literal is an abstraction of a set of [[#NameUsageDefinition][name-usages]].  A [[#NameStringDefinition][name-string]] is an electronic representation of a name-literal.  A name-literal may have [[#VariantSpellingDefinition][variant spellings]]; each variant is represented by a [[#NameStringDefinition][name-string]]. -- [[LCNameLiteralDiscussion][Discussion]]
d18 1
a18 1
	<b>Name-string</b>:  The Unicode string equivalent of [[#NameLiteralDefinition][name-literal]] printed on paper or represented in an electronic document to indicate a scientific name within the scope of <nop>LinneanCore's domain. It does *not* include authorship, but does include markup such as parentheses around infrageneric/supraspecific [[#NameUnitDefinition][Name-units]], and infraspecific rank terms (e.g., subsp., var., f. etc.). -- [[LCNameStringDiscussion][Discussion]]
d21 1
a21 1
	<b>Name-string&nbsp;with&nbsp;authorship</b>: A [[#NameStringDefinition][Name-string]] that includes the Code-appropriate authorships embedded within the [[#NameStringDefinition][name-string]]. -- [[LCNameStringDiscussionWithAuthorship][Discussion]]
d24 1
a24 1
	<b>Name-unit</b>: A portion of a multi-part [[#NameStringDefinition][name-string]] that constitutes one discrete [[#RankDefinition][Rank]]. There do not appear to be any cases where a single name-unit would contain a space (" "), but it may include a hyphen ("-") or other characters outside the standard letters.  It is a token composing name-string, technically. -- [[LCNameUnitDiscussion][Discussion]]
d27 1
a27 1
	<b>Name-usage</b>: The appearance of a [[#NameStringDefinition][Name-string]] within a [[#ReferenceDefinition][Reference]]. -- [[LCNameUsageDiscussion][Discussion]]
d34 1
a34 1
	<b>Basionym</b>: A role a name can have in relation to another name which is explicitly based upon the basionym name. Specifically, in genus or rank changing recombinations ("comb. nov.", "stat. nov.") the new name is based on a basionym name. The basionym of a name is always a [[#ProtonymDefinition][Protonym]] (= [[#OriginalNameDefinition][Original Name]] or [[#ReplacementNameDefinition][Replacement Name]]). The role of the basionym is very similar to the role of the [[#ReplacedSynonymDefinition][Replaced Synonym]] in the case of "nom. nov.". [[LCProtonymDiscussion][Discussion]] <!-- [[#BasionymDefinition][Basionym]] -->
d37 1
a37 1
	<b>Basal&nbsp;Name</b>&nbsp;or&nbsp;<b>basonym</b>:  A role name for a name in a nomenclatural relationship, including [[#BasionymDefinition][Basionym]] and [[#ReplacedSynonymDefinition][Replaced Synonym]]. -- [[LCProtonymDiscussion][Discussion]] <!-- [[#BasalNameDefinition][Basal Name]] -->
d43 1
a43 1
	<b>Replaced&nbsp;Synonym</b>: A role a name can have in relation to another name which is explicitly based upon the replaced synonym name. For example, if genus or rank changing recombinations would result in the creation of homonyms, a new epithet name has to be introduced to replace the previous epithet of the "Replaced Synonym". The replaced&nbsp;synonym of a name is always a [[#ProtonymDefinition][Protonym]] (= [[#OriginalNameDefinition][Original Name]] or [[#ReplacementNameDefinition][Replacement Name]]). This role is very close to a [[#BasionymDefinition][Basionym]], but ICBN (33.3) avoids the term basionym and uses this term instead. [[LCProtonymDiscussion][Discussion]] <!-- [[#ReplacedSynonymDefinition][Replaced Synonym]] -->
d46 1
a46 1
	<b>Replacement&nbsp;Name</b>: A new name that replaces an existing name (= [[#ReplacedSynonymDefinition][Replaced Synonym]]). [[LCProtonymDiscussion][Discussion]] <!-- [[#ReplacementNameDefinition][Replacement Name]] -->
d50 1
a50 1
	<b>Original&nbsp;Name</b>: A name that introduces a new epithet and originally designates a type specimen (or other typification, including iconotype etc.). Multiple original names may accidentially based on the same type specimen. However, cases where a name is explicitly based to an older name (comb. nov,, stat. nov., nom. nov.) should not be considered original names. -- [[LCProtonymDiscussion][Discussion]] <!-- [[#OriginalNameDefinition][Original Name]] -->
d53 1
a53 1
	<b>Protonym</b>: A name that introduced a new epithet the first time. This is the case in [[#OriginalNameDefinition][Original Names]] (not based on previously published nomenclatural names) and in the case of [[#ReplacementNameDefinition][Replacement Names]] (= "nom. nov.", = avowed substitute). -- [[LCProtonymDiscussion][Discussion]] <!-- [[#ProtonymDefinition][Protonym]] -->
d89 1
a89 1
	<b>New&nbsp;combination</b>: A re-use of a previously-existing [[#ProtonymDefinition][Protonym]] (= [[#OriginalNameDefinition][Original Name]] or [[#ReplacementNameDefinition][Replacement Names]]) in a different nomenclatural context.  In the botany world these are thought of as discrete "names", separate from their [[#ProtonymDefinition][protonyms]]; but in Zoology they are usually thought of as merely different contextual usages of a pre-existing "name" ([[#ProtonymDefinition][protonym]]).  Although ICZN does not have any rules to determine which "revised contextual usages" of pre-existing [[#ProtonymDefinition][protonyms]] constitute an "official" New Combination, in most cases it will be more or less unambiguously determinable who first placed a pre-existing species epithet into a different nomenclatural context. In any case, New combinations ONLY in the context of a particular kind of usage that represents a subsequent use of a pre-existing [[#ProtonymDefinition][protonym]] in a novel nomenclatural context (e.g., the first placement of an existing species epithet into a different genus than the epithet was originally described in (i.e., the nomenclatural context of it's [[#ProtonymDefinition][Protonym]]). -- [[LCNewCombinationDiscussion][Discussion]]
d94 1
a94 1
	<b>Variant&nbsp;spelling</b>: This term refers to variant spellings (i.e., slightly different [[#LCNameStringDiscussion][Name-strings]]) used for what is otherwise a pre-existing [[#ProtonymDefinition][Protonym]] or [[#NewCombinationDefinition][New Combination]].  These include intentional variations (e.g., alternate gender forms of Species-group epithets), as well as unintentional variations (i.e., [[#LapsusDefinition][Lapsus]]). Variant spellings exist ONLY in the context of a [[#NameUsageDefinition][Name-usage]]. -- [[LCVariantSpellingDiscussion][Discussion]]
d97 1
a97 1
	<b>Lapsus</b>: A particular kind of [[#VariantSpellingDefinition][Variant spelling]] that represents an unintentional alternate [[#NameStringDefinition][Name-string]] (e. g., typographical error). -- [[LCLapsusDiscussion][Discussion]]
d100 1
a100 1
	<b>Reference</b>: Any form of DOCUMENTED date-stamped instance of one or more Authors (Agents).  This is broadly defined to include forms of documentation outside the context of [[#PublicationDefinition][Publications]]. "Documented" means that at least one physical (paper) or "permanent" electronic representation/facsimilie of information presented by Agent-Authors at a specific date/time is archived somewhere. Besides [[#PublicationDefinition][Publications]], these can include things like written personal communication (or archived representation of verbal personal communication), specimen labels, field notebooks, etc., etc. -- [[LCReferenceDiscussion][Discussion]]
d103 1
a103 1
	<b>Documentation</b>: Synonym of the [[#ReferenceDefinition][Reference]] with less ambiguity; the word 'reference' is also used as relationship, just like the word 'name' can be used either name-string or name-object-relationship. -- Discussion on [[LCReferenceDiscussion][Reference]] and [[LCPublicationDiscussion][Publication]]
d106 1
a106 1
	<b>Publication</b>: A special subset of [[#ReferenceDefinition][References]] that have been "published" in some way (perhaps best to define "publication" in accordance with ICZN/ICBN rules governing publications????) -- [[LCPublicationDiscussion][Discussion]]
d109 1
a109 1
	<b>Unpublished&nbsp;Documentation</b>: Permanently documented information (e.g. on paper, in digital format) that has not been published to a wider audience. This includes letters, laboratory or field books. It does not include forms of information attribution like "pers. comm.", which are not documented in any way. (Gregor) -- [[LCUnpublishedDocumentationDiscussion][Discussion]]
a113 1

@


1.30
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="FrankBungartz" date="1105552800" format="1.0" version="1.30"}%
d6 1
a6 1
	<b>Rank</b>: A specific, most-precise taxonomic rank (including intermediate ranks, such as "Subgenus", "Subspecies", etc.). See [[http://efgblade.cs.umb.edu/twiki/pub/UBIF/EnumerationTypes/UBIF-Docu-Enumerations.html#TaxonomicRankEnum][TaxonomicRankEum]]. -- [[TaxonomicRankDiscussion][Discussion]]
@


1.29
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="FrankBungartz" date="1105541808" format="1.0" version="1.29"}%
d36 6
a86 2
#BasalNameDefinition
	<b>Basal&nbsp;Name</b>&nbsp;or&nbsp;<b>basonym</b>:  A role name for a name in a nomenclatural relationship, including [[#BasionymDefinition][Basionym]] and [[#ReplacedSynonymDefinition][Replaced Synonym]]. -- [[LCProtonymDiscussion][Discussion]] <!-- [[#BasalNameDefinition][Basal Name]] -->
@


1.28
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="GregorHagedorn" date="1103211584" format="1.0" version="1.28"}%
d49 32
@


1.27
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="GregorHagedorn" date="1100875044" format="1.0" version="1.27"}%
d3 76
a78 75
These are some definitions proposed for use in further discussion.  Note that the word "name" is not on this list without some sort of qualification. We should all try to avoid using the word "name" without an explicit context. All definitions assume the scope of nomenclature defined for <nop>LinneanCore's domain, which is *tentatively* the Code-governed scientific names, plus possibly Trade Names, plus possibly some non-code-governed extensions of code-governed names [races, etc.], plus Linnean-type names used above the rank of Family (not technically governed by the Codes of Nomenclature -- at least not ICZN/ICBN.  Please feel free to comment/amend/etc., using the topics provided at the end of each definition. - 30 Oct 2004

#RankDefinition
	<b>Rank</b>: A specific, most-precise taxonomic rank (including intermediate ranks, such as "Subgenus", "Subspecies", etc.). See [[http://efgblade.cs.umb.edu/twiki/pub/UBIF/EnumerationTypes/UBIF-Docu-Enumerations.html#TaxonomicRankEnum][TaxonomicRankEum]]. -- [[TaxonomicRankDiscussion][Discussion]]

#RankGroupDefinition
	<b>Rank-group</b>: The "full" ranking groups. Within the context of Codes of nomenclature, these include only "Family-group", "Genus-group", and "Species-group".  However, we will also need to deal with "Order-group", "Class-group", "Phylum-group", and "Kingdom-group" entities as well. Although "Phylum-group" is Zoo-centric, "Division" is used for different [[#RankDefinition][ranks]] by different disciplines (even different sub-disciplines within Zoology), and "Phylum" is only used for one [[#RankDefinition][ranks]]. Therefore, it makes more sense to use "Phylum-group", "Phylum", "Subphylum", etc. -- and assume that these are all precisely synonymous with the botanical "Division" equivalencies. -- [[LCRankGroupDiscussion][Discussion]]

#NameDefinition
	<b>Name</b>: A relationship between a name-literal (and hence name-string) and a named-object.  It is recommeded to avoid this word as possible, but sometime inevitable.

#NameLiteralDefinition
	<b>Name-literal</b>: A literal word (or words) designating at least one object.  A single name-literal may designate multiple objects (homonymy) and multiple name-literals may designate single object (synonymy).  A name-literal is an abstraction of a set of [[#NameUsageDefinition][name-usages]].  A [[#NameStringDefinition][name-string]] is an electronic representation of a name-literal.  A name-literal may have [[#VariantSpellingDefinition][variant spellings]]; each variant is represented by a [[#NameStringDefinition][name-string]]. -- [[LCNameLiteralDiscussion][Discussion]]

#NameStringDefinition
	<b>Name-string</b>:  The Unicode string equivalent of [[#NameLiteralDefinition][name-literal]] printed on paper or represented in an electronic document to indicate a scientific name within the scope of <nop>LinneanCore's domain. It does *not* include authorship, but does include markup such as parentheses around infrageneric/supraspecific [[#NameUnitDefinition][Name-units]], and infraspecific rank terms (e.g., subsp., var., f. etc.). -- [[LCNameStringDiscussion][Discussion]]

#NameStringWithAuthorshipDefinition
	<b>Name-string&nbsp;with&nbsp;authorship</b>: A [[#NameStringDefinition][Name-string]] that includes the Code-appropriate authorships embedded within the [[#NameStringDefinition][name-string]]. -- [[LCNameStringDiscussionWithAuthorship][Discussion]]

#NameUnitDefinition
	<b>Name-unit</b>: A portion of a multi-part [[#NameStringDefinition][name-string]] that constitutes one discrete [[#RankDefinition][Rank]]. There do not appear to be any cases where a single name-unit would contain a space (" "), but it may include a hyphen ("-") or other characters outside the standard letters.  It is a token composing name-string, technically. -- [[LCNameUnitDiscussion][Discussion]]

#NameUsageDefinition
	<b>Name-usage</b>: The appearance of a [[#NameStringDefinition][Name-string]] within a [[#ReferenceDefinition][Reference]]. -- [[LCNameUsageDiscussion][Discussion]]

---

(Here some preliminary attempt by Gregor to clarify the Protonym/Basionym confusion, therefore for the moment not alphabetical:)

#BasionymDefinition
	<b>Basionym</b>: A role a name can have in relation to another name which is explicitly based upon the basionym name. Specifically, in genus or rank changing recombinations ("comb. nov.", "stat. nov.") the new name is based on a basionym name. The basionym of a name is always a [[#ProtonymDefinition][Protonym]] (= [[#OriginalNameDefinition][Original Name]] or [[#ReplacementNameDefinition][Replacement Name]]). The role of the basionym is very similar to the role of the [[#ReplacedSynonymDefinition][Replaced Synonym]] in the case of "nom. nov.". [[LCProtonymDiscussion][Discussion]] <!-- [[#BasionymDefinition][Basionym]] -->

#ReplacedSynonymDefinition
	<b>Replaced&nbsp;Synonym</b>: A role a name can have in relation to another name which is explicitly based upon the replaced synonym name. For example, if genus or rank changing recombinations would result in the creation of homonyms, a new epithet name has to be introduced to replace the previous epithet of the "Replaced Synonym". The replaced&nbsp;synonym of a name is always a [[#ProtonymDefinition][Protonym]] (= [[#OriginalNameDefinition][Original Name]] or [[#ReplacementNameDefinition][Replacement Name]]). This role is very close to a [[#BasionymDefinition][Basionym]], but ICBN (33.3) avoids the term basionym and uses this term instead. [[LCProtonymDiscussion][Discussion]] <!-- [[#ReplacedSynonymDefinition][Replaced Synonym]] -->

#ReplacementNameDefinition
	<b>Replacement&nbsp;Name</b>: A new name that replaces an existing name (= [[#ReplacedSynonymDefinition][Replaced Synonym]]). [[LCProtonymDiscussion][Discussion]] <!-- [[#ReplacementNameDefinition][Replacement Name]] -->


#OriginalNameDefinition
	<b>Original&nbsp;Name</b>: A name that introduces a new epithet and originally designates a type specimen (or other typification, including iconotype etc.). Multiple original names may accidentially based on the same type specimen. However, cases where a name is explicitly based to an older name (comb. nov,, stat. nov., nom. nov.) should not be considered original names. -- [[LCProtonymDiscussion][Discussion]] <!-- [[#OriginalNameDefinition][Original Name]] -->

#ProtonymDefinition
	<b>Protonym</b>: A name that introduced a new epithet the first time. This is the case in [[#OriginalNameDefinition][Original Names]] (not based on previously published nomenclatural names) and in the case of [[#ReplacementNameDefinition][Replacement Names]] (= "nom. nov.", = avowed substitute). -- [[LCProtonymDiscussion][Discussion]] <!-- [[#ProtonymDefinition][Protonym]] -->

#BasalNameDefinition
	<b>Basal&nbsp;Name</b>&nbsp;or&nbsp;<b>basonym</b>:  A role name for a name in a nomenclatural relationship, including [[#BasionymDefinition][Basionym]] and [[#ReplacedSynonymDefinition][Replaced Synonym]]. -- [[LCProtonymDiscussion][Discussion]] <!-- [[#BasalNameDefinition][Basal Name]] -->

#NewCombinationDefinition
	<b>New&nbsp;combination</b>: A re-use of a previously-existing [[#ProtonymDefinition][Protonym]] (= [[#OriginalNameDefinition][Original Name]] or [[#ReplacementNameDefinition][Replacement Names]]) in a different nomenclatural context.  In the botany world these are thought of as discrete "names", separate from their [[#ProtonymDefinition][protonyms]]; but in Zoology they are usually thought of as merely different contextual usages of a pre-existing "name" ([[#ProtonymDefinition][protonym]]).  Although ICZN does not have any rules to determine which "revised contextual usages" of pre-existing [[#ProtonymDefinition][protonyms]] constitute an "official" New Combination, in most cases it will be more or less unambiguously determinable who first placed a pre-existing species epithet into a different nomenclatural context. In any case, New combinations ONLY in the context of a particular kind of usage that represents a subsequent use of a pre-existing [[#ProtonymDefinition][protonym]] in a novel nomenclatural context (e.g., the first placement of an existing species epithet into a different genus than the epithet was originally described in (i.e., the nomenclatural context of it's [[#ProtonymDefinition][Protonym]]). -- [[LCNewCombinationDiscussion][Discussion]]

---

#VariantSpellingDefinition
	<b>Variant&nbsp;spelling</b>: This term refers to variant spellings (i.e., slightly different [[#LCNameStringDiscussion][Name-strings]]) used for what is otherwise a pre-existing [[#ProtonymDefinition][Protonym]] or [[#NewCombinationDefinition][New Combination]].  These include intentional variations (e.g., alternate gender forms of Species-group epithets), as well as unintentional variations (i.e., [[#LapsusDefinition][Lapsus]]). Variant spellings exist ONLY in the context of a [[#NameUsageDefinition][Name-usage]]. -- [[LCVariantSpellingDiscussion][Discussion]]

#LapsusDefinition
	<b>Lapsus</b>: A particular kind of [[#VariantSpellingDefinition][Variant spelling]] that represents an unintentional alternate [[#NameStringDefinition][Name-string]] (e. g., typographical error). -- [[LCLapsusDiscussion][Discussion]]
 
#ReferenceDefinition
	<b>Reference</b>: Any form of DOCUMENTED date-stamped instance of one or more Authors (Agents).  This is broadly defined to include forms of documentation outside the context of [[#PublicationDefinition][Publications]]. "Documented" means that at least one physical (paper) or "permanent" electronic representation/facsimilie of information presented by Agent-Authors at a specific date/time is archived somewhere. Besides [[#PublicationDefinition][Publications]], these can include things like written personal communication (or archived representation of verbal personal communication), specimen labels, field notebooks, etc., etc. -- [[LCReferenceDiscussion][Discussion]]

#Documentation
	<b>Documentation</b>: Synonym of the [[#ReferenceDefinition][Reference]] with less ambiguity; the word 'reference' is also used as relationship, just like the word 'name' can be used either name-string or name-object-relationship. -- Discussion on [[LCReferenceDiscussion][Reference]] and [[LCPublicationDiscussion][Publication]]

#PublicationDefinition
	<b>Publication</b>: A special subset of [[#ReferenceDefinition][References]] that have been "published" in some way (perhaps best to define "publication" in accordance with ICZN/ICBN rules governing publications????) -- [[LCPublicationDiscussion][Discussion]]

#UnpublishedDocumentationDefinition
	<b>Unpublished&nbsp;Documentation</b>: Permanently documented information (e.g. on paper, in digital format) that has not been published to a wider audience. This includes letters, laboratory or field books. It does not include forms of information attribution like "pers. comm.", which are not documented in any way. (Gregor) -- [[LCUnpublishedDocumentationDiscussion][Discussion]]

---

(see also LinneanCoreSomePrivateConceptDefinitions)
@


1.26
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="GregorHagedorn" date="1100627328" format="1.0" version="1.26"}%
a68 1

d76 2
a77 1
---
@


1.25
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="GregorHagedorn" date="1100601145" format="1.0" version="1.25"}%
d67 1
a67 1
	<del>Name-source</del><b>Documentation</b>: Synonym of the [[#ReferenceDefinition][Reference]] with less ambiguity; the word 'reference' is also used as relationship, just like the word 'name' can be used either name-string or name-object-relationship. -- Discussion on [[LCReferenceDiscussion][Reference]] and [[LCPublicationDiscussion][Publication]]
d77 1
a77 13

Also by Gregor another attempt to define the different kind of taxon concepts used in biological taxonomy

-- unfinished - will finish later need to save now! --

#TypeConceptDefinition
	<b>Type&nbsp;Concept</b>: Also called nomenclatural "name-object". This defines only a single point in nature and time, the type specimen. This kind of concept is the basis for the rules of nomenclature in bacteriology, botany, and zoology. It has little value when attempting to identify unknown organisms, but it serves as a fixing point to connect the circumscription concepts that are usually -- [[LCConceptConceptsDiscussion][Discussion]]

#CircumscriptionConceptDefinition
	<b>Circumscription&nbsp;Concept</b>: A concept defining an extension of observations in nature. The only concept used in identification. This kind of taxon concept is often loosely referred to as a "taxon concept" as opposed to a name -- [[LCConceptConceptsDiscussion][Discussion]]

#HierarchyConceptDefinition
	<b>Type&nbsp;Concept</b>: Perhaps call this enumerated concept instead? A tree of concepts based on other concepts. This has no value for identification. -- [[LCConceptConceptsDiscussion][Discussion]]
@


1.24
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="NozomiJamesYtow" date="1100277371" format="1.0" version="1.24"}%
a65 1
#NameSource
d70 1
a70 1
#PublicationDefinition	  
d77 13
@


1.23
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="GregorHagedorn" date="1100012861" format="1.0" version="1.23"}%
d11 3
d24 1
a24 1
	<b>Name-unit</b>: A portion of a multi-part [[#NameStringDefinition][name-string]] that constitutes one discrete [[#RankDefinition][Rank]]. There do not appear to be any cases where a single name-unit would contain a space (" "), but it may include a hyphen ("-") or other characters outside the standard letters. -- [[LCNameUnitDiscussion][Discussion]]
@


1.22
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="NozomiJamesYtow" date="1099816761" format="1.0" version="1.22"}%
d31 1
a31 1
	<b>Basionym</b>: A role a name can have in relation to another name which is explicitly based upon the basionym name. Specifically, in genus or rank changing recombinations ("comb. nov.", "stat. nov.") the new name is based on a basionym name. The role of the basionym is very similar to the role of the [[#ReplacedSynonymDefinition][Replaced Synonym]] in the case of "nom. nov.". [[LCProtonymDiscussion][Discussion]] <!-- [[#BasionymDefinition][Basionym]] -->
d34 5
a38 1
	<b>Replaced&nbsp;Synonym</b>: A role a name can have in relation to another name which is explicitly based upon the replaced synonym name. Specifically, in genus or rank changing recombinations that would result in the creation of homonyms, a new epithet name has to be introduced to replace the previous epithet of the "Replaced Synonym". This role is very close to a [[#BasionymDefinition][Basionym]], but ICBN (33.3) avoids the term basionym and uses this term instead. [[LCProtonymDiscussion][Discussion]] <!-- [[#ReplacedSynonymDefinition][Replaced Synonym]] -->
d44 1
a44 1
	<b>Protonym</b>: A name that introduced a new epithet the first time. This is the case in original names (not based on previously published nomenclatural names) and in the case of replacement names (= "nom. nov.", = avowed substitute). -- [[LCProtonymDiscussion][Discussion]] <!-- [[#ProtonymDefinition][Protonym]] -->
d50 1
a50 1
	<b>New&nbsp;combination</b>: A re-use of a previously-existing name Original name (Gregor: I removed protonym here!) in a different nomenclatural context.  In the botany world these are thought of as discrete "names", separate from their [[#ProtonymDefinition][protonyms]]; but in Zoology they are usually thought of as merely different contextual usages of a pre-existing "name" ([[#ProtonymDefinition][protonym]]).  Although ICZN does not have any rules to determine which "revised contextual usages" of pre-existing [[#ProtonymDefinition][protonyms]] constitute an "official" New Combination, in most cases it will be more or less unambiguously determinable who first placed a pre-existing species epithet into a different nomenclatural context. In any case, New combinations ONLY in the context of a particular kind of usage that represents a subsequent use of a pre-existing [[#ProtonymDefinition][protonym]] in a novel nomenclatural context (e.g., the first placement of an existing species epithet into a different genus than the epithet was originally described in (i.e., the nomenclatural context of it's [[#ProtonymDefinition][Protonym]]). -- [[LCNewCombinationDiscussion][Discussion]]
d59 1
a59 1

@


1.21
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="NozomiJamesYtow" date="1099697580" format="1.0" version="1.21"}%
d60 2
a61 1
	<b>Name-source</b>: Synonym of the [[#ReferenceDefinition][Reference]] with less ambiguity; the word 'reference' is also used as relationship, just like the word 'name' can be used either name-string or name-object-relationship. -- Discussion on [[LCReferenceDiscussion][Reference]] and [[LCPublicationDiscussion][Publication]]
@


1.20
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="GregorHagedorn" date="1099577340" format="1.0" version="1.20"}%
d43 1
a43 1
	<b>Basal&nbsp;Name</b>: A role name for a name in a nomenclatural relationship, including [[#BasionymDefinition][Basionym]] and [[#ReplacedSynonymDefinition][Replaced Synonym]]. -- [[LCProtonymDiscussion][Discussion]] <!-- [[#BasalNameDefinition][Basal Name]] -->
@


1.19
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="GregorHagedorn" date="1099567200" format="1.0" version="1.19"}%
d30 2
a31 2
#BasionymDefinition <!-- [[#BasionymDefinition][Basionym]] -->
	<b>Basionym</b>: A role a name can have in relation to another name which is explicitly based upon the basionym name. Specifically, in genus or rank changing recombinations ("comb. nov.", "stat. nov.") the new name is based on a basionym name. The role of the basionym is very similar to the role of the [[#ReplacedSynonymDefinition][Replaced Synonym]] in the case of "nom. nov.". [[LCProtonymDiscussion][Discussion]]
d33 2
a34 2
#ReplacedSynonymDefinition <!-- [[#ReplacedSynonymDefinition][Replaced Synonym]] -->
	<b>Replaced Synonym</b>: A role a name can have in relation to another name which is explicitly based upon the replaced synonym name. Specifically, in genus or rank changing recombinations that would result in the creation of homonyms, a new epithet name has to be introduced to replace the previous epithet of the "Replaced Synonym". This role is very close to a [[#BasionymDefinition][Basionym]], but ICBN (33.3) avoids the term basionym and uses this term instead. [[LCProtonymDiscussion][Discussion]]
d37 1
a37 1
	<b>Original Name</b>: A name that introduces a new epithet and originally designates a type specimen (or other typification, including iconotype etc.). Multiple original names may accidentially based on the same type specimen. However, cases where a name is explicitly based to an older name (comb. nov,, stat. nov., nom. nov.) should not be considered original names. -- [[LCProtonymDiscussion][Discussion]]
d40 4
a43 1
	<b>Protonym</b>: A name that introduced a new epithet the first time. This is the case in original names (not based on previously published nomenclatural names) and in the case of replacement names (= "nom. nov.", = avowed substitute). -- [[LCProtonymDiscussion][Discussion]]
@


1.18
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="GregorHagedorn" date="1099562674" format="1.0" version="1.18"}%
d26 13
d40 1
a40 1
	<b>Protonym</b>: Effectively identical to a basionym (although we need to confirm that in cases of a replacement name or nom. nov., there are two protonyms, but only one basionym.  Protonyms and basionyms probably do not need to be discussed separately, as long as we acknowledge that the schema will keep track of special cases of repacement name and nom. nov. A protonym exists ONLY in the context of a particular kind of [[#NameUsageDefinition][Name-usage]] that represents a code-compliant original description of a new basionym (i.e., new terminal epithet). -- [[LCProtonymDiscussion][Discussion]]
d43 3
a45 1
	<b>New&nbsp;combination</b>: A re-use of a previously-existing [[#ProtonymDefinition][protonym]] in a different nomenclatural context.  In the botany world these are thought of as discrete "names", separate from their [[#ProtonymDefinition][protonyms]]; but in Zoology they are usually thought of as merely different contextual usages of a pre-existing "name" ([[#ProtonymDefinition][protonym]]).  Although ICZN does not have any rules to determine which "revised contextual usages" of pre-existing [[#ProtonymDefinition][protonyms]] constitute an "official" New Combination, in most cases it will be more or less unambiguously determinable who first placed a pre-existing species epithet into a different nomenclatural context. In any case, New combinations ONLY in the context of a particular kind of usage that represents a subsequent use of a pre-existing [[#ProtonymDefinition][protonym]] in a novel nomenclatural context (e.g., the first placement of an existing species epithet into a different genus than the epithet was originally described in (i.e., the nomenclatural context of it's [[#ProtonymDefinition][Protonym]]). -- [[LCNewCombinationDiscussion][Discussion]]
@


1.17
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="NozomiJamesYtow" date="1099425600" format="1.0" version="1.17"}%
d15 1
a15 1
	<b>Name-string</b>:  The Unicode string equivalent of [[#NameLiteralDefinition][name-literal]] printed on paper or represented in an electronic document to indicate a scientific name within the scope of <nop>LinneanCore's domain. It does *not* include authorship, but does include markup such as parentheses around infrageneric/supraspecific [[#NameUnitDefinition][Name-units]], and infraspecific prefixes (e.g., subsp., var., f. etc.). -- [[LCNameStringDiscussion][Discussion]]
@


1.16
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="GregorHagedorn" date="1099310940" format="1.0" version="1.16"}%
d41 4
@


1.15
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="NozomiJamesYtow" date="1099307368" format="1.0" version="1.15"}%
d3 1
a3 1
These are some definitions proposed for use in further discussion.  Note that the word "name" is not on this list without some sort of qualification. We should all try to avoid using the word "name" without an explicit context. All definitions assume the scope of nomenclature defined for <nop>LinneanCore's domain, which is *tentatively* the Code-governed scientific names, plus possibly Trade Names, plus possibly some non-code-governed extensions of code-governed names [races, etc.], plus Linnean-type names used above the rank of Family (not technically governed by the Codes of Nomenclature -- at least not ICZN/ICBN.  Please feel free to comment/amend/etc., using the topics provided at the defined term. - 30 Oct 2004
d6 1
a6 1
	[[http://efgblade.cs.umb.edu/twiki/pub/UBIF/EnumerationTypes/UBIF-Docu-Enumerations.html#TaxonomicRankEnum][<b>Rank</b>]]: A specific, most-precise taxonomic rank (including intermediate ranks, such as "Subgenus", "Subspecies", etc.).  See 
d9 1
a9 1
	[[LCRankGroupDiscussion][<b>Rank-group</b>]]: The "full" ranking groups. Within the context of Codes of nomenclature, these include only "Family-group", "Genus-group", and "Species-group".  However, we will also need to deal with "Order-group", "Class-group", "Phylum-group", and "Kingdom-group" entities as well. Although "Phylum-group" is Zoo-centric, "Division" is used for different [[#RankDefinition][ranks]] by different disciplines (even different sub-disciplines within Zoology), and "Phylum" is only used for one [[#RankDefinition][ranks]]. Therefore, it makes more sense to use "Phylum-group", "Phylum", "Subphylum", etc. -- and assume that these are all precisely synonymous with the botanical "Division" equivalencies.
d12 1
a12 1
	[[LCNameLiteralDiscussion][<b>Name-literal</b>]]: A literal word (or words) designating at least one object.  A single name-literal may designate multiple objects (homonymy) and multiple name-literals may designate single object (synonymy).  A name-literal is an abstraction of a set of [[#NameUsageDefinition][name-usages]].  A [[#NameStringDefinition][name-string]] is an electronic representation of a name-literal.  A name-literal may have [[#VariantSpellingDefinition][variant spellings]]; each variant is represented by a [[#NameStringDefinition][name-string]].
d15 1
a15 1
	[[LCNameStringDiscussion][<b>Name-string</b>]]:  The Unicode string equivalent of [[#NameLiteralDefinition][name-literal]] printed on paper or represented in an electronic document to indicate a scientific name within the scope of <nop>LinneanCore's domain. It does *not* include authorship, but does include markup such as parentheses around infrageneric/supraspecific [[#NameUnitDefinition][Name-units]], and infraspecific prefixes (e.g., subsp., var., f. etc.).
d18 1
a18 1
	[[LCNameStringDiscussionWithAuthorship][<b>Name-string&nbsp;with&nbsp;authorship</b>]]: A [[#NameStringDefinition][Name-string]] that includes the Code-appropriate authorships embedded within the [[#NameStringDefinition][name-string]].
d21 1
a21 1
	[[LCNameUnitDiscussion][<b>Name-unit</b>]]: A portion of a multi-part [[#NameStringDefinition][name-string]] that constitutes one discrete [[#RankDefinition][Rank]]. There do not appear to be any cases where a single name-unit would contain a space (" "), but it may include a hyphen ("-") or other characters outside the standard letters.
d24 1
a24 1
	[[LCNameUsageDiscussion][<b>Name-usage</b>]]: The appearance of a [[#NameStringDefinition][Name-string]] within a [[#ReferenceDefinition][Reference]]. 
d27 1
a27 1
	[[LCProtonymDiscussion][<b>Protonym</b>]]: Effectively identical to a basionym (although we need to confirm that in cases of a replacement name or nom. nov., there are two protonyms, but only one basionym.  Protonyms and basionyms probably do not need to be discussed separately, as long as we acknowledge that the schema will keep track of special cases of repacement name and nom. nov. A protonym exists ONLY in the context of a particular kind of [[#NameUsageDefinition][Name-usage]] that represents a code-compliant original description of a new basionym (i.e., new terminal epithet).
d30 1
a30 1
	[[LCNewCombinationDiscussion][<b>New&nbsp;combination</b>]]: A re-use of a previously-existing [[#ProtonymDefinition][protonym]] in a different nomenclatural context.  In the botany world these are thought of as discrete "names", separate from their [[#ProtonymDefinition][protonyms]]; but in Zoology they are usually thought of as merely different contextual usages of a pre-existing "name" ([[#ProtonymDefinition][protonym]]).  Although ICZN does not have any rules to determine which "revised contextual usages" of pre-existing [[#ProtonymDefinition][protonyms]] constitute an "official" New Combination, in most cases it will be more or less unambiguously determinable who first placed a pre-existing species epithet into a different nomenclatural context. In any case, New combinations ONLY in the context of a particular kind of usage that represents a subsequent use of a pre-existing [[#ProtonymDefinition][protonym]] in a novel nomenclatural context (e.g., the first placement of an existing species epithet into a different genus than the epithet was originally described in (i.e., the nomenclatural context of it's [[#ProtonymDefinition][Protonym]]).
d33 1
a33 1
	[[LCVariantSpellingDiscussion][<b>Variant&nbsp;spelling</b>]]: This term refers to variant spellings (i.e., slightly different [[#LCNameStringDiscussion][Name-strings]]) used for what is otherwise a pre-existing [[#ProtonymDefinition][Protonym]] or [[#NewCombinationDefinition][New Combination]].  These include intentional variations (e.g., alternate gender forms of Species-group epithets), as well as unintentional variations (i.e., [[#LapsusDefinition][Lapsus]]). Variant spellings exist ONLY in the context of a [[#NameUsageDefinition][Name-usage]]. 
d36 1
a36 1
	[[LCLapsusDiscussion][<b>Lapsus</b>]] A particular kind of [[#VariantSpellingDefinition][Variant spelling]] that represents an unintentional alternate [[#NameStringDefinition][Name-string]] (e. g., typographical error).
d39 1
a39 1
	[[LCReferenceDiscussion][<b>Reference</b>]]: Any form of DOCUMENTED date-stamped instance of one or more Authors (Agents).  This is broadly defined to include forms of documentation outside the context of [[#PublicationDefinition][Publications]]. "Documented" means that at least one physical (paper) or "permanent" electronic representation/facsimilie of information presented by Agent-Authors at a specific date/time is archived somewhere. Besides [[#PublicationDefinition][Publications]], these can include things like written personal communication (or archived representation of verbal personal communication), specimen labels, field notebooks, etc., etc.
d42 1
a42 1
	[[LCPublicationDiscussion][<b>Publication</b>]]: A special subset of [[#ReferenceDefinition][References]] that have been "published" in some way (perhaps best to define "publication" in accordance with ICZN/ICBN rules governing publications????) 
d45 1
a45 1
	[[LCUnpublishedDocumentationDiscussion][<b>Unpublished&nbsp;Documentation</b>]]: Permanently documented information (e.g. on paper, in digital format) that has not been published to a wider audience. This includes letters, laboratory or field books. It does not include forms of information attribution like "pers. comm.", which are not documented in any way. -- Gregor
@


1.14
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="GregorHagedorn" date="1099300647" format="1.0" version="1.14"}%
d3 1
a3 1
These are some definitions proposed for use in further discussion.  Note that the word "name" is not on this list without some sort of qualification. We should all try to avoid using the word "name" without an explicit context. All definitions assume the scope of nomenclature defined for <nop>LinneanCore's domain, which is *tentatively* the Code-governed scientific names, plus possibly Trade Names, plus possibly some non-code-governed extensions of code-governed names [races, etc.], plus Linnean-type names used above the rank of Family (not technically governed by the Codes of Nomenclature -- at least not ICZN/ICBN.  Please feel free to comment/amend/etc., using the topics provided at the end of each definition. - 30 Oct 2004
d6 1
a6 1
	<b>Rank</b>: A specific, most-precise taxonomic rank (including intermediate ranks, such as "Subgenus", "Subspecies", etc.).  See [[http://efgblade.cs.umb.edu/twiki/pub/UBIF/EnumerationTypes/UBIF-Docu-Enumerations.html#TaxonomicRankEnum][TaxonomicRankEum]]. [Please discuss on TaxonomicRankDiscussion!]
d9 1
a9 1
	<b>Rank-group</b>: The "full" ranking groups. Within the context of Codes of nomenclature, these include only "Family-group", "Genus-group", and "Species-group".  However, we will also need to deal with "Order-group", "Class-group", "Phylum-group", and "Kingdom-group" entities as well. Although "Phylum-group" is Zoo-centric, "Division" is used for different [[#RankDefinition][ranks]] by different disciplines (even different sub-disciplines within Zoology), and "Phylum" is only used for one [[#RankDefinition][ranks]]. Therefore, it makes more sense to use "Phylum-group", "Phylum", "Subphylum", etc. -- and assume that these are all precisely synonymous with the botanical "Division" equivalencies. [Please discuss on [[LCRankGroupDiscussion][Rank-group discussion]]]
d12 1
a12 1
	<b>Name-literal</b>: A literal word (or words) designating at least one object.  A single name-literal may designate multiple objects (homonymy) and multiple name-literals may designate single object (synonymy).  A name-literal is an abstraction of a set of [[#NameUsageDefinition][name-usages]].  A [[#NameStringDefinition][name-string]] is an electronic representation of a name-literal.  A name-literal may have [[#VariantSpellingDefinition][variant spellings]]; each variant is represented by a [[#NameStringDefinition][name-string]]. [Please discuss on [[LCNameLiteralDiscussion][Name-literal discussion]]]
d15 1
a15 1
	<b>Name-string</b>:  The Unicode string equivalent of [[#NameLiteralDefinition][name-literal]] printed on paper or represented in an electronic document to indicate a scientific name within the scope of <nop>LinneanCore's domain. It does *not* include authorship, but does include markup such as parentheses around infrageneric/supraspecific [[#NameUnitDefinition][Name-units]], and infraspecific prefixes (e.g., subsp., var., f. etc.). [Please discuss on [[LCNameStringDiscussion][Name-string discussion]]]
d18 1
a18 1
	<b>Name-string&nbsp;with&nbsp;authorship</b>: A [[#NameStringDefinition][Name-string]] that includes the Code-appropriate authorships embedded within the [[#NameStringDefinition][name-string]]. [Please discuss on [[LCNameStringDiscussionWithAuthorship][Name-string with authorship discussion]]]
d21 1
a21 1
	<b>Name-unit</b>: A portion of a multi-part [[#NameStringDefinition][name-string]] that constitutes one discrete [[#RankDefinition][Rank]]. There do not appear to be any cases where a single name-unit would contain a space (" "), but it may include a hyphen ("-") or other characters outside the standard letters. [Please discuss on [[LCNameUnitDiscussion][Name-unit discussion]]]
d24 1
a24 1
	<b>Name-usage</b>: The appearance of a [[#NameStringDefinition][Name-string]] within a [[#ReferenceDefinition][Reference]]. [Please discuss on [[LCNameUsageDiscussion][Name-usage discussion]]]
d27 1
a27 1
	<b>Protonym</b>: Effectively identical to a basionym (although we need to confirm that in cases of a replacement name or nom. nov., there are two protonyms, but only one basionym.  Protonyms and basionyms probably do not need to be discussed separately, as long as we acknowledge that the schema will keep track of special cases of repacement name and nom. nov. A protonym exists ONLY in the context of a particular kind of [[#NameUsageDefinition][Name-usage]] that represents a code-compliant original description of a new basionym (i.e., new terminal epithet). [Please discuss on [[LCProtonymDiscussion][Protonym discussion]]]
d30 1
a30 1
	<b>New&nbsp;combination</b>: A re-use of a previously-existing [[#ProtonymDefinition][protonym]] in a different nomenclatural context.  In the botany world these are thought of as discrete "names", separate from their [[#ProtonymDefinition][protonyms]]; but in Zoology they are usually thought of as merely different contextual usages of a pre-existing "name" ([[#ProtonymDefinition][protonym]]).  Although ICZN does not have any rules to determine which "revised contextual usages" of pre-existing [[#ProtonymDefinition][protonyms]] constitute an "official" New Combination, in most cases it will be more or less unambiguously determinable who first placed a pre-existing species epithet into a different nomenclatural context. In any case, New combinations ONLY in the context of a particular kind of usage that represents a subsequent use of a pre-existing [[#ProtonymDefinition][protonym]] in a novel nomenclatural context (e.g., the first placement of an existing species epithet into a different genus than the epithet was originally described in (i.e., the nomenclatural context of it's [[#ProtonymDefinition][Protonym]]). [Please discuss on [[LCNewCombinationDiscussion][New Combination discussion]]]
d33 1
a33 1
	<b>Variant&nbsp;spelling</b>: This term refers to variant spellings (i.e., slightly different [[#LCNameStringDiscussion][Name-strings]]) used for what is otherwise a pre-existing [[#ProtonymDefinition][Protonym]] or [[#NewCombinationDefinition][New Combination]].  These include intentional variations (e.g., alternate gender forms of Species-group epithets), as well as unintentional variations (i.e., [[#LapsusDefinition][Lapsus]]). Variant spellings exist ONLY in the context of a [[#NameUsageDefinition][Name-usage]]. [Please discuss on [[VariantSpelling][Variant Spelling discussion]]]
d36 1
a36 1
	<b>Lapsus</b>: A particular kind of [[#VariantSpellingDefinition][Variant spelling]] that represents an unintentional alternate [[#NameStringDefinition][Name-string]] (e. g., typographical error). [Please discuss on [[LCLapsusDiscussion][Lapsus discussion]]]
d39 1
a39 1
	<b>Reference</b>: Any form of DOCUMENTED date-stamped instance of one or more Authors (Agents).  This is broadly defined to include forms of documentation outside the context of [[#PublicationDefinition][Publications]]. "Documented" means that at least one physical (paper) or "permanent" electronic representation/facsimilie of information presented by Agent-Authors at a specific date/time is archived somewhere. Besides [[#PublicationDefinition][Publications]], these can include things like written personal communication (or archived representation of verbal personal communication), specimen labels, field notebooks, etc., etc. [Please discuss on [[LCReferenceDiscussion][Reference discussion]]]
d42 1
a42 1
	<b>Publication</b>: A special subset of [[#ReferenceDefinition][References]] that have been "published" in some way (perhaps best to define "publication" in accordance with ICZN/ICBN rules governing publications????) [Please discuss on [[LCPublicationDiscussion][Publication discussion]]]
d45 1
a45 1
	<b>Unpublished&nbsp;Documentation</b>: Permanently documented information (e.g. on paper, in digital format) that has not been published to a wider audience. This includes letters, laboratory or field books. It does not include forms of information attribution like "pers. comm.", which are not documented in any way. -- Gregor [Please discuss on [[LCUnpublishedDocumentationDiscussion][Unpublished Documentation discussion]]]
@


1.13
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="GregorHagedorn" date="1099252320" format="1.0" version="1.13"}%
d3 1
a3 1
These are some definitions proposed for use in further discussion.  Note that the word "name" is not on this list without some sort of qualification. We should all try to avoid using the word "name" without an explicit context. All definitions assume the scope of nomenclature defined for <nop>LinneanCore's domain, which is *tentatively* the Code-governed scientific names, plus possibly Trade Names, plus possibly some non-code-governed extensions of code-governed names [races, etc.], plus Linnean-type names used above the rank of Family (not technically governed by the Codes of Nomenclature -- at least not ICZN/ICBN.  Please feel free to comment/amend/etc. All comentary associated with the definitions are organized within a separate LinneanCoreDefinitionsDiscussion page. - 30 Oct 2004
@


1.12
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="GregorHagedorn" date="1099213380" format="1.0" version="1.12"}%
d6 1
a6 2
	<b>Rank</b>: A specific, most-precise taxonomic rank (including intermediate ranks, such as "Subgenus", "Subspecies", etc.).  See [[http://efgblade.cs.umb.edu/twiki/pub/UBIF/EnumerationTypes/UBIF-Docu-Enumerations.html#TaxonomicRankEnum][TaxonomicRankEum]].
		* [[Rank][Rank discussion]]
d8 14
a21 19
#LCRankGroupDiscussionDefinition
	<b>Rank-group</b>: The "full" ranking groups. Within the context of Codes of nomenclature, these include only "Family-group", "Genus-group", and "Species-group".  However, we will also need to deal with "Order-group", "Class-group", "Phylum-group", and "Kingdom-group" entities as well. Although "Phylum-group" is Zoo-centric, "Division" is used for different [[#RankDefinition][ranks]] by different disciplines (even different sub-disciplines within Zoology), and "Phylum" is only used for one [[#RankDefinition][ranks]]. Therefore, it makes more sense to use "Phylum-group", "Phylum", "Subphylum", etc. -- and assume that these are all precisely synonymous with the botanical "Division" equivalencies.
		* [[LCRankGroupDiscussion][Rank-group discussion]]

#LCNameLiteralDiscussionDefinition
	<b>Name-literal</b>: A literal word (or words) designating at least one object.  A single name-literal may designate multiple objects (homonymy) and multiple name-literals may designate single object (synonymy).  A name-literal is an abstraction of a set of [[#NameUsageDefinition][name-usages]].  A [[#LCNameStringDiscussionDefinition][name-string]] is an electronic representation of a name-literal.  A name-literal may have [[#VariantSpellingDefinition][variant spellings]]; each variant is represented by a [[#LCNameStringDiscussionDefinition][name-string]]. 
		* [[LCNameLiteralDiscussion][Name-literal discussion]]

#LCNameStringDiscussionDefinition
	<b>Name-string</b>:  The Unicode string equivalent of [[#LCNameLiteralDiscussionDefinition][name-literal]] printed on paper or represented in an electronic document to indicate a scientific name within the scope of <nop>LinneanCore's domain. It does *not* include authorship, but does include markup such as parentheses around infrageneric/supraspecific [[#LCNameUnitDiscussionDefinition][Name-units]], and infraspecific prefixes (e.g., subsp., var., f. etc.).
		* [[LCNameStringDiscussion][Name-string discussion]]

#LCNameStringDiscussionWithAuthorshipDefinition
	<b>Name-string&nbsp;with&nbsp;authorship</b>: A [[#LCNameStringDiscussionDefinition][Name-string]] that includes the Code-appropriate authorships embedded within the [[#LCNameStringDiscussionDefinition][name-string]].
		* [[LCNameStringDiscussionWithAuthorship][Name-string with authorship discussion]]

#LCNameUnitDiscussionDefinition
	<b>Name-unit</b>: A portion of a multi-part [[#LCNameStringDiscussionDefinition][name-string]] that constitutes one discrete [[#RankDefinition][Rank]]. There do not appear to be any cases where a single name-unit would contain a space (" "), but it may include a hyphen ("-") or other characters outside the standard letters.
		* [[LCNameUnitDiscussion][Name-unit discussion]]
d24 1
a24 2
	<b>Name-usage</b>: The appearance of a [[#LCNameStringDiscussionDefinition][Name-string]] within a [[#ReferenceDefinition][Reference]].
		* [[NameUsage][Name-usage discussion]]
d27 1
a27 2
	<b>Protonym</b>: Effectively identical to a basionym (although we need to confirm that in cases of a repacement name or nom. nov., there are two protonyms, but only one basionym.  Protonyms and basionyms probably do not need to be discussed separately, as long as we acknowledge that the schema will keep track of special cases of repacement name and nom. nov. A protonym exists ONLY in the context of a particular kind of [[#NameUsageDefinition][Name-usage]] that represents a code-compliant original description of a new basionym (i.e., new terminal epithet).
		* [[Protonym][Protonym discussion]]
d29 2
a30 3
#LCNewCombinationDiscussionDefinition
	<b>New&nbsp;combination</b>: A re-use of a previously-existing [[#ProtonymDefinition][protonym]] in a different nomenclatural context.  In the botany world these are thought of as discrete "names", separate from their [[#ProtonymDefinition][protonyms]]; but in Zoology they are usually thought of as merely different contextual usages of a pre-existing "name" ([[#ProtonymDefinition][protonym]]).  Although ICZN does not have any rules to determine which "revised contextual usages" of pre-existing [[#ProtonymDefinition][protonyms]] constitute an "official" New Combination, in most cases it will be more or less unambiguously determinable who first placed a pre-existing species epithet into a different nomenclatural context. In any case, New combinations ONLY in the context of a particular kind of usage that represents a subsequent use of a pre-existing [[#ProtonymDefinition][protonym]] in a novel nomenclatural context (e.g., the first placement of an existing species epithet into a different genus than the epithet was originally described in (i.e., the nomenclatural context of it's [[#ProtonymDefinition][Protonym]]).
		* [[LCNewCombinationDiscussion][New Combination discussion]]
d33 1
a33 2
	<b>Variant&nbsp;spelling</b>: This term refers to variant spellings (i.e., slightly different [[#LCNameStringDiscussion][Name-strings]]) used for what is otherwise a pre-existing [[#ProtonymDefinition][Protonym]] or [[#LCNewCombinationDiscussionDefinition][New Combination]].  These include intentional variations (e.g., alternate gender forms of Species-group epithets), as well as unintentional variations (i.e., [[#LapsusDefinition][Lapsus]]). Variant spellings exist ONLY in the context of a [[#NameUsageDefinition][Name-usage]].
		* [[VariantSpelling][Variant Spelling discussion]]
d36 1
a36 2
	<b>Lapsus</b>: A particular kind of [[#VariantSpellingDefinition][Variant spelling]] that represents an unintentional alternate [[#LCNameStringDiscussionDefinition][Name-string]] (e. g., typographical error).
		* [[Lapsus][Lapsus discussion]]
d39 1
a39 2
	<b>Reference</b>: Any form of DOCUMENTED date-stamped instance of one or more Authors (Agents).  This is broadly defined to include forms of documentation outside the context of [[#PublicationDefinition][Publications]]. "Documented" means that at least one physical (paper) or "permanent" electronic representation/facsimilie of information presented by Agent-Authors at a specific date/time is archived somewhere. Besides [[#PublicationDefinition][Publications]], these can include things like written personal communication (or archived representation of verbal personal communication), specimen labels, field notebooks, etc., etc.
		* [[Reference][Reference discussion]]
d42 1
a42 2
	<b>Publication</b>: A special subset of [[#ReferenceDefinition][References]] that have been "published" in some way (perhaps best to define "publication" in accordance with ICZN/ICBN rules governing publications????)
		* [[Publication][Publication discussion]]
d45 1
a45 2
	<b>Unpublished&nbsp;Documentation</b>: Permanently documented information (e.g. on paper, in digital format) that has not been published to a wider audience. This includes letters, laboratory or field books. It does not include forms of information attribution like "pers. comm.", which are not documented in any way. -- Gregor
		* [[UnpublishedDocumentationDiscussion][Unpublished Documentation discussion]]
d47 1
a47 2
---

@


1.11
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="RichardPyle" date="1099202460" format="1.0" version="1.11"}%
d3 1
a3 1
These are some definitions proposed for use in further discussion.  Note that the word "name" is not on this list without some sort of qualification. We should all try to avoid using the word "name" without an explicit context. All definitions assume the scope of nomenclature defined for <nop>LinneanCore's domain, which is *tentatively* the Code-governed scientific names, plus possibly Trade Names, plus possibly some non-code-governed extensions of code-governed names [races, etc.], plus Linnean-type names used above the rank of Family (not technically governed by the Codes of Nomenclature -- at least not ICZN/ICBN.  Please feel free to comment/ammend/etc. All comentary associated with the definitions are organized within a separate LinneanCoreDefinitionsDiscussion page. - 30 Oct 2004
d9 19
a27 19
#RankGroup
	<b>Rank-group</b>:  The "full" ranking groups. Within the context of Codes of nomenclature, these include only "Family-group", "Genus-group", and "Species-group".  However, we will also need to deal with "Order-group", "Class-group", "Phylum-group", and "Kingdom-group" entities as well. Although "Phylum-group" is Zoo-centric, "Division" is used for different [[#RankDefinition][ranks]] by different disciplines (even different sub-disciplines within Zoology), and "Phylum" is only used for one [[#RankDefinition][ranks]]. Therefore, it makes more sense to use "Phylum-group", "Phylum", "Subphylum", etc. -- and assume that these are all precisely synonymous with the botanical "Division" equivalencies.
		* [[RankGroup][Rank-group discussion]]

#NameLiteral
	<b>Name-literal</b>:  A literal word (or words) designating at least one object.  A single name-literal may designate multiple objects (homonymy) and multiple name-literals may designate single object (synonymy).  A name-literal is an abstraction of a set of [[#NameUsage][name-usages]].  A [[#NameString][name-string]] is an electronic representation of a name-literal.  A name-literal may have [[#VariantSpelling][variant spellings]]; each variant is represented by a [[#NameString][name-string]]. 
		* [[NameLiteral][Name-literal discussion]]

#NameString
	<b>Name-string</b>:  The Unicode string equivalent of [[#NameLiteral][name-literal]] printed on paper or represented in an electronic document to indicate a scientific name within the scope of <nop>LinneanCore's domain. It does *not* include authorship, but does include markup such as parentheses around infrageneric/supraspecific [[#NameUnit][Name-units]], and infraspecific prefixes (e.g., subsp., var., f. etc.).
		* [[NameString][Name-string discussion]]

#NameStringWithAuthorship		
	<b>Name-string&nbsp;with&nbsp;authorship</b>: A [[#NameString][Name-string]] that includes the Code-appropriate authorships embedded within the [[#NameString][name-string]].
		* [[NameStringWithAuthorship][Name-string with authorship discussion]]

#NameUnit
	<b>Name-unit</b>: A portion of a multi-part [[#NameString][name-string]] that constitutes one discrete [[#RankDefinition][Rank]]. There do not appear to be any cases where a single name-unit would contain a space (" "), but it may include a hyphen ("-") or other characters outside the standard letters.
		* [[NameUnit][Name-unit discussion]]
d29 2
a30 2
#NameUsage
	<b>Name-usage</b>: The appearance of a [[#NameString][Name-string]] within a [[#ReferenceDefinition][Reference]].
d34 1
a34 1
	<b>Protonym</b>: Effectively identical to a basionym (although we need to confirm that in cases of a repacement name or nom. nov., there are two protonyms, but only one basionym.  Protonyms and basionyms probably do not need to be discussed separately, as long as we acknowledge that the schema will keep track of special cases of repacement name and nom. nov. A protonym exists ONLY in the context of a particular kind of [[#NameUsage][Name-usage]] that represents a code-compliant original description of a new basionym (i.e., new terminal epithet).
d37 1
a37 1
#NewCombination
d39 1
a39 1
		* [[NewCombination][New Combination discussion]]
d41 2
a42 2
#VariantSpelling
	<b>Variant&nbsp;spelling</b>: This term refers to variant spellings (i.e., slightly different [[#NameString][Name-strings]]) used for what is otherwise a pre-existing [[#ProtonymDefinition][Protonym]] or [[#NewCombination][New Combination]].  These include intentional variations (e.g., alternate gender forms of Species-group epithets), as well as unintentional variations (i.e., [[#LapsusDefinition][Lapsus]]). Variant spellings exist ONLY in the context of a [[#NameUsage][Name-usage]].
d46 1
a46 1
	<b>Lapsus</b>: A particular kind of [[#VariantSpelling][Variant spelling]] that represents an unintentional alternate [[#NameString][Name-string]] (e.g., typographical error).
d54 1
a54 1
	<b>Publication</b>:  A special subset of [[#ReferenceDefinition][References]] that have been "published" in some way (perhaps best to define "publication" in accordance with ICZN/ICBN rules governing publications????)
d57 3
a59 3
#UnpublishedDocumentation
	<b>Unpublished&nbsp;Documentation</b>:  Permanently documented information (e.g. on paper, in digital format) that has not been published to a wider audience. This includes letters, laboratory or field books. It does not include forms of information attribution like "pers. comm.", which are not documented in any way. -- Gregor
		* [[UnpublishedDocumentation][Unpublished Documaentation discussion]]
d61 2
a62 1
---
@


1.10
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="NozomiJamesYtow" date="1099198589" format="1.0" version="1.10"}%
d3 1
a3 1
These are some definitions that I am proposing for use in further discussion.  Note that the word "name" is not on this list, without some sort of qualification. We should all try to avoid using the word "name" without an explicit context. All definitions assume the scope of nomenclature defined for <nop>LinneanCore's domain, which is *tentatively* the Code-governed scientific names, plus possibly Trade Names, plus possibly some non-code-governed extensions of code-governed names [races, etc.], plus Linnean-type names used above the rank of Family (not technically governed by the Codes of Nomenclature -- at least not ICZN/ICBN.  Please feel free to comment/ammend/etc. -- (When these definitions are finalized, I suggest we move all comentary associated with the definitions to a separate LinneanCoreDefinitionsDiscussion page. - 30 Oct 2004)
d6 2
a7 1
	Rank: A specific, most-precise taxonomic rank (including intermediate ranks, such as "Subgenus", "Subspecies", etc.).  See [[http://efgblade.cs.umb.edu/twiki/pub/UBIF/EnumerationTypes/UBIF-Docu-Enumerations.html#TaxonomicRankEnum][TaxonomicRankEum]].
d10 2
a11 1
	Rank-group:  The "full" ranking groups. Within the context of Codes of nomenclature, these include only "Family-group", "Genus-group", and "Species-group".  However, we will also need to deal with "Order-group", "Class-group", "Phylum-group", and "Kingdom-group" entities as well.  I realize that "Phylum-group" is Zoo-centric, but since "Division" is used for different Ranks by different disciplines (even different sub-disciplines within Zoology), and "Phylum" is only used for one rank, I propose that we use "Phylum-group", "Phylum", "Subphylum", etc. -- and assume that these are all precisely synonymous with the botanical "Division" equivalencies.
d14 2
a15 1
	Name-literal:  A literal word (or words) designating at least one object.  A single name-literal may designate multiple objects (homonymy) and multiple name-literals may designate single object (synonymy).  A name-literal is an abstraction of a set of [[#NameUsage][name-usages]].  A [[#NameString][name-string]] is an electronic representation of a name-literal.  A name-literal may have [[#VariantSpelling][variant spellings]]; each variant is represented by a [[#NameString][name-string]]. 
d18 1
a18 1
	Name-string:  The Unicode string equivalent of [[#NameLiteral][name-literal]] printed on paper or represented in an electronic document to indicate a scientific name within the scope of <nop>LinneanCore's domain. It does *not* include authorship, but does include markup such as parentheses around infrageneric/supraspecific [[#NameUnit][Name-units]], and infraspecific prefixes (e.g., subsp., var., f. etc.). A Name-string DOES NOT EXIST outside the context of a [[#NameUsage][Name-usage]].
d21 3
a23 3
#NameStringPlusAuthorship		
	Name-string&nbsp;plus&nbsp;authorship: A [[#NameString][Name-string]] that includes the Code-appropriate authorships embedded within the [[#NameString][Name-string]]. Not sure whether this should always be anchored to a usage.
		* Gregor: Please elaborate about the last sentence, I do not understand this - then delete this question. -- 30. Oct. 2004
d26 1
a26 1
	Name-unit: A portion of a multi-part (multinomial? polynomial? I think of the latter as a mathematical term...) that constitutes one discrete [[#RankDefinition][Rank]]. I don't think there are any cases where a single *Name-unit* would contain a space (" "), but it may include a hyphen ("-") or other characters outside the standard letters.
d30 2
a31 1
	Name-usage: The appearance of a [[#NameString][Name-string]] within a [[#ReferenceDefinition][Reference]].
d34 2
a35 1
	Protonym: Effectively identical to a *Basionym* (although we need to confirm that in cases of a repacement name or nom. nov., there are two *Protonyms*, but only one *Basionym*.  I think we don't need to discuss *Protonyms* and *Basionyms* separately, as long as we acknowledge that the schema will keep track of special cases of repacement name and nom. nov. A *Protonym* exists ONLY in the context of a particular kind of [[#NameUsage][Name-usage]] that represents a code-compliant original description of a new Basionym (i.e., new terminal epithet).
d38 2
a39 1
	New&nbsp;combination: A re-use of a previously-existing Protonym in a different nomenclatural context.  In the Botany world these are thought of as discrete "names", separate from their [[#ProtonymDefinition][Protonyms]]; but in Zoology they are usually thought of as merely different contextual usages of a pre-existing "name" ([[#ProtonymDefinition][Protonym]]).  Although ICZN does not have any rules to determine which "revised contextual usages" of pre-existing [[#ProtonymDefinition][Protonyms]] constitute an "official" *New Combination*, in most cases it will be more or less unambiguously determinable who first placed a pre-existing species epithet into a different nomenclatural context. In any case, *New combinations* ONLY in the context of a particular kind of usage that represents a subsequent use of a pre-existing [[#ProtonymDefinition][Protonym]] in a novel nomenclatural context (e.g., the first placement of an existing species epithet into a different genus than the epithet was originally described in (i.e., the nomenclatural context of it's [[#ProtonymDefinition][Protonym]]). *QUESTION:* Should we define this exactly as the Botanical Code defines it -- e.g., exclusive of novel placements within a different subgenus context?
d42 2
a43 1
	Variant&nbsp;spelling: This term refers to variant spellings (i.e., slightly different [[#NameString][Name-strings]]) used for what is otherwise a pre-existing [[#ProtonymDefinition][Protonym]] or [[#NewCombination][New Combination]].  These include intentional variations (e.g., alternate gender forms of Species-group epithets), as well as unintentional variations (i.e., [[#LapsusDefinition][Lapsus]]). *Variant spellings* exist ONLY in the context of a [[#NameUsage][Name-usage]].
d46 2
a47 1
	Lapsus: A particular kind of [[#VariantSpelling][Variant spelling]] that represents an unintentional alternate [[#NameString][Name-string]] (e.g., typographical error).
d50 1
a50 1
	Reference: Any form of DOCUMENTED date-stamped instance of one or more Authors (Agents).  This is broadly defined to include forms of documentation outside the context of [[#PublicationDefinition][Publications]]. "Documented" means that at least one physical (paper) or "permanent" electronic representation/facsimilie of information presented by Agent-Authors at a specific date/time is archived somewhere. Besides [[#PublicationDefinition][Publications]], these can include things like written personal communication (or archived representation of verbal personal communication), specimen labels, field notebooks, etc., etc.
d54 1
a54 1
	Publication:  A special subset of [[#ReferenceDefinition][References]] that have been "published" in some way (perhaps best to define "publication" in accordance with ICZN/ICBN rules governing publications????)
d58 2
a59 1
	Unpublished&nbsp;Documentation:  Permanently documented information (e.g. on paper, in digital format) that has not been published to a wider audience. This includes letters, laboratory or field books. It does not include forms of information attribution like "pers. comm.", which are not documented in any way. -- Gregor
a60 1
-- Main.RichardPyle - 29 Oct 2004
a61 3

I would hope for a revision of protonym, and perhaps a definition where nom. nov. / replacement name appears. -- Gregor

@


1.9
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="RichardPyle" date="1099193389" format="1.0" version="1.9"}%
d33 1
a33 1
	New&nbsp;combination: A re-use of a previously-existing Protonym in a different nomenclatural context.  In the Botany world these are thought of as discrete "names", separate from their [[#ProtonymDefinition][Protonyms]]; but in Zoology they are usually thought of as merely different contextual usages of a pre-existing "name" ([[#ProtonymDefinition][Protonym]]).  Although ICZN does not have any rules to determine which "revised contextual usages" of pre-existing [[#ProtonymDefinition][Protonyms]] constitute an "official" *New Combination*, in most cases it will be more or less unambiguously determinable who first placed a pre-existing species epithet into a different nomenclatural context. In any case, *New combinations* ONLY in the context of a particular kind of usage that represents a subsequent use of a pre-existing [[#ProtonymDefinition][Protonym]] in a novel nomenclatural context (e.g., the first placement of an existing species epithet into a different genus than the epithet was originally described in (i.e., the nomenclatural context of it's [[#ProtonymDefinition][Protonym]). *QUESTION:* Should we define this exactly as the Botanical Code defines it -- e.g., exclusive of novel placements within a different subgenus context?
@


1.8
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="NozomiJamesYtow" date="1099185900" format="1.0" version="1.8"}%
d55 2
a56 1
-- Rich: for your information, please delete this paragraph once read (it will not self-destroy though): I already did the moving, removed ASCII from ASCII/Unicode (XML is always Unicode). For *Rank-group* I wonder why you discuss this term. I think since it can be derived from knowledge of the rank, it is not necessary in LC - do you disagree? I would hope for a revision of protonym, and perhaps a definition where nom. nov. / replacement name appears. -- Gregor
@


1.7
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="NozomiJamesYtow" date="1099180740" format="1.0" version="1.7"}%
d5 2
d8 2
a9 1
	* *Rank*: A specific, most-precise taxonomic rank (including intermediate ranks, such as "Subgenus", "Subspecies", etc.).  See [[http://efgblade.cs.umb.edu/twiki/pub/UBIF/EnumerationTypes/UBIF-Docu-Enumerations.html#TaxonomicRankEnum][TaxonomicRankEum]].
d11 2
a12 1
	* *Rank-group*:  The "full" ranking groups. Within the context of Codes of nomenclature, these include only "Family-group", "Genus-group", and "Species-group".  However, we will also need to deal with "Order-group", "Class-group", "Phylum-group", and "Kingdom-group" entities as well.  I realize that "Phylum-group" is Zoo-centric, but since "Division" is used for different Ranks by different disciplines (even different sub-disciplines within Zoology), and "Phylum" is only used for one rank, I propose that we use "Phylum-group", "Phylum", "Subphylum", etc. -- and assume that these are all precisely synonymous with the botanical "Division" equivalencies.
d14 6
a19 4
	* *Name-string*:  The Unicode equivalent of a literal string of text characters printed on paper or represented in an electronic document to indicate a scientific name within the scope of <nop>LinneanCore's domain. It does *not* include authorship, but does include markup such as parentheses around infrageneric/supraspecific *Name-Units*, and infraspecific prefixes (e.g., subsp., var., f. etc.). A Name-string DOES NOT EXIST outside the context of a [[#NameUsage][Name-usage]].
		* NameString discussion
		
	* *Name-string plus authorship*: A *Name-string* that includes the Code-appropriate authorships embedded within the *Name-string*. Not sure whether this should always be anchored to a usage.
d22 6
a27 2
	* *Name-unit*: A portion of a multi-part (multinomial? polynomial? I think of the latter as a mathematical term...) that constitutes one discrete *Rank*. I don't think there are any cases where a single *Name-unit* would contain a space (" "), but it may include a hyphen ("-") or other characters outside the standard letters.
		* NameUnit discussion
d29 2
a30 1
	* *Name-usage*: The appearance of a *Name-string* within a *Reference*.
d32 2
a33 1
	* *Protonym*: Effectively identical to a *Basionym* (although we need to confirm that in cases of a repacement name or nom. nov., there are two *Protonyms*, but only one *Basionym*.  I think we don't need to discuss *Protonyms* and *Basionyms* separately, as long as we acknowledge that the schema will keep track of special cases of repacement name and nom. nov. A *Protonym* exists ONLY in the context of a particular kind of *Name-usage* that represents a code-compliant original description of a new Basionym (i.e., new terminal epithet).
d35 2
a36 1
	* *New combination*: A re-use of a previously-existing Protonym in a different nomenclatural context.  In the Botany world these are thought of as discrete "names", separate from their *Protonyms*; but in Zoology they are usually thought of as merely different contextual usages of a pre-existing "name" (*Protonym*).  Although ICZN does not have any rules to determine which "revised contextual usages" of pre-existing *Protonyms* constitute an "official" *New Combination*, in most cases it will be more or less unambiguously determinable who first placed a pre-existing species epithet into a different nomenclatural context. In any case, *New combinations* ONLY in the context of a particular kind of usage that represents a subsequent use of a pre-existing *Protonym* in a novel nomenclatural context (e.g., the first placement of an existing species epithet into a different genus than the epithet was originally described in (i.e., the nomenclatural context of it's *Protonym*). *QUESTION:* Should we define this exactly as the Botanical Code defines it -- e.g., exclusive of novel placements within a different subgenus context?
d38 2
a39 1
	* *Variant spellings*: This term refers to variant spellings (i.e., slightly different *Name-strings*) used for what is otherwise a pre-existing *Protonym* or *New Combination*.  These include intentional variations (e.g., alternate gender forms of Species-group epithets), as well as unintentional variations (i.e., *Lapsus*). *Variant spellings* exist ONLY in the context of a *Name-usage*.
d41 3
a43 1
	* *Lapsus*: A particular kind of *Variant spelling* that represents an unintentional alternate *Name-string* (e.g., typographical error).
d45 3
a47 5
	* *Reference*: Any form of DOCUMENTED date-stamped instance of one or more Authors (Agents).  This is broadly defined to include forms of documentation outside the context of *Publications*. "Documented" means that at least one physical (paper) or "permanent" electronic representation/facsimilie of information presented by Agent-Authors at a specific date/time is archived somewhere. Besides *Publications*, these can include things like written personal communication (or archived representation of verbal personal communication), specimen labels, field notebooks, etc., etc.
		* [[Reference]] discussion
		
	* *Publication*:  A special subset of *References* that have been "published" in some way (perhaps best to define "publication" in accordance with ICZN/ICBN rules governing publications????)
		* [[Publication]] discussion
d49 2
a50 1
	* *Unpublished Documentation*:  Permanently documented information (e.g. on paper, in digital format) that has not been published to a wider audience. This includes letters, laboratory or field books. It does not include forms of information attribution like "pers. comm.", which are not documented in any way. -- Gregor
@


1.6
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="GregorHagedorn" date="1099178405" format="1.0" version="1.6"}%
d5 1
d10 3
a12 11
	* *Name-string*:  The Unicode equivalent of a literal string of text characters printed on paper or represented in an electronic document to indicate a scientific name within the scope of <nop>LinneanCore's domain. It does *not* include authorship, but does include markup such as parentheses around infrageneric/supraspecific *Name-Units*, and infraspecific prefixes (e.g., subsp., var., f. etc.). A Name-string DOES NOT EXIST outside the context of a *Name-usage*.
		* JMS: It would be better to use *Linnean name-string* for  <nop>LinneanCore specific name-string.  Do we need to restrict to ASCII/Unicode?  Do you have distinguish what printed on paper (glyph) and its electronic representation?  What do you mean by "context" here?  Nomenclatural correction can be made without correcting publication.  Do you include such machine-generated one as a *Name-usage*? -- 30 Oct 2004
		* Richard Pyle: My intention was for these definitions to exist only within the context of <nop>LinneanCore discussions, so "Linnean name-string" seems redundant. But if you want these definitions to have broader scope, then I suppose you could qualify it that way....but how would the definition of a "*Vernacular name-string*" (or other qualified name-string) differ from this definition?
			* JMS: I'd like to keep broder if possible, because we would need to say "such such is out of scope of <nop>LinneanCore; should be treated separetely (parhaps by TCS)" etc.  We'd better separate definition part, and <nop>LinneanCore specific part, e.g. " ...printed on paper or represented in an electronic document to designate a named object.  It is a scientific name within the scope of <nop>LinneanCore's domain." -- Oct 30 2004
			* (RP, cont.) I guess there is no need to specify "printed on paper or represented in an electronic document" -- I only added that bit to emphasize that the *Name-string* exists only in the context of a *Name-usage*. I mentioned "ASCII/Unicode" because I wanted to emphasize that the *Name-string* is the electronic representation of the *Name-string* (I've modified the definition to reflect this).  Are there other ways to electronically represent text strings besides ASCII/Unicode?  The reason for the restriction to electronic representation is that I assumed that LC data would always be represented electronically (at least at some point in its life).  The transliteration of printed scientific names into Unicode *Name-strings* is not perfect (even more problematic with ASCII), so the LC *Name-string* is specifically intended to mean the electronic version.
			* JMS: Again I prefer to broader defintion with restriction to <nop>LinneanCore.  TDWG-ish XML schema treates texts as UTF-8 generally, but it does not exclude to have name-strings on specimen label in a JPEG file.  How about " A literal string of text characters printed on paper or represented in an electronic document to desiganate a named-object.  It is a scientific name represented in UTF-8 within the scope of <nop>LinneanCore's domain." -- Oct 30 2004
				* Richard Pyle: I'm inclined to agree with all of your points, and change the definition accordingly.  However, I just want to establish clarity on one point.  In my mind, the word "string" in this context refers *specifically* to a sequence of electronically-rendered (ASCII/Unicode) characters. I do not think of a JPEG or bitmap rendering of a series of printed characters as a "string" composed of characters -- I think of these as images composed of pixels.  Thus, to me the "string* implies a standard computer-text (ASCII/Unicode) sequence of characters.  I think of the *Name-string* specifically as a schema element in LC (or TCS) that can be searched using text-comparison computer filter procedures.  So to me, the *Name-string* is not really a "name object", but an ASCII/Unicode (or UTF-8, if you prefer) <em>representation</em> of a name object.  In the case of electronic *References*, they are the same.  In the case of paper-printed *References*, there is an implied transliteration.  *HOWEVER*, I am willing to change my views on this and define a "Name-string" as a name object (as you suggest), and qualify that within the context of LC it implies a UTF-8 character string -- if you (or others) feel strongly about this. -- 30 Oct 2004
		* (RP, cont.) By "context", I was specifically trying to distinguish the *Name-string* as the literal text string represented in a taxonomic *Reference*, and *not* some sort of "corrected" nomenclatural representation that exists only within LC.  Perhaps we need a different definition for "*Code-compliant name-string*" to accomodate the machine-generated "corrected" strings?  The Machine-generated instance might be considered as a *Name-usage*, and therefore its corrected nomenclatural representation could be considered as a *Name-string*.  But the point is, it would be considered a *Name-string* only in the context of the machine-generated *Name-usage*; not in the context of the *Name-usage* of the source *Reference* Upon which the Machine name instance is based. -- 30 Oct 2004
		* Gregor: What do you mean by "Name-string exists only in the context of a Name-usage"? What does exist mean? The primary issue with names for me is their comparability. I want to know who else said something about the pathogen I believe I have. Thus I need to define equality rules for name-strings across name usage. In some respect this is what you do when you enter a name in Google etc. What is that string of unicode characters entered in Google that represents a scientific organism name? This is to me the essential item I would call a name string. No problem having another term for it - but give one. Name-string to me seems the obvious choice, rather than constraining name-string to string in name-usage context. -- 30. Oct. 2004
		* Gregor: I am rather confused why you limit Name-String to NOT include authors. In my practice I have no use for this term. A name-string without authors is an ambiguous in incomplete namestring. If I want to make conclusions based on name strings in printed or digital publications, I can use name-string with authors, or have to guess about the authors from geographical or historical context. To me the the Name-string-without-authors seems to be the special case. Is this botany against zoology? Or just Gregor :-) ? -- 30. Oct. 2004

d17 1
a17 1
		* Gregor: a multi-part *what*? Name-string? Name-string-with-authors? I think you mean words or terms in a name string, but I do not understand the definition. Do you mean "Aceraceae: Acer rubrum spp. rubrum L." has 6, 5, 4, or 3 units? In general, I propose to use "part" instead of unit: *Name-part*: A part of a multi-part Name-string-with-authors, delimited by whitespace, expcept in the case of authors where each name constitutes a part, and in the case of rank connecting terms composed of multiple words ("fm. spec."). What about the sensu suffixes? -- 30. Oct. 2004
d30 4
a33 1
		* Gregor: I think this does not work. The instance of the author of this text is sitting in front of the screen in Germany. It is not date-stamped. Honestly - I do not get what you try to express. I propose to add to publication "unpublished documentation" (letters, labbooks) and use this in the context, but I still do not get what you mean by the reference definition. Why is it not Reference: An attempt to make an unambiguous reference to a publication or unpublished documentation, optionally including a fragment identfier like a page number. A reference does not have to include publication date or authorship, provided the reference is unambiguous by other means (e.g. author plus volume number ("Sacc. XXII: 421"), or title that is unambiguous in the context ("Species plantarum, p. 30"). -- 30. Oct. 2004
a34 2
	* *Publication*:  A special subset of *References* that have been "published" in some way (perhaps best to define "publication" in accordance with ICZN/ICBN rules governing publications????)
		* Gregor: I do not think a publication is a subclass of references. A reference refers to an entire publication (or unpubl. documentation) or a fragment therein. -- 30. Oct. 2004
d40 1
a40 2
-- Rich: for your information, please delete this paragraph once read (it will not self-destroy though): I already did the moving, removed ASCII from ASCII/Unicode (XML is always Unicode). For *Rank-group* I wonder why you discuss this term. I think since it can be derived from knowledge of the rank, it is not necessary in LC - do you disagree? I would hope for a revision of protonym, and perhaps a definition where nom. nov. / replacement name appears. -- Gregor

@


1.5
log
@none
@
text
@d1 3
a3 5
%META:TOPICINFO{author="RichardPyle" date="1099171800" format="1.0" version="1.5"}%
%META:TOPICPARENT{name="LinneanCoreDisentangle"}%
These are some definitions that I am proposing for use in further discussion.  Note that the word "name" is not on this list, without some sort of qualification. We should all try to avoid using the word "name" without an explicit context. All definitions assume the scope of nomenclature defined for <nop>LinneanCore's domain, which is *tentatively* the Code-governed scientific names, plus possibly Trade Names, plus possibly some non-code-governed extensions of code-governed names [races, etc.], plus Linnean-type names used above the rank of Family (not technically governed by the Codes of Nomenclature -- at least not ICZN/ICBN.  Please feel free to comment/ammend/etc. 

		* Richard Pyle: When these definitions are finalized, I suggest we move all comentary associated with the definitions to a separate LinneanCoreDefinitionsDiscussion page, and move this page to root LinneanCore page (i.e., not nested within the LinneanCoreDisentangle page) - 30 Oct 2004
d9 1
a9 1
	* *Name-string*:  The ASCII/Unicode equivalent of a literal string of text characters printed on paper or represented in an electronic document to indicate a scientific name within the scope of <nop>LinneanCore's domain. It does *not* include authorship, but does include markup such as parentheses around infrageneric/supraspecific *Name-Units*, and infraspecific prefixes (e.g., subsp., var., f. etc.). A Name-string DOES NOT EXIST outside the context of a *Name-usage*.
d17 2
d21 1
d24 1
d36 2
a37 1
	* *Reference*: Any form of DOCUMENTED date-stamped instance of one or more Authors (Agents).  This is broadly defined to include forms of documentation ourside the context of *Publications*. "Documented" means that at least one physical (paper) or "permanent" electronic representation/facimilie of information presented by Agent-Authors at a specific date/time is archived somewhere. Besides *Publications*, these can include things like written personal communication (or archived representation of verbal personal communication), specimen labels, field notebooks, etc., etc.
d40 2
d43 2
d46 2
a47 1
-- Main.RichardPyle - 29 Oct 2004
@


1.4
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="NozomiJamesYtow" date="1099163856" format="1.0" version="1.4"}%
d3 3
a5 1
These are some definitions that I am proposing for use in further discussion.  Note that the word "name" is not on this list, without some sort of qualification. We should all try to avoid using the word "name" without an explicit context. All definitions assume the scope of nomenclature defined for <nop>LinneanCore's domain, which is *tentatively* the Code-governed scientific names, plus possibly Trade Names, plus possibly some non-code-governed extensions of code-governed names [races, etc.], plus Linnean-type names used above the rank of Family (not technically governed by the Codes of Nomenclature -- at least not ICZN/ICBN.  Please feel free to comment/ammend/etc.
d15 1
a15 1
		* (RP, cont.) I guess there is no need to specify "printed on paper or represented in an electronic document" -- I only added that bit to emphasize that the *Name-string* exists only in the context of a *Name-usage*. I mentioned "ASCII/Unicode" because I wanted to emphasize that the *Name-string* is the electronic representation of the *Name-string* (I've modified the definition to reflect this).  Are there other ways to electronically represent text strings besides ASCII/Unicode?  The reason for the restriction to electronic representation is that I assumed that LC data would always be represented electronically (at least at some point in its life).  The transliteration of printed scientific names into Unicode *Name-strings* is not perfect (even mor eproblematic with ASCII), so the LC *Name-string* is specifically intended to mean the electronic version.
d17 1
@


1.3
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="RichardPyle" date="1099158900" format="1.0" version="1.3"}%
d11 5
a15 1
		* Richard Pyle: My intention was for these definitions to exist only within the context of <nop>LinneanCore discussions, so "Linnean name-string" seems redundant. But if you want these definitions to have broader scope, then I suppose you could qualify it that way....but how would the definition of a "*Vernacular name-string*" (or other qualified name-string) differ from this definition?  I guess there is no need to specify "printed on paper or represented in an electronic document" -- I only added that bit to emphasize that the *Name-string* exists only in the context of a *Name-usage*. I mentioned "ASCII/Unicode" because I wanted to emphasize that the *Name-string* is the electronic representation of the *Name-string* (I've modified the definition to reflect this).  Are there other ways to electronically represent text strings besides ASCII/Unicode?  The reason for the restriction to electronic representation is that I assumed that LC data would always be represented electronically (at least at some point in its life).  The transliteration of printed scientific names into Unicode *Name-strings* is not perfect (even mor eproblematic with ASCII), so the LC *Name-string* is specifically intended to mean the electronic version.  By "context", I was specifically trying to distinguish the *Name-string* as the literal text string represented in a taxonomic *Reference*, and *not* some sort of "corrected" nomenclatural representation that exists only within LC.  Perhaps we need a different definition for "*Code-compliant name-string*" to accomodate the machine-generated "corrected" strings?  The Machine-generated instance might be considered as a *Name-usage*, and therefore its corrected nomenclatural representation could be considered as a *Name-string*.  But the point is, it would be considered a *Name-string* only in the context of the machine-generated *Name-usage*; not in the context of the *Name-usage* of the source *Reference* Upon which the Machine name instance is based. -- 30 Oct 2004
@


1.2
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="NozomiJamesYtow" date="1099100513" format="1.0" version="1.2"}%
d9 3
a11 2
	* *Name-string*:  The literal string of ASCII/Unicode text characters printed on paper or represented in an electronic document to indicate a scientific name within the scope of <nop>LinneanCore's domain. It does *not* include authorship, but does include markup such as parentheses around infrageneric/supraspecific *Name-Units*, and infraspecific prefixes (e.g., subsp., var., f. etc.). A Name-string DOES NOT EXIST outside the context of a *Name-usage*.
		* JMS: It would be better to use Linnean name-string for  <nop>LinneanCore specific name-string.  Do we need to restrict to ASCII/Unicode?  Do you have distinguish what printed on paper (glyph) and its electronic representation?  What do you mean by "context" here?  Nomenclatural correction can be made without correcting publication.  Do you include such machine-generated one as a Name-usage? -- 30 Oct 2004
@


1.1
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="RichardPyle" date="1099086780" format="1.0" version="1.1"}%
d10 1
@