The latest release of the UniProt protein database contains just over a
billion triples*! PRESS RELEASE :-)
The data is all available via the (Semantic or otherwise) Web:
http://beta.uniprot.org/
...or can be bulk-downloaded from:
ftp://ftp.uniprot.org/
* Counting some reification sta
OK, thanks to your stimulus I've reworked the recommendations to be
more clear about what I mean by a URI Note recommendations document.
I've tried to provide more motivation and examples of answers to each
question. I always omit something important when I do things like
this, so please
I have made some progress with the conversion of the PDSP Ki database
(containing quantitative information about ligand-receptor interactions with a
focus on neuroscience).
Ontology URL:
http://purl.org/ycmi/ki/core.owl
Associated Wiki page:
http://esw.w3.org/topic/HCLSIG_BioRDF_Subgroup/Data/
Hi,
I'm one of Bio2RDF maintainer. While we still strongly believe in HTTP
URI with a REST nomenclature and a GET retrieval, we also believe that
some kind of standardization about how URIs should be created would be
beneficial for the health care and life science domain. These
recommendations ar
First let me thank you for taking a serious look at the requirements.
I appreciate it.
On Oct 21, 2007, at 7:44 PM, Peter Ansell wrote:
Hi all,
I have been using the Bio2Rdf markup system and I personally do not
see what all the fuss is about but there must be something so here are
my opin
Peter Ansell wrote:
Not sure what the difficulties are here.
Agreeing on what the best practices are -- if any? :-)
Everyone has their "personally, I would stick with x"s. I think the idea
was to document the arguments (any maybe even reach some conclusions), in
order to avoid repetitive di
