Hello Bill,
[EMAIL PROTECTED] wrote on 01/22/2007 06:21:19 AM:
>
> William Bug wrote:
> > Also - for loading remote LSID resources:
> > It installed just fine, but when I try to access:
> > urn:lsid:uniprot.org:keywords:462
> >
> > I get an error back claiming "unknown protocol".
As Eric says
/wiki/Extensible_Resource_Identifier
=
--
Sean Martin
IBM Corp
NID registration status and asked about the OMG's intentions and
he reiterated his previous position that the OMG would register it and
asked me to work with various people there to get it done. So I am on the
hook.
Kindest regards, Sean
--
Sean Martin
IBM Corp
[EMAIL PROTECTED] (Henry
S. Thomp
ogram [2].
Kindest regards, Sean
[1] Minerva: A Scalable OWL Ontology
Storage and Inference System
http://apex.sjtu.edu.cn/apex_wiki/Papers?action="">
[2] IBM Integrated Ontology Development
Toolkit
http://www.alphaworks.ibm.com/tech/semanticstk
--
Sean Martin
IBM Corp
>
> Perhaps I'm misunderstanding the specific needs here, but I wonder
if
> authoritative identification of individuals is really an argument
for a
> ID-oriented naming convention - such as LSID.
>
With regard to identity, has anyone here had experiece
with I-names [1]. These are OASIS "human-
can be significantly eased &
enhanced by Semantic Web standards and technologies. This belief drives
much of our current work here. Thanks for putting this out there Lee!
http://www.thefigtrees.net/lee/blog/2006/08/life_sciences_on_the_web_with.html
Kindest regards, Sean
--
Sean Martin
IBM Corp
orithm for sharpening), that new image instance could be made
available as an LSID revision by incrementing the version area of the LSID
name.
Kindest regards, Sean
--
Sean Martin
IBM Corp.
vices like phones, PDAs and other thin clients. It would also make
the provision of a _javascript_ library for Web 2.0 style applications simple.
It is my belief that technically this can be added in a simple, non-disruptive
manner.
Kindest regards, Sean
--
Sean Martin
IBM Corp.
to go on doing so while we find it useful for our purposes. What
would be marvelous would be to start defining the scope of the metadata
returned so we can take the existing usefulness to the next level.
I will look forwards to talking with
you next week. Have a great weekend everyone.
Kindest regards, Sean
--
Sean Martin
IBM Corp
heme would additionally provide _stable_ global and
optionally local http URL access to all accessible LSID named data objects
and metadata along with possible performance benefits.
Little new programming & standards work would
be required.
Kindest regards, Sean
--
Sean Martin
IBM Corp
://lsid.biopathways.org/resolver/metadata/urn:lsid:ncbi.nlm.nih.gov.lsid.biopathways.org:genbank:30350027
for its metadata. Obviously you would replace "lsid.biopathways.org"
with whatever the Name Mapping Authority" domain name is.
--
Sean Martin
IBM Corp
t library coverage across the languages that are commonly used to
program Life Sciences applications, especially since the base libraries
(DNS, WWW, and Web Services) are already ubiquitous.
Kindest regards, Sean
--
Sean Martin
IBM Corp.
> absolutely agree that for your purposes you need
to take this very
> seriously, but using 'http' doesn't make this
any harder (or, of
> course, any easier).
>
I am not sure that I can agree with you on this point.
How does one go about differentiating between one http:// URI and another
programmatically for the purposes of knowing what its conventions are?
As opposed to using something else which only has one established convention?
Kindest regards, Sean
[1] http://www.omg.org/cgi-bin/doc?dtc/04-05-01
--
Sean Martin
IBM Corp.
blic/public-semweb-lifesci/2006Jul/0074.html
Kindest regards, Sean
Henry Story <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
07/24/2006 06:45 AM
To
Sean Martin/Cambridge/[EMAIL PROTECTED]
cc
public-semweb-lifesci@w3.org
Subject
Re: BioRDF: URI Best Practices
I too would
Hi Alan,
[EMAIL PROTECTED] wrote on 07/23/2006
11:51:35 PM:
>
> On Jul 21, 2006, at 2:53 PM, Sean Martin wrote:
>
> > XW> Should a LSID resolver decide not
to resolve a particular LSID,
> > wouldn't it
> > XW> be the same effect as a broken link?
>
> It seems to me that content negotiation is a pre-semantic web way
of
> handling a bit of semantics. Why not adopt a uniform way of handling
> these things? You could certainly support content negotiation
> discovered information by translating it to to the more expressive
> rdf/owl.
>
I c
s in our effort
but not the name.
>
Actually, LSIDs should never be allowed to represent
something else.. that is the point, have the right tools for the job as
opposed to everything looks a bit like a nail if you have a hammer ;-)
Kindest regards, Sean
--
Sean Martin
IBM Corp.
[1] http://web.archive.org/web/*/http://www.i3c.org
h less so. Of
course sometimes it is even hard to figure out what is actually current
too! Unfortunately repeatable science and of course legal obligations require
us to have decent answers here too, or am I missing something?
Kindest regards, Sean
--
Sean Martin
IBM Corp
them and so the various concerns may not be obvious
with just the one table suggested.
Kindest regards, Sean
--
Sean Martin
IBM Corp.
[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
07/19/2006 06:33 PM
To
"'public-semweb-lifesci'"
cc
Subject
BioRDF: URI Best Practic
ony of you playing the (extremely useful) part of devil's advocate
on this topic. I don’t know if you realize it, but my understanding is
that the original LSID was based on work at Millennium. ;-)
--
Sean Martin
IBM Corp.
area collaboration.
Kindest regards, Sean
--
Sean Martin
IBM Corp
on it, and who owns the hostname now) baggage surrounding
HTTP URLs as well as a number of technical short comings given
the communities requirements, it is not hard to see how the idea of a new
URN with its own specialized technical and social contracts provided a
fresh start and yet still mapped down onto existing internet infrastructure.
Kindest regards, Sean
--
Sean Martin
IBM Corp
Alyssa Wolf has just released a LSID
RDF Browser plug-in for Firefox. [1]
This x-platform Firefox plug-in is an
alternative to using a purely web based resolver, like the one at lsid.biopathways.org
[2].
Both are quite interesting to use against
the NCBI's Entrez search. See the "Try it now"
tml
[11] http://lsid.biopathways.org/resolver/
[12] http://lsid.biopathways.org/resolver/urn:lsid:ncbi.nlm.nih.gov.lsid.biopathways.org:pubmed:15153306
Have a great (and for some long) weekend.
Kindest regards, Sean
--
Sean Martin
IBM Corp
Cambridge, MA
t=Abstract&list_uids=15153306&query_hl=3&itool=pubmed_docsum
Kindest regards, Sean
---
Sean Martin
IBM Corp.
ge
the gap that separates authority name strings from service locations. From
what I recall, the URN specs specifically do not permit names and locations
to be confounded.
Kindest regards, Sean
--
Sean Martin
IBM Corp.
[EMAIL PROTECTED] wrote on 06/16/2006
12:59:12 PM:
>
> On Fri, 2006-06-16
take to
tie all possible legal RDF URIs (its just a name!) to a single end
point and transport protocol. Additionally it is extremely helpful
to have some obvious way to programmatically disambiguate between URIs
that offer different social/technical "contracts".
Kindest regards, Sean
tructured
text, html or
xml and are easily dereferenceable as the unique handles
to arbitarily large
RDF graphs and/or binary objects... ;-)
Kindest regards, Sean
--
Sean Martin
IBM Corp
meeting. There were a number
of people there who were interested in having these, so maybe this can
be the start. Thanks Eric!
Kindest regards, Sean
--
Sean Martin
IBM Corp
Eric Miller <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
02/08/2006 09:08 AM
To
Eric Jain <[EMAIL
29 matches
Mail list logo
