<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Pradnya,<br>
    <br>
    <blockquote type="cite">
      <p class="MsoNormal"><font size="2" color="navy" face="Arial"><span
            style="font-size:
            10.0pt;font-family:Arial;color:navy">About the identifiers,
            where do I see the
            acronym for an ontology? Can I use it with REST web services
            in place of
            ontology id and ontology version id? From your answer it
            seems is should be
            editable, is that correct?<o:p></o:p></span></font></p>
      <font size="2" color="navy" face="Arial"><span style="font-size:
          10.0pt;font-family:Arial;color:navy"><o:p></o:p></span></font></blockquote>
    It is editable if you are the one that submitted the ontology (or if
    you are an administrator of an NCBO Virtual Appliance). We're
    looking at implementing lookups using the abbreviation in a future
    version.<br>
    <br>
    <blockquote type="cite">
      <p class="MsoNormal"><font size="2" color="navy" face="Arial"><span
            style="font-size:
            10.0pt;font-family:Arial;color:navy">By Acronym were you
            referring to the
            ontology abbreviation like MDR in case of MEDDRA? If yes, I
            guess it is not
            editable. Meaning probably we cannot generate it on my web
            application side and
            replace it on BioPortal. Also not sure if it can be used
            with web services.<o:p></o:p></span></font></p>
    </blockquote>
    Yes, acronym == abbreviation in this case. It is not editable unless
    the conditions above are met. However, if you administer an ontology
    or a Virtual Appliance then you can edit it. When we enable lookups
    using the abbreviation, we likely won't allow you to easily change
    the abbreviation once an ontology has been created in the system.<br>
    <br>
    <blockquote type="cite"><font size="2" face="Calibri"><span
          style="font-size:11.0pt;font-family:Calibri"></span></font><font
        size="2" color="navy" face="Arial"><span
          style="font-size:10.0pt;font-family:Arial;color:navy">Should
          this version have
          API key protection enabled on it? If not, is there any newer
          version of VM
          appliance released which has API key protection enabled?</span></font></blockquote>
    Version .2 does not have API Key protection enabled, this started in
    version .3. We'll be releasing a new NCBO Virtual Appliance version
    in the coming weeks, I would recommend waiting until that is out
    before you decide to upgrade.<br>
    <br>
    Paul R Alexander<br>
    Web / UI Developer<br>
    NCBO BioPortal<br>
    Stanford Center for Biomedical Informatics Research<br>
    <br>
    <br>
    On 1/26/12 8:56 AM, Pradnya Gawade wrote:
    <blockquote
cite="mid:110BCBFD7726F24EADA4275534BF28B602143787@anaconda.isovera.local"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 11 (filtered
        medium)">
      <!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:smarttagtype
        namespaceuri="urn:schemas-microsoft-com:office:smarttags"
        name="PlaceType">
        <o:smarttagtype
          namespaceuri="urn:schemas-microsoft-com:office:smarttags"
          name="PlaceName">
          <o:smarttagtype
            namespaceuri="urn:schemas-microsoft-com:office:smarttags"
            name="place">
            <!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
            <style>
<!--
 /* Font Definitions */
 @font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 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";
        color:black;}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline;}
pre
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";
        color:black;}
span.EmailStyle17
        {mso-style-type:personal;
        font-family:Arial;
        color:windowtext;}
