Our plan in the very near future is to record PURLs such as these (and other URIs) to provide a URI interconversion service through identifiers.org URIs. In general, at the moment, we tend to record primarily the final resolving locations.
We are sorry that your request did not return any expected result. Here is a list of possible reasons:
Your requested term has been deprecated
The ontology that contains the term has not been updated
Whoops! Our program has an unhandled and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if you have any further questions.
cheers,
Nick
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Looks like there is a problem with OntoBee - Oliver can you fix?
If identifiers.org points at the PURL we can start to get an exact
number for the % uptime which would be useful for us.
Nick, I would prefer the PURL was registered as that way I don't have to
change things twice if we end up using a different resolver
On 22 Apr 2014, at 3:50, Nick Juty wrote:
Hi Chris,
Thanks for your query.
Our plan in the very near future is to record PURLs such as these (and
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated
The ontology that contains the term has not been updated
Whoops! Our program has an unhandled and unexpected error in
processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
The Ontobee virtuoso database was broken last midnight when it was trying to upload the newest version of GO and failed.
I have resumed it now. It should be fine now.
Thanks,
Oliver
-----Original Message-----
From: Chris Mungall [mailto:cjmungall@lbl.gov]
Sent: Tuesday, April 22, 2014 10:41 AM
To: [identifiers-org:new-collection]; He, Yongqun
Subject: Re: [identifiers-org:new-collection] #16 Uberon PURLs
Looks like there is a problem with OntoBee - Oliver can you fix?
If identifiers.org points at the PURL we can start to get an exact number for the % uptime which would be useful for us.
Nick, I would prefer the PURL was registered as that way I don't have to change things twice if we end up using a different resolver
On 22 Apr 2014, at 3:50, Nick Juty wrote:
Hi Chris,
Thanks for your query.
Our plan in the very near future is to record PURLs such as these (and
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Our plan in the very near future is to record PURLs such as these (and
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Our plan in the very near future is to record PURLs such as these (and
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Our plan in the very near future is to record PURLs such as these (and
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Our plan in the very near future is to record PURLs such as these (and
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Our plan in the very near future is to record PURLs such as these (and
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Our plan in the very near future is to record PURLs such as these (and
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Our plan in the very near future is to record PURLs such as these (and
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Our plan in the very near future is to record PURLs such as these (and
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Our plan in the very near future is to record PURLs such as these (and
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Our plan in the very near future is to record PURLs such as these (and
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Our plan in the very near future is to record PURLs such as these (and
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Our plan in the very near future is to record PURLs such as these (and
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Our plan in the very near future is to record PURLs such as these (and
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Our plan in the very near future is to record PURLs such as these (and
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
r plan in the very near future is to record PURLs such as these (and
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
lan in the very near future is to record PURLs such as these (and
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
in the very near future is to record PURLs such as these (and
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
the very near future is to record PURLs such as these (and
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
e very near future is to record PURLs such as these (and
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
ery near future is to record PURLs such as these (and
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
other URIs) to provide a URI interconversion service through
identifiers.org URIs. In general, at the moment, we tend to record
primarily the final resolving locations.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
rary.org/obo/UBERON_0007225,
which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
We are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
e are sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
re sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
sorry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
ry that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
that your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
t your request did not return any expected result.
Here is a list of possible reasons:
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Your requested term has been deprecated The ontology that contains
the term has not been updated Whoops! Our program has an unhandled
and unexpected error in processing your request."
I hope that clarifies things a little, but feel free to contact us if
you have any further questions.
Thanks for getting back to me, and to Oliver for fixing the OntoBee issue.
I was about to do as you requested, and add the OBO PURL for UBERON, but I have run into a problem; can you tell me if the official UBERON identifier derived from 'UBERON:' or 'UBERON_'? Right now we have OLS and BioPortal using a colon, and OntoBee using an underscore. The Registry entry has it listed with a colon. I guess as lead developer, you should have the final say.
I'd be grateful to hear any suggestions you may have that would assist us in getting your PURL listed.
cheers
Nick
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for getting back to me, and to Oliver for fixing the OntoBee
issue.
I was about to do as you requested, and add the OBO PURL for UBERON,
but I have run into a problem; can you tell me if the official UBERON
identifier derived from 'UBERON:' or 'UBERON_'? Right now we have OLS
and BioPortal using a colon, and OntoBee using an underscore. The
Registry entry has it listed with a colon. I guess as lead developer,
you should have the final say.
I'd be grateful to hear any suggestions you may have that would assist
us in getting your PURL listed.
Thanks for getting back to me. I've seen that documentation, but
unfortunately it does not really help me. I can add UBERON with
identifiers using 'UBERON:', which will work for OLS and BioPortal
instances, but not for you. Or vice versa, if I add the underscore
version, they will work for only you.
Is there any chance that you could implement something that can handle the
colon version on your side?
Thanks for getting back to me, and to Oliver for fixing the OntoBee
issue.
I was about to do as you requested, and add the OBO PURL for UBERON,
but I have run into a problem; can you tell me if the official UBERON
identifier derived from 'UBERON:' or 'UBERON_'? Right now we have OLS
and BioPortal using a colon, and OntoBee using an underscore. The
Registry entry has it listed with a colon. I guess as lead developer,
you should have the final say.
I'd be grateful to hear any suggestions you may have that would assist
us in getting your PURL listed.
In this case, I am wondering if you can make some mapping or other update in your site to make it fit to the two scenarios.
Best,
Oliver
From: Nick Juty [mailto:njuty@users.sf.net]
Sent: Saturday, April 26, 2014 7:53 PM
To: [identifiers-org:new-collection]
Subject: [identifiers-org:new-collection] Re: #16 Uberon PURLs
Hi Chris,
Thanks for getting back to me. I've seen that documentation, but
unfortunately it does not really help me. I can add UBERON with
identifiers using 'UBERON:', which will work for OLS and BioPortal
instances, but not for you. Or vice versa, if I add the underscore
version, they will work for only you.
Is there any chance that you could implement something that can handle the
colon version on your side?
Thanks for getting back to me, and to Oliver for fixing the OntoBee
issue.
I was about to do as you requested, and add the OBO PURL for UBERON,
but I have run into a problem; can you tell me if the official UBERON
identifier derived from 'UBERON:' or 'UBERON_'? Right now we have OLS
and BioPortal using a colon, and OntoBee using an underscore. The
Registry entry has it listed with a colon. I guess as lead developer,
you should have the final say.
I'd be grateful to hear any suggestions you may have that would assist
us in getting your PURL listed.
Hi Chris,
Thanks for your query.
Our plan in the very near future is to record PURLs such as these (and other URIs) to provide a URI interconversion service through identifiers.org URIs. In general, at the moment, we tend to record primarily the final resolving locations.
The other thing, that I have found this on a fairly frequent basis, is that your URL does not work. It gets redirected to http://www.ontobee.org/browser/rdf.php?o=UBERON&iri=http://purl.obolibrary.org/obo/UBERON_0007225, which gives the message:
"Term Not Found
We are sorry that your request did not return any expected result. Here is a list of possible reasons:
I hope that clarifies things a little, but feel free to contact us if you have any further questions.
cheers,
Nick
Looks like there is a problem with OntoBee - Oliver can you fix?
If identifiers.org points at the PURL we can start to get an exact
number for the % uptime which would be useful for us.
Nick, I would prefer the PURL was registered as that way I don't have to
change things twice if we end up using a different resolver
On 22 Apr 2014, at 3:50, Nick Juty wrote:
Related
Request new collection: #16
The Ontobee virtuoso database was broken last midnight when it was trying to upload the newest version of GO and failed.
I have resumed it now. It should be fine now.
Thanks,
Oliver
-----Original Message-----
From: Chris Mungall [mailto:cjmungall@lbl.gov]
Sent: Tuesday, April 22, 2014 10:41 AM
To: [identifiers-org:new-collection]; He, Yongqun
Subject: Re: [identifiers-org:new-collection] #16 Uberon PURLs
Looks like there is a problem with OntoBee - Oliver can you fix?
If identifiers.org points at the PURL we can start to get an exact number for the % uptime which would be useful for us.
Nick, I would prefer the PURL was registered as that way I don't have to change things twice if we end up using a different resolver
On 22 Apr 2014, at 3:50, Nick Juty wrote:
i Chris,
hris,
s,
Thanks for your query.
anks for your query.
s for your query.
or your query.
your query.
r query.
uery.
y.
Our plan in the very near future is to record PURLs such as these (and
r plan in the very near future is to record PURLs such as these (and
lan in the very near future is to record PURLs such as these (and
in the very near future is to record PURLs such as these (and
the very near future is to record PURLs such as these (and
e very near future is to record PURLs such as these (and
ery near future is to record PURLs such as these (and
near future is to record PURLs such as these (and
ar future is to record PURLs such as these (and
future is to record PURLs such as these (and
ure is to record PURLs such as these (and
is to record PURLs such as these (and
to record PURLs such as these (and
record PURLs such as these (and
cord PURLs such as these (and
d PURLs such as these (and
URLs such as these (and
s such as these (and
uch as these (and
as these (and
these (and
ese (and
(and
nd
ther URIs) to provide a URI interconversion service through
r URIs) to provide a URI interconversion service through
RIs) to provide a URI interconversion service through
) to provide a URI interconversion service through
o provide a URI interconversion service through
rovide a URI interconversion service through
ide a URI interconversion service through
a URI interconversion service through
URI interconversion service through
interconversion service through
terconversion service through
conversion service through
version service through
sion service through
n service through
ervice through
ice through
through
rough
gh
dentifiers.org URIs. In general, at the moment, we tend to record
tifiers.org URIs. In general, at the moment, we tend to record
iers.org URIs. In general, at the moment, we tend to record
s.org URIs. In general, at the moment, we tend to record
rg URIs. In general, at the moment, we tend to record
URIs. In general, at the moment, we tend to record
s. In general, at the moment, we tend to record
In general, at the moment, we tend to record
general, at the moment, we tend to record
eral, at the moment, we tend to record
l, at the moment, we tend to record
at the moment, we tend to record
the moment, we tend to record
moment, we tend to record
ment, we tend to record
t, we tend to record
we tend to record
tend to record
d to record
o record
ecord
rd
rimarily the final resolving locations.
arily the final resolving locations.
ly the final resolving locations.
the final resolving locations.
final resolving locations.
nal resolving locations.
resolving locations.
solving locations.
ving locations.
g locations.
ocations.
tions.
ns.
The other thing, that I have found this on a fairly frequent basis, is
e other thing, that I have found this on a fairly frequent basis, is
ther thing, that I have found this on a fairly frequent basis, is
r thing, that I have found this on a fairly frequent basis, is
hing, that I have found this on a fairly frequent basis, is
g, that I have found this on a fairly frequent basis, is
that I have found this on a fairly frequent basis, is
t I have found this on a fairly frequent basis, is
have found this on a fairly frequent basis, is
ve found this on a fairly frequent basis, is
found this on a fairly frequent basis, is
nd this on a fairly frequent basis, is
this on a fairly frequent basis, is
s on a fairly frequent basis, is
n a fairly frequent basis, is
fairly frequent basis, is
irly frequent basis, is
y frequent basis, is
requent basis, is
uent basis, is
t basis, is
asis, is
s, is
is
hat your URL does not work. It gets redirected to
your URL does not work. It gets redirected to
ur URL does not work. It gets redirected to
URL does not work. It gets redirected to
does not work. It gets redirected to
es not work. It gets redirected to
not work. It gets redirected to
work. It gets redirected to
rk. It gets redirected to
It gets redirected to
gets redirected to
ts redirected to
redirected to
irected to
cted to
d to
o
ttp://www.ontobee.org/browser/rdf.php?o=UBERON&iri=http://purl.obolib
://www.ontobee.org/browser/rdf.php?o=UBERON&iri=http://purl.obolib
www.ontobee.org/browser/rdf.php?o=UBERON&iri=http://purl.obolib
.ontobee.org/browser/rdf.php?o=UBERON&iri=http://purl.obolib
tobee.org/browser/rdf.php?o=UBERON&iri=http://purl.obolib
ee.org/browser/rdf.php?o=UBERON&iri=http://purl.obolib
org/browser/rdf.php?o=UBERON&iri=http://purl.obolib
/browser/rdf.php?o=UBERON&iri=http://purl.obolib
owser/rdf.php?o=UBERON&iri=http://purl.obolib
er/rdf.php?o=UBERON&iri=http://purl.obolib
rdf.php?o=UBERON&iri=http://purl.obolib
.php?o=UBERON&iri=http://purl.obolib
p?o=UBERON&iri=http://purl.obolib
=UBERON&iri=http://purl.obolib
ERON&iri=http://purl.obolib
N&iri=http://purl.obolib
ri=http://purl.obolib
http://purl.obolib
p://purl.obolib
/purl.obolib
rl.obolib
obolib
lib
ary.org/obo/UBERON_0007225,
.org/obo/UBERON_0007225,
g/obo/UBERON_0007225,
bo/UBERON_0007225,
UBERON_0007225,
RON_0007225,
_0007225,
07225,
25,
hich gives the message:
h gives the message:
ives the message:
s the message:
he message:
message:
sage:
e:
"Term Not Found
erm Not Found
Not Found
t Found
ound
d
e are sorry that your request did not return any expected result.
re sorry that your request did not return any expected result.
sorry that your request did not return any expected result.
ry that your request did not return any expected result.
that your request did not return any expected result.
t your request did not return any expected result.
our request did not return any expected result.
request did not return any expected result.
quest did not return any expected result.
st did not return any expected result.
did not return any expected result.
not return any expected result.
t return any expected result.
eturn any expected result.
rn any expected result.
any expected result.
expected result.
pected result.
ted result.
result.
sult.
t.
ere is a list of possible reasons:
is a list of possible reasons:
a list of possible reasons:
list of possible reasons:
t of possible reasons:
f possible reasons:
ossible reasons:
ible reasons:
e reasons:
easons:
ons:
:
Your requested term has been deprecated The ontology that contains
r requested term has been deprecated The ontology that contains
equested term has been deprecated The ontology that contains
ested term has been deprecated The ontology that contains
ed term has been deprecated The ontology that contains
term has been deprecated The ontology that contains
m has been deprecated The ontology that contains
as been deprecated The ontology that contains
been deprecated The ontology that contains
n deprecated The ontology that contains
eprecated The ontology that contains
ecated The ontology that contains
ted The ontology that contains
The ontology that contains
he ontology that contains
ontology that contains
ology that contains
gy that contains
that contains
t contains
ontains
ains
s
he term has not been updated Whoops! Our program has an unhandled
term has not been updated Whoops! Our program has an unhandled
m has not been updated Whoops! Our program has an unhandled
as not been updated Whoops! Our program has an unhandled
not been updated Whoops! Our program has an unhandled
been updated Whoops! Our program has an unhandled
en updated Whoops! Our program has an unhandled
updated Whoops! Our program has an unhandled
ated Whoops! Our program has an unhandled
d Whoops! Our program has an unhandled
Whoops! Our program has an unhandled
ops! Our program has an unhandled
! Our program has an unhandled
ur program has an unhandled
program has an unhandled
gram has an unhandled
m has an unhandled
as an unhandled
an unhandled
unhandled
andled
led
nd unexpected error in processing your request."
unexpected error in processing your request."
xpected error in processing your request."
cted error in processing your request."
d error in processing your request."
rror in processing your request."
r in processing your request."
n processing your request."
rocessing your request."
essing your request."
ing your request."
your request."
ur request."
request."
uest."
t."
I hope that clarifies things a little, but feel free to contact us if
hope that clarifies things a little, but feel free to contact us if
e that clarifies things a little, but feel free to contact us if
hat clarifies things a little, but feel free to contact us if
clarifies things a little, but feel free to contact us if
arifies things a little, but feel free to contact us if
fies things a little, but feel free to contact us if
s things a little, but feel free to contact us if
hings a little, but feel free to contact us if
gs a little, but feel free to contact us if
a little, but feel free to contact us if
ittle, but feel free to contact us if
le, but feel free to contact us if
but feel free to contact us if
t feel free to contact us if
eel free to contact us if
free to contact us if
ee to contact us if
to contact us if
contact us if
tact us if
t us if
s if
f
ou have any further questions.
have any further questions.
e any further questions.
ny further questions.
further questions.
ther questions.
r questions.
uestions.
tions.
ns.
cheers,
eers,
s,
Nick
ck
--
[new-collection:#16] Uberon PURLs
[new-collection:#16] Uberon PURLs**
ew-collection:#16] Uberon PURLs**
collection:#16] Uberon PURLs**
lection:#16] Uberon PURLs**
tion:#16] Uberon PURLs**
n:#16] Uberon PURLs**
16] Uberon PURLs**
Uberon PURLs**
eron PURLs**
n PURLs**
URLs**
s**
Status: open
Status:** open
tus:** open
:** open
open
en
*Created: Mon Apr 21, 2014 11:07 PM UTC by Chris Mungall Last
eated: Mon Apr 21, 2014 11:07 PM UTC by Chris Mungall Last
ed: Mon Apr 21, 2014 11:07 PM UTC by Chris Mungall Last
Mon Apr 21, 2014 11:07 PM UTC by Chris Mungall Last
Mon Apr 21, 2014 11:07 PM UTC by Chris Mungall **Last
Apr 21, 2014 11:07 PM UTC by Chris Mungall **Last
r 21, 2014 11:07 PM UTC by Chris Mungall **Last
1, 2014 11:07 PM UTC by Chris Mungall **Last
2014 11:07 PM UTC by Chris Mungall **Last
4 11:07 PM UTC by Chris Mungall **Last
1:07 PM UTC by Chris Mungall **Last
7 PM UTC by Chris Mungall **Last
M UTC by Chris Mungall **Last
TC by Chris Mungall **Last
by Chris Mungall **Last
Chris Mungall **Last
is Mungall **Last
Mungall **Last
gall **Last
l **Last
*Last
st
pdated:** Mon Apr 21, 2014 11:07 PM UTC
ted:** Mon Apr 21, 2014 11:07 PM UTC
:** Mon Apr 21, 2014 11:07 PM UTC
Mon Apr 21, 2014 11:07 PM UTC
n Apr 21, 2014 11:07 PM UTC
pr 21, 2014 11:07 PM UTC
21, 2014 11:07 PM UTC
2014 11:07 PM UTC
14 11:07 PM UTC
11:07 PM UTC
07 PM UTC
PM UTC
UTC
Owner:* nobody
ner:** nobody
:** nobody
nobody
body
y
'm the lead developer of uberon
the lead developer of uberon
lead developer of uberon
ad developer of uberon
developer of uberon
eloper of uberon
per of uberon
of uberon
uberon
eron
n
hen I go here
I go here
go here
here
e
http://info.identifiers.org/uberon/UBERON:0007225
tp://info.identifiers.org/uberon/UBERON:0007225
//info.identifiers.org/uberon/UBERON:0007225
nfo.identifiers.org/uberon/UBERON:0007225
.identifiers.org/uberon/UBERON:0007225
entifiers.org/uberon/UBERON:0007225
ifiers.org/uberon/UBERON:0007225
ers.org/uberon/UBERON:0007225
.org/uberon/UBERON:0007225
g/uberon/UBERON:0007225
beron/UBERON:0007225
on/UBERON:0007225
UBERON:0007225
RON:0007225
:0007225
07225
25
I see links to OLS and BioPortal, but not to the official PURL,
see links to OLS and BioPortal, but not to the official PURL,
links to OLS and BioPortal, but not to the official PURL,
nks to OLS and BioPortal, but not to the official PURL,
to OLS and BioPortal, but not to the official PURL,
OLS and BioPortal, but not to the official PURL,
S and BioPortal, but not to the official PURL,
nd BioPortal, but not to the official PURL,
BioPortal, but not to the official PURL,
Portal, but not to the official PURL,
tal, but not to the official PURL,
, but not to the official PURL,
ut not to the official PURL,
not to the official PURL,
to the official PURL,
the official PURL,
e official PURL,
fficial PURL,
cial PURL,
l PURL,
URL,
,
http://purl.obolibrary.org/obo/UBERON_0007225
tp://purl.obolibrary.org/obo/UBERON_0007225
//purl.obolibrary.org/obo/UBERON_0007225
url.obolibrary.org/obo/UBERON_0007225
.obolibrary.org/obo/UBERON_0007225
olibrary.org/obo/UBERON_0007225
brary.org/obo/UBERON_0007225
ry.org/obo/UBERON_0007225
org/obo/UBERON_0007225
/obo/UBERON_0007225
o/UBERON_0007225
BERON_0007225
ON_0007225
0007225
7225
5
an you add this?
you add this?
add this?
d this?
his?
?
Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
Related
Request new collection: #16
Hi Chris,
Thanks for getting back to me, and to Oliver for fixing the OntoBee issue.
I was about to do as you requested, and add the OBO PURL for UBERON, but I have run into a problem; can you tell me if the official UBERON identifier derived from 'UBERON:' or 'UBERON_'? Right now we have OLS and BioPortal using a colon, and OntoBee using an underscore. The Registry entry has it listed with a colon. I guess as lead developer, you should have the final say.
I'd be grateful to hear any suggestions you may have that would assist us in getting your PURL listed.
cheers
Nick
Hi Nick,
See
http://oboformat.googlecode.com/svn/trunk/doc/obo-syntax.html
For how OBO identifiers are mapped to URIs
On 22 Apr 2014, at 8:56, Nick Juty wrote:
Related
Request new collection: #16
Hi Chris,
Thanks for getting back to me. I've seen that documentation, but
unfortunately it does not really help me. I can add UBERON with
identifiers using 'UBERON:', which will work for OLS and BioPortal
instances, but not for you. Or vice versa, if I add the underscore
version, they will work for only you.
Is there any chance that you could implement something that can handle the
colon version on your side?
cheers
Nick
Related
Request new collection: #16
Hi Nick,
In this case, I am wondering if you can make some mapping or other update in your site to make it fit to the two scenarios.
Best,
Oliver
From: Nick Juty [mailto:njuty@users.sf.net]
Sent: Saturday, April 26, 2014 7:53 PM
To: [identifiers-org:new-collection]
Subject: [identifiers-org:new-collection] Re: #16 Uberon PURLs
Hi Chris,
Thanks for getting back to me. I've seen that documentation, but
unfortunately it does not really help me. I can add UBERON with
identifiers using 'UBERON:', which will work for OLS and BioPortal
instances, but not for you. Or vice versa, if I add the underscore
version, they will work for only you.
Is there any chance that you could implement something that can handle the
colon version on your side?
cheers
Nick
Hi Nick,
See
http://oboformat.googlecode.com/svn/trunk/doc/obo-syntax.html
For how OBO identifiers are mapped to URIs
On 22 Apr 2014, at 8:56, Nick Juty wrote:
Hi Chris,
Thanks for getting back to me, and to Oliver for fixing the OntoBee
issue.
I was about to do as you requested, and add the OBO PURL for UBERON,
but I have run into a problem; can you tell me if the official UBERON
identifier derived from 'UBERON:' or 'UBERON_'? Right now we have OLS
and BioPortal using a colon, and OntoBee using an underscore. The
Registry entry has it listed with a colon. I guess as lead developer,
you should have the final say.
I'd be grateful to hear any suggestions you may have that would assist
us in getting your PURL listed.
cheers
Nick
[new-collection:#16]http://sourceforge.net/p/identifiers-org/new-collection/16/ Uberon PURLs
Status: open
Created: Mon Apr 21, 2014 11:07 PM UTC by Chris Mungall
Last Updated: Tue Apr 22, 2014 10:50 AM UTC
Owner: nobody
I'm the lead developer of uberon
When I go here
http://info.identifiers.org/uberon/UBERON:0007225
I see links to OLS and BioPortal, but not to the official PURL,
http://purl.obolibrary.org/obo/UBERON_0007225
Can you add this?
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/identifiers-org/new-collection/16/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
[new-collection:#16]http://sourceforge.net/p/identifiers-org/new-collection/16/ Uberon PURLs
Status: open
Created: Mon Apr 21, 2014 11:07 PM UTC by Chris Mungall
Last Updated: Tue Apr 22, 2014 10:50 AM UTC
Owner: nobody
I'm the lead developer of uberon
When I go here
http://info.identifiers.org/uberon/UBERON:0007225
I see links to OLS and BioPortal, but not to the official PURL,
http://purl.obolibrary.org/obo/UBERON_0007225
Can you add this?
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/identifiers-org/new-collection/16/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
[new-collection:#16]http://sourceforge.net/p/identifiers-org/new-collection/16/ Uberon PURLs
Status: open
Created: Mon Apr 21, 2014 11:07 PM UTC by Chris Mungall
Last Updated: Tue Apr 22, 2014 10:50 AM UTC
Owner: nobody
I'm the lead developer of uberon
When I go here
http://info.identifiers.org/uberon/UBERON:0007225
I see links to OLS and BioPortal, but not to the official PURL, http://purl.obolibrary.org/obo/UBERON_0007225
Can you add this?
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/identifiers-org/new-collection/16/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
Related
Request new collection: #16