<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">There are W3C standards for expressing (tagging) the language of elements in an XML document [1], which is built into the XML standard (the xml:lang attribute), and for the language of strings in RDF documents [2] (like this: "some string"@en-US). The tags for languages are also standardized [3].<div><br></div><div>I'd strongly recommend against reinventing mechanisms for this - XML is for exchanging, and not displaying information. Reinventions of the standard (like the below, or putting the language into parentheses) typically appear motivated by how one would like to display the information - that's what XSLT or custom programming is for, though.</div><div><br></div><div>Using the notation for text in RDF, you could easily enumerate several strings, each tagged with a different language and perhaps delimited by comma, for a single instance of DwC-A field.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>-hilmar</div><div><br></div><div>[1] <a href="http://www.w3.org/TR/xml-i18n-bp/#AuthLang">http://www.w3.org/TR/xml-i18n-bp/#AuthLang</a></div><div>[2] <a href="http://www.w3.org/2007/OWL/wiki/InternationalizedStringSpec#Preliminaries">http://www.w3.org/2007/OWL/wiki/InternationalizedStringSpec#Preliminaries</a></div><div>[3] <a href="http://www.w3.org/International/questions/qa-choosing-language-tags">http://www.w3.org/International/questions/qa-choosing-language-tags</a></div><div> </div><div><div><div>On Jul 21, 2011, at 11:23 AM, Geoffrey Allen wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Greeting,<div><br></div><div>I have recently begun the process of digitising the 60,000 specimen vouchers from the UNB herbarium. The textual data for 40,000+ of those has already been entered into a database, and I am now trying to map those values to DwC so that we may share the data with other collections.</div><div><br></div><div>I have some concern over the fact that simple DwC does not allow the repetition or extension of certain fields. The vernacularName field is a particular problem. New Brunswick is Canada's only officially bilingual province, as such, our specimens are all identified with both their English and French common names in the database. It would be very useful if we could extend DwC, creating something along the lines of <vernacularName lang=en>, or allow nesting of elements, perhaps in the form:</div><div><vernacularName> </div><div><span class="Apple-tab-span" style="white-space:pre"> </span><English>Chives</English></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><French>Ciboulette, brulotte</French></div><div></vernacularName> </div><div><br></div><div>The other option, as I see it, is that we store the English and French common names in our own fields, and then concatenate the two to create the DwC:vernacularName field. I see this option as less than ideal since it may hinder search/browsability. It may also cause a host of other problems from interpreting to storing the data. The herbarium with whom we first intent to share the data has already expressed a concern that their system cannot handle the diacritics found in many of the French names (!). They would like the Eng. common names, but not the French. This is more difficult to achieve if we concat the values.</div><div><br></div><div>One additional thought is that the herbarium's imprint, _Flora of New Brunswick_, also includes common names in Maliseet and Mi'kmaq wherever possible. Although these two aboriginal languages do not currently exist in the dataset we are using, there is the potential that they may be added at some point in the future. </div><div><br></div><div>It seems to me that the repetition of fields may be necessary in other instances too. I am having some difficulty figuring out how to record all the location data we have for the specimens, which are indicated using verbal descriptions, Lat/Long, UTM, and NTS coordinates - in many cases using all 4 for a single sample, but I will save the details for another posting.</div><div><br></div><div>I will watch for the group's thoughts on this problem.</div><div><br></div><div>Many thanks,</div><div>Geoffrey</div><div><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>--------------------------------------------</div><div><br></div><div>Geoffrey Allen</div><div>Digital Projects Librarian</div><div>Electronic Text Centre</div><div>Harriet Irving Library</div><div>University of New Brunswick</div><div>Fredericton, NB E3B 5H5<br>Tel: (506) 447-3250</div><div>Fax: (506) 453-4595</div><div><a href="mailto:gsallen@unb.ca">gsallen@unb.ca</a></div></div></div></span></span> </div> <br></div></div>_______________________________________________<br>tdwg-content mailing list<br><a href="mailto:tdwg-content@lists.tdwg.org">tdwg-content@lists.tdwg.org</a><br><a href="http://lists.tdwg.org/mailman/listinfo/tdwg-content">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><br></blockquote></div><br><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><font class="Apple-style-span" face="Monaco" size="3"><span class="Apple-style-span" style="font-size: 11px; ">-- </span></font></div><div><font class="Apple-style-span" face="Monaco" size="3"><span class="Apple-style-span" style="font-size: 11px; ">===========================================================</span></font></div><div><font class="Apple-style-span" face="Monaco" size="3"><span class="Apple-style-span" style="font-size: 11px; ">: Hilmar Lapp -:- Durham, NC -:- informatics.nescent.org :</span></font></div><div><font class="Apple-style-span" face="Monaco" size="3"><span class="Apple-style-span" style="font-size: 11px; ">===========================================================</span></font></div><div><br class="webkit-block-placeholder"></div></div></span><br class="Apple-interchange-newline"> </div><br></div></body></html>