BIONT/BioRDF [Telcon]

2007-02-02 Thread Susie Stephens
For the next few weeks, while we are focusing on finalizing the use cases, we are going to be holding joint BIONT/BioRDF calls. The first of these calls will be held during the BioRDF time slot on Monday. Kind regards, Vipul and Susie Date of Call: Monday February 5, 2007 Time of Call: 11:

RE: [BioRDF] URI Resolution

2007-02-02 Thread Matthias Samwald
> - If the server replies 303 See Other, follow the link in the > response to get information about resource. [obscure hack but worth > a try] > (see http://www.w3.org/2001/tag/issues.html#httpRange-14)   I guess we should find a diplomatic formulation for that.     > - Disadvantage: you need an O

Re: [BioRDF] URI Resolution

2007-02-02 Thread Mark Montgomery
- Mint URL's whose hostname specifies a long-lived server that will maintain the resource at the given URL in perpetuity. (Publishers, libraries, and universities are in good positions to do this.) [good as for as it goes, but user may not be in control, or may find quality

RE: [BioRDF] URI Resolution

2007-02-02 Thread Booth, David (HP Software - Boston)
> From: Xiaoshu Wang > > > From: David Booth > > . . . > > My overall comment: Yes! I believe a URI resolution ontology could > > significantly help address these problems, while still > > permitting URIs > > to be based on the http scheme, thus facilitating bootstrapping and > > minimizing ba

Re: [BioRDF] URI Resolution

2007-02-02 Thread Xiaoshu Wang
My overall comment: Yes! I believe a URI resolution ontology could significantly help address these problems, while still permitting URIs to be based on the http scheme, thus facilitating bootstrapping and minimizing barriers to adoption. I am very doubtful about the practicality of such an