son)
09/26/2006 12:09 PM
To
Dan Connolly <[EMAIL PROTECTED]>
cc
Sean Martin/Cambridge/[EMAIL PROTECTED],
public-semweb-lifesci@w3.org, Alan Ruttenberg <[EMAIL PROTECTED]>,
Noah Mendelsohn/Cambridge/[EMAIL PROTECTED]
Subject
Re: LSID lookup details:
help?
-BEGI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31 July 2006, Dan Connolly wrote:
> In today's call, I learned a bit about how LSID lookup
> works:
>
> (1) try to find an SRV record using the domain in the LSID
> (2) fall back to a DDDS lookup and NAPTR and such
>
> Option (2) depends on some
Ben Szekely
IBM Software Engineer
Advanced Internet Technology, Cambridge, MA
[EMAIL PROTECTED]
[EMAIL PROTECTED] wrote on 07/31/2006
10:57:30 PM:
>
> On Mon, 2006-07-31 at 15:27 -0400, [EMAIL PROTECTED] wrote:
> > dan,
> >
> > I recall reading that the PDB Resolver is offline pending
> > upg
On Mon, 2006-07-31 at 15:27 -0400, [EMAIL PROTECTED] wrote:
> dan,
>
> I recall reading that the PDB Resolver is offline pending
> upgrades.
Ah... so 404 happens in the LSID world too. :)
Wait... isn't this exactly the case where the software
is supposed to fall back to DDNS/NAPTR stuff? Is th
On Mon, 2006-07-31 at 15:15 -0400, Benjamin H Szekely wrote:
>
> Perhaps try one of the following LSIDs
>
> urn:lsid:gdb.org:GenomicSegment:GDB132938
> urn:lsid:ncbi.nlm.nih.gov.lsid.biopathways.org:pubmed:12441807
OK, yes, those seem to work. Thanks.
--
Dan Connolly, W3C http://www.w3.or
dan,
I recall reading that the PDB Resolver is offline pending
upgrades.
You might try urn:lsid:gdb.org:GenomicSegment:GDB132938
which does work with the BioPathways Resolver:
http://lsid.biopathways.org/resolver/urn:lsid:gdb.org:Genom
icSegment:GDB132938
jb
Quoting Dan Connolly <[EMAIL P
Perhaps try one of the following LSIDs
urn:lsid:gdb.org:GenomicSegment:GDB132938
urn:lsid:ncbi.nlm.nih.gov.lsid.biopathways.org:pubmed:12441807
- Ben
Ben Szekely
IBM Software Engineer
Advanced Internet Technology, Cambridge, MA
[EMAIL PROTECTED]
[EMAIL PROTECTED] wrote on 07/31/2006
01:34:31 P
Based on some quick research Steve Evanchik
did at the lab here...
"The domain rcsb.org periodically
doesn't resolve correctly on my machine:
$ nslookup.exe rcsb.org
Server: somdns01.srv.ibm.com
Address: 9.0.5.1
Name: rcsb.org
and from my Linux machine:
[EMAIL PROTECTED]:~> nslookup rc
In today's call, I learned a bit about how LSID lookup
works:
(1) try to find an SRV record using the domain in the LSID
(2) fall back to a DDDS lookup and NAPTR and such
Option (2) depends on some NAPTR stuff in the "arpa" parts
of DNS space that OMG is expected to install but hasn't
gotten a
