[tcs-lc] nameObjects, spellings, vernaculars, etc

[Roger Hyam]

Rich,

Yes that is how you do it.

Whether misspelled names get GUIDs is not an issue for the schema. That 
is another debate to be had in another place at another time. It will 
support them if they do and if they don't.

Roger

p.s. who are the "LC group"? You keep mentioning them. How does one join?


Richard Pyle wrote:

>>If you want to represent an alternative spelling of a name use a
>>TaxonConcept and/or a NameObject and relationships to express it
>>as a misspelling of the name.
>>    
>>
>
>Which element would contain the misspelled name? Would each misspelled name
>get its own NameObject instance (i.e., its own GUID) -- separate from the
>"code-correct" version of what would otherwise be the "same name" (=same
>protologue)?
>
>For example, would you have this situation:
>
><NameObjects>
>  <NameObject id="N001">
>    <Label>Asterropterix</Label>
>    <Rank>genus</Rank>
>    <CanonicalName>
>      <Simple>Asterropterix</Simple>
>      <Uninominal>Asterropterix</Uninominal>
>    </CanonicalName>
>    <CanonicalAuthorship>
>      <Simple>Rüppell, 1830</Simple>
>      <ProtonymAuthorship>
>        <Simple>Rüppell, 1830</Simple>
>        <Year>1830</Year>
>        <Authors>
>          <Name>Rüppell</Name>
>        </Authors>
>      </ProtonymAuthorship>
>    </CanonicalAuthorship>
>  </NameObject>
>  <NameObject id="N002">
>    <Label>Asterropteryx</Label>
>    <Rank>genus</Rank>
>    <CanonicalName>
>      <Simple>Asterropteryx</Simple>
>      <Uninominal>Asterropteryx</Uninominal>
>    </CanonicalName>
>    <CanonicalAuthorship>
>      <Simple>Rüppell, 1830</Simple>
>      <ProtonymAuthorship>
>        <Simple>Rüppell, 1830</Simple>
>        <Year>1830</Year>
>        <Authors>
>          <Name>Rüppell</Name>
>        </Authors>
>      </ProtonymAuthorship>
>    </CanonicalAuthorship>
> </NameObject>
></NameObjects>
>
>
>  
>
>>Just for the record a NameObject is a data structure for holding
>>pieces of data that resemble scientific biological names governed
>>by one of the codes ICBN, ICZN, ICNCP etc. It is not just for
>>validly/effectively/accepted/nice names you can store anything you
>>like in it that appears like it might be code compliant.
>>You can then make up TaxonConcepts that use it and synonymise these
>>concepts into the ones you like.  It really is pretty simple.
>>    
>>
>
>It may be simple, but as you decribe it, I don't think that a "NameObject"
>meets the needs of the LC group. I'm not sure what you mean, exactly, by
>"validly/effectively/accepted/nice", beacause each of those four words can
>have different meanings.
>
>Aloha,
>Rich
>
>
>
>  
>

-- 

==============================================
 Roger Hyam
----------------------------------------------
 Biodiversity Informatics
 Independent Web Development 
----------------------------------------------
 http://www.hyam.net  roger at hyam.net
----------------------------------------------
 2 Janefield Rise, Lauder, TD2 6SP, UK.
 T: +44 (0)1578 722782 M: +44 (0)7890 341847
==============================================


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/tcs-lc/attachments/20050506/b90fd5ef/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: roger.vcf
Type: text/x-vcard
Size: 275 bytes
Desc: not available
Url : http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/tcs-lc/attachments/20050506/b90fd5ef/roger.vcf