<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>> It's somewhat clear what uBio identifiers refer to: names vs. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>> something more nebulous involving taxa or ... something. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>> (Not trying to push your button, Rich Pyle).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>:-)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Actually, saying that uBio identifiers refer to “names” is a bit like saying uBio identifiers refer to “stuff” (which is only slightly more ambiguous than “names”). I think what you mean (a bit more explicitly) is that uBio identifiers refer to “name-strings”, wherein each unique literal UTF-8-encoded string of characters purported to represent a scientific name receives an integer as an identifier.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>GNI also assigns unique identifiers to such name-strings, but the difference is that the GNI identifier is a hash of the string itself. Thus, given a string, you can algorithmically derive the GNI identifier for it. There is no way to algorithmically convert the uBio name-strings into their corresponding integer uBio identifiers.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I have a question, and a suggestion.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Question: Are new uBio integer identifiers ever going to be minted? Or do we just want to maintain them for legacy purposes?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Suggestion: Regardless of the answer to the question, I suggest that Dima generate an index for uBio integer identifiers and the corresponding hash uuid used by GNI. I will import these into BioGUID.org, so going forward we will always have an index to translate the uBio integers into the GN hashed UUIDs. From there, it would be a simple step to allow GN services to process uBio identifiers natively, and do all the cool things that Steve (and others) would like uBio/GN to do.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Aloha,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Rich<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> tdwg-content-bounces@lists.tdwg.org [mailto:tdwg-content-bounces@lists.tdwg.org] <b>On Behalf Of </b>Steve Baskauf<br><b>Sent:</b> Friday, October 16, 2015 3:09 AM<br><b>To:</b> Dmitry Mozzherin<br><b>Cc:</b> Chuck Miller; tdwg-content@lists.tdwg.org; Jonathan A Rees; Shorthouse, David<br><b>Subject:</b> Re: [tdwg-content] status of uBio<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks all for the information and comments about the status of uBio. I'm glad to hear that the server will probably come back up. If not, then I hope the data will be made available to those who said they would be willing to host it.<br><br>I have been interested in using the uBio identifiers for several reasons:<br>1. They have managed to stick around for a long time and are stable in their format (as LSIDs and HTTP proxied LSIDs).<br>2. The coverage of names is really good for plants, animals, different geographic locations, etc. I also use ITIS identifiers but it's fairly common for me to not be able to find one for the name I need, which almost never happens with uBio.<br>3. It's somewhat clear what uBio identifiers refer to: names vs. something more nebulous involving taxa or ... something. (Not trying to push your button, Rich Pyle). <br>4. You can actually get RDF associated with the LSID version of the uBio identifiers. I was wanting to download some to play with in our new triplestore (<a href="http://rdf.library.vanderbilt.edu">http://rdf.library.vanderbilt.edu</a>) when I discovered that the server was down. The RDF is somewhat ad hoc, but hey, it's there.<br><br>There isn't really any other source that has all of these characteristics. So please keep uBio going indefinitely, if at all possible. <br>Steve<br><br>Dmitry Mozzherin wrote: <o:p></o:p></p><div><p class=MsoNormal>I had been administering uBio for the last year, but now I am moving from MBL. uBio machine is in a bad shape, and it crashes after a few hours of work. My plan is to create Docker containers for database, code and data, which should make whole system much more stable, and much more manageable. Good news I will definitely try my best to do it, the bad news I am spread thinner than usual with move, transferring hardware and grant, GN things, EOL things, and figuring out what to do with the house etc. uBio 'code' part is about 35 Gb, which makes the task more complicated, but I am quite optimistic that I will be able to make containers and put them either on an MBL machine, run it from University of Illinois, or give it to Naturalis -- depending on what will make more sense for Dave Remsen, MBL and all interested in the project.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><pre>-- <o:p></o:p></pre><pre>Steven J. Baskauf, Ph.D., Senior Lecturer<o:p></o:p></pre><pre>Vanderbilt University Dept. of Biological Sciences<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>postal mail address:<o:p></o:p></pre><pre>PMB 351634<o:p></o:p></pre><pre>Nashville, TN 37235-1634, U.S.A.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>delivery address:<o:p></o:p></pre><pre>2125 Stevenson Center<o:p></o:p></pre><pre>1161 21st Ave., S.<o:p></o:p></pre><pre>Nashville, TN 37235<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>office: 2128 Stevenson Center<o:p></o:p></pre><pre>phone: (615) 343-4582, fax: (615) 322-4942<o:p></o:p></pre><pre>If you fax, please phone or email so that I will know to look for it.<o:p></o:p></pre><pre><a href="http://bioimages.vanderbilt.edu">http://bioimages.vanderbilt.edu</a><o:p></o:p></pre><pre><a href="http://vanderbilt.edu/trees">http://vanderbilt.edu/trees</a><o:p></o:p></pre><pre><o:p> </o:p></pre></div></div></body></html>