Re: [rdf] Re: proposal for standard NCBI database URI

2006-05-10 Thread Benjamin H Szekely
Hi Phil,       I'm not sure I understand why having a class DataBank makes this owl full, perhaps you could explain a bit more.  But in general, not much about these ontologies was deliberate so any discovered oversites like the potential one you pointed out are appreciated.   - Ben Phillip Lor

RE: [rdf] Re: proposal for standard NCBI database URI

2006-05-09 Thread Benjamin H Szekely
Hi All,   I'm new to this list and I only did a cursory reading of the archives so I apologize if I add anything that has already been addressed.  As some of you know, Stephen Evanchik and myself are the lead developers on the LSID Toolkit.  I have implemented a prototype LSID Resolution Service

Re: [rdf] Re: proposal for standard NCBI database URI

2006-05-09 Thread chris mungall
One other thing to bear in mind is that many of the IDs that are purported to be NCBI nucleotide sequence IDs are actually NCBI/EMBL/ DDBJ IDs. See http://www.insdc.org/ Presumably the ID scheme should reflect this?

Re: [rdf] Re: proposal for standard NCBI database URI

2006-05-09 Thread Larry Hunter
On Tue, 2006-05-09 at 10:12 -0700, Mark Wilkinson wrote: > Are there limits on the number of retrievals that can be done in a day > on these URLs? i.e. will my domain get blacklisted if I pull in 100K > records every hour? Yes. Here are the rules: http://eutils.ncbi.nlm.nih.gov/entrez/query/s

Re: [rdf] Re: proposal for standard NCBI database URI

2006-05-09 Thread Alf Eaton
On 09 May 2006, at 13:12, Mark Wilkinson wrote: I stand corrected :-) Are there limits on the number of retrievals that can be done in a day on these URLs? i.e. will my domain get blacklisted if I pull in 100K records every hour? # Run retrieval scripts on weekends or between 9 pm and 5 am

Re: [rdf] Re: proposal for standard NCBI database URI

2006-05-09 Thread Alan Ruttenberg
Thanks, I like this proposal, Larry. You are right - it works now and satisfies the requirement. I amend my proposal to be: http://eutils.ncbi.nlm.nih.gov/entrez/eutils/efetch.fcgi?db= DATABASE_GOES_HERE>& e.g. http://eutils.ncbi.nlm.nih.gov/entrez/eutils/efetch.fcgi?db=gene&id=596 http:

RE: [rdf] Re: proposal for standard NCBI database URI

2006-05-09 Thread Xiaoshu Wang
> http://eutils.ncbi.nlm.nih.gov/entrez/eutils/efetch.fcgi? > > which just brings back the raw data. Details here: > > http://eutils.ncbi.nlm.nih.gov/entrez/query/static/efetch_help.html These kinds of URIs are more used as API. It will be difficult to use them in the context of SW to

Re: [rdf] Re: proposal for standard NCBI database URI

2006-05-09 Thread Mark Wilkinson
I stand corrected :-) Are there limits on the number of retrievals that can be done in a day on these URLs? i.e. will my domain get blacklisted if I pull in 100K records every hour? M On Tue, 2006-05-09 at 10:58 -0600, Larry Hunter wrote: > On Tue, 2006-05-09 at 09:16 -0700, Mark Wilkinson w

Re: [rdf] Re: proposal for standard NCBI database URI

2006-05-09 Thread Larry Hunter
On Tue, 2006-05-09 at 09:16 -0700, Mark Wilkinson wrote: > H yeah, that's true... but my "gut" does a back-flip when I am > forced to use a URI that refers to a web page, complete with fancy NCBI > decorations and menu's You're mistaken about that. If you don't want the decorations, the

Re: [rdf] Re: proposal for standard NCBI database URI

2006-05-09 Thread Mark Wilkinson
H yeah, that's true... but my "gut" does a back-flip when I am forced to use a URI that refers to a web page, complete with fancy NCBI decorations and menu's :-) I think what we are REALLY looking for is an identifier of a data- entity, independent of its representation. This is what t