ords, somebody else hosts the facility to
make statements, but these could be linked via bioguids. For example,
an obvious lightweight way to do this would be to use blogs as
annotation tools, and have the blog entry contain a link to the bioguid.
Can you see any points for making http://
Dear Matt,
I was wondering what the rules are for creating the actual identifier
that bioGUID would end up using to reference this database record.
The rules, such as they are, are in my previous post.
I'm not sure. There seem to be various adventures of GO in RDF around
the pla
On 3/30/07, Roderic Page <[EMAIL PROTECTED]> wrote:
Dear Matt,
> Do you have any publications that outline the motivation here (except
> the LSIDs don't work for the semantic web argument you have outlined
> in your online material)?
No publication as yet on bioGUID, but
Dear Matt,
Do you have any publications that outline the motivation here (except
the LSIDs don't work for the semantic web argument you have outlined
in your online material)?
No publication as yet on bioGUID, but I'm working on some rough notes.
In essence the motivation
Hi Roderic.
Do you have any publications that outline the motivation here (except
the LSIDs don't work for the semantic web argument you have outlined
in your online material)?
What are the rules for generating a URI for a particular database
record? For example:
http://bioguid.info/rdf/GO:0003
I've put together a web site called http://bioguid.info which, rather
grandly, is an attempt to bootstrap the biodiversity Semantic Web by
providing resolvable URIs for biological objects, such as publications,
taxonomic names, nucleotide sequences, and specimens.
These URIs (or "GUIDs")