span.EmailStyle19
        {mso-style-type:personal-reply;
        font-family:Arial;
        color:navy;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
        {page:Section1;}
 /* List Definitions */
 @list l0
        {mso-list-id:110706228;
        mso-list-template-ids:1072097876;}
@list l1
        {mso-list-id:615252520;
        mso-list-template-ids:-1168460002;}
@list l1:level1
        {mso-level-start-at:2;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l2
        {mso-list-id:812285522;
        mso-list-type:hybrid;
        mso-list-template-ids:2067845478 -2006651366 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l2:level1
        {mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l2:level2
        {mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l2:level3
        {mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l2:level4
        {mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l2:level5
        {mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l2:level6
        {mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l2:level7
        {mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l2:level8
        {mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l2:level9
        {mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l3
        {mso-list-id:1463693974;
        mso-list-template-ids:-390170368;}
@list l4
        {mso-list-id:1503815588;
        mso-list-template-ids:2044485360;}
@list l4:level1
        {mso-level-start-at:2;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
-->
</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]-->
            <div class="Section1">
              <p class="MsoNormal"><font size="2" color="navy"
                  face="Arial"><span style="font-size:
                    10.0pt;font-family:Arial;color:navy">Hi Paul,<o:p></o:p></span></font></p>
              <p class="MsoNormal"><font size="2" color="navy"
                  face="Arial"><span style="font-size:
                    10.0pt;font-family:Arial;color:navy"><o:p> </o:p></span></font></p>
              <p class="MsoNormal"><font size="2" color="navy"
                  face="Arial"><span style="font-size:
                    10.0pt;font-family:Arial;color:navy">Thank you for
                    your reply.<o:p></o:p></span></font></p>
              <p class="MsoNormal"><font size="2" color="navy"
                  face="Arial"><span style="font-size:
                    10.0pt;font-family:Arial;color:navy"><o:p> </o:p></span></font></p>
              <p class="MsoNormal"><font size="2" color="navy"
                  face="Arial"><span style="font-size:
                    10.0pt;font-family:Arial;color:navy">About the
                    identifiers, where do I see the
                    acronym for an ontology? Can I use it with REST web
                    services in place of
                    ontology id and ontology version id? From your
                    answer it seems is should be
                    editable, is that correct?<o:p></o:p></span></font></p>
              <p class="MsoNormal"><font size="2" color="navy"
                  face="Arial"><span style="font-size:
                    10.0pt;font-family:Arial;color:navy"><o:p> </o:p></span></font></p>
              <p class="MsoNormal"><font size="2" color="navy"
                  face="Arial"><span style="font-size:
                    10.0pt;font-family:Arial;color:navy">About the API
                    key enabling, I do not know
                    which version of BioPortal we are using on VM
                    appliance? How can I know the
                    version? I tried to explore the software for it but
                    did not get the answer. I
                    had downloaded it from </span></font><font size="2"
                  face="Calibri"><span
                    style="font-size:11.0pt;font-family:Calibri"><a
                      moz-do-not-send="true"
href="http://www.bioontology.org/ncbo-appliance/ncbo-appliance-v0.2.ova%20on%207/13/11"><font
                        size="2" color="navy" face="Arial"><span
                          style="font-size:10.0pt;font-family:Arial;
                          color:navy;text-decoration:none">http://www.bioontology.org/ncbo-appliance/ncbo-appliance-v0.2.ova
on
                          7/13/11</span></font></a>. </span></font><font
                  size="2" color="navy" face="Arial"><span
                    style="font-size:10.0pt;font-family:Arial;color:navy">Should
                    this version have
                    API key protection enabled on it? If not, is there
                    any newer version of VM
                    appliance released which has API key protection
                    enabled?<o:p></o:p></span></font></p>
              <p class="MsoNormal"><font size="2" color="navy"
                  face="Arial"><span style="font-size:
                    10.0pt;font-family:Arial;color:navy"><o:p> </o:p></span></font></p>
              <p class="MsoNormal"><font size="2" color="navy"
                  face="Arial"><span style="font-size:
                    10.0pt;font-family:Arial;color:navy">Thank you,<o:p></o:p></span></font></p>
              <p class="MsoNormal"><font size="2" color="navy"
                  face="Arial"><span style="font-size:
                    10.0pt;font-family:Arial;color:navy">Pradnya<o:p></o:p></span></font></p>
              <p class="MsoNormal"><font size="2" color="navy"
                  face="Arial"><span style="font-size:
                    10.0pt;font-family:Arial;color:navy"><o:p> </o:p></span></font></p>
              <div>
                <div class="MsoNormal" style="text-align:center"
                  align="center"><font size="3" color="black"
                    face="Times New Roman"><span
                      style="font-size:12.0pt;color:windowtext">
                      <hr tabindex="-1" size="2" width="100%"
                        align="center">
                    </span></font></div>
                <p class="MsoNormal"><b><font size="2" color="black"
                      face="Tahoma"><span
style="font-size:10.0pt;font-family:Tahoma;color:windowtext;font-weight:bold">From:</span></font></b><font
                    size="2" color="black" face="Tahoma"><span
                      style="font-size:10.0pt;font-family:Tahoma;
                      color:windowtext"> Paul R Alexander
                      [<a class="moz-txt-link-freetext" href="mailto:palexander@stanford.edu">mailto:palexander@stanford.edu</a>] <br>
                      <b><span style="font-weight:bold">Sent:</span></b>
                      Wednesday, January 25, 2012
                      7:09 PM<br>
                      <b><span style="font-weight:bold">To:</span></b>
                      Pradnya Gawade<br>
                      <b><span style="font-weight:bold">Cc:</span></b>
                      <a class="moz-txt-link-abbreviated" href="mailto:bioontology-support@lists.stanford.edu">bioontology-support@lists.stanford.edu</a><br>
                      <b><span style="font-weight:bold">Subject:</span></b>
                      Re: [bioontology-support]
                      Ontology identifiers, API key</span></font><font
                    color="black"><span style="color:windowtext"><o:p></o:p></span></font></p>
              </div>
              <p class="MsoNormal"><font size="3" color="black"
                  face="Times New Roman"><span style="font-size:12.0pt"><o:p> </o:p></span></font></p>
              <p class="MsoNormal"><font size="3" color="black"
                  face="Times New Roman"><span style="font-size:12.0pt">Pradnya,<br>
                    <br>
                    <o:p></o:p></span></font></p>
              <ol start="1" type="1">
                <li class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
                  mso-list:l0 level1 lfo1"><font size="2" color="black"
                    face="Arial"><span
                      style="font-size:10.0pt;font-family:Arial">I see
                      that some of the bioportal REST web services need
                      ontology id and some need ontology version id as
                      parameter depending on what they serve. I am using
                      my own instance of bioportal  and as far as I
                      understand when we upload a new ontology, both
                      these identifiers are generated by bioportal and
                      we cannot edit them.<u1:p></u1:p></span></font><o:p></o:p></li>
              </ol>
              <p class="MsoNormal"><font size="3" color="black"
                  face="Times New Roman"><span style="font-size:12.0pt">Correct,
                    these identifiers are generated. However, you
                    can use the acronym as a consistent identifier.<br>
                    <br>
                    <br>
                    <o:p></o:p></span></font></p>
              <ol start="2" type="1">
                <li class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
                  mso-list:l1 level1 lfo2"><font size="2" color="black"
                    face="Arial"><span
                      style="font-size:10.0pt;font-family:Arial">How to
                      enable API key on bioportal VM image? With the VM
                      image we have presently, I can access the REST web
                      services without providing any API key, so I
                      believe I will have to enable the API key
                      protection explicitly. <u1:p></u1:p></span></font><o:p></o:p></li>
              </ol>
              <p class="MsoNormal"><font size="3" color="black"
                  face="Times New Roman"><span style="font-size:12.0pt">These
                    cannot be enabled or disabled as it is a
                    fundamental change to the NCBO codebase. If you're
                    running an older NCBO
                    Virtual Appliance image then you will not have them
                    while the newer ones do.<br>
                    <br>
                    Paul R Alexander<br>
                    Web / UI Developer<br>
                    NCBO BioPortal<br>
                    <st1:place w:st="on"><st1:placename w:st="on">Stanford</st1:placename>
                      <st1:placetype w:st="on">Center</st1:placetype></st1:place>
                    for Biomedical Informatics
                    Research<br>
                    <br>
                    <br>
                    On 1/24/12 11:13 AM, Pradnya Gawade wrote: <o:p></o:p></span></font></p>
              <p class="MsoNormal"><font size="2" color="black"
                  face="Arial"><span style="font-size:
                    10.0pt;font-family:Arial">Hi Trish,<u1:p></u1:p></span></font><o:p></o:p></p>
              <p class="MsoNormal"><font size="2" color="black"
                  face="Arial"><span style="font-size:
                    10.0pt;font-family:Arial"><u1:p> </u1:p></span></font><o:p></o:p></p>
              <p class="MsoNormal"><font size="2" color="black"
                  face="Arial"><span style="font-size:
                    10.0pt;font-family:Arial">Few questions for you or
                    any body else on the list to
                    answer. Thanks in advance.<br>
                    <br>
                    <br>
                  </span></font><o:p></o:p></p>
              <u1:p></u1:p>
              <ol style="margin-top:0in" start="1" type="1">
                <li class="MsoNormal" style="mso-list:l2 level1 lfo5"><font
                    size="2" color="black" face="Arial"><span
                      style="font-size:10.0pt;font-family:Arial">I see
                      that some of the bioportal REST web services need
                      ontology id and some need ontology version id as
                      parameter depending on what they serve. I am using
                      my own instance of bioportal  and as far as I
                      understand when we upload a new ontology, both
                      these identifiers are generated by bioportal and
                      we cannot edit them.<u1:p></u1:p></span></font><o:p></o:p></li>
              </ol>
              <p class="MsoNormal" style="margin-left:.5in"><font
                  size="2" color="black" face="Arial"><span
                    style="font-size:10.0pt;font-family:Arial">For the
                    integration
                    of my web application with bioportal, we wanted to
                    maintain the generation of
                    dictionary identifier (we call them as dictionary
                    oid) on my web application
                    side. Is it possible to accomplish this with
                    bioportal? <u1:p></u1:p></span></font><o:p></o:p></p>
              <p class="MsoNormal" style="margin-left:.5in"><font
                  size="2" color="black" face="Arial"><span
                    style="font-size:10.0pt;font-family:Arial">Just FYI
                    here that
                    we are going to maintain every individual dictionary
                    version as its own
                    separate dictionary for bioportal (called “private”
                    ontology
                    supported in bioportal 3.4).<u1:p></u1:p></span></font><o:p></o:p></p>
              <p class="MsoNormal"><font size="2" color="black"
                  face="Arial"><span style="font-size:
                    10.0pt;font-family:Arial"><u1:p> </u1:p></span></font><o:p></o:p></p>
              <ol style="margin-top:0in" start="2" type="1">
                <li class="MsoNormal" style="mso-list:l2 level1 lfo5"><font
                    size="2" color="black" face="Arial"><span
                      style="font-size:10.0pt;font-family:Arial">How to
                      enable API key on bioportal VM image? With the VM
                      image we have presently, I can access the REST web
                      services without providing any API key, so I
                      believe I will have to enable the API key
                      protection explicitly. <u1:p></u1:p></span></font><o:p></o:p></li>
              </ol>
              <p class="MsoNormal"><font size="2" color="black"
                  face="Arial"><span style="font-size:
                    10.0pt;font-family:Arial"><u1:p> </u1:p></span></font><o:p></o:p></p>
              <p class="MsoNormal"><font size="2" color="black"
                  face="Arial"><span style="font-size:
                    10.0pt;font-family:Arial">Thank you,<u1:p></u1:p></span></font><o:p></o:p></p>
              <p class="MsoNormal"><font size="2" color="black"
                  face="Arial"><span style="font-size:
                    10.0pt;font-family:Arial">Pradnya<u1:p></u1:p></span></font><o:p></o:p></p>
              <p class="MsoNormal"><font size="3" color="black"
                  face="Times New Roman"><span style="font-size:12.0pt"><br>
                    <br>
                    <br>
                  </span></font></p>
              <fieldset class="mimeAttachmentHeader"></fieldset>
              <font size="3" color="black" face="Times New Roman"><o:p></o:p></font>
              <pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt">_______________________________________________<o:p></o:p></span></font></pre>
              <pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt">bioontology-support mailing list<o:p></o:p></span></font></pre>
              <pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt"><a moz-do-not-send="true" href="mailto:bioontology-support@lists.stanford.edu">bioontology-support@lists.stanford.edu</a><o:p></o:p></span></font></pre>
              <pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt"><a moz-do-not-send="true" href="https://mailman.stanford.edu/mailman/listinfo/bioontology-support">https://mailman.stanford.edu/mailman/listinfo/bioontology-support</a><o:p></o:p></span></font></pre>
            </div>
          </o:smarttagtype></o:smarttagtype></o:smarttagtype></blockquote>
  </body>
</html>