You can make it that way, but I'm not sure I agree that this should be
the canonical URI for TreeBASE. Why shouldn't that be http://treebase.org
, and TreeBASE as a resource and concept exists without the existence
of phyloWS, so I don't see why to tether those two together.
If you want the base phyloWS URL to resolve to something useful, have
it resolve to the TreeBASE PhyloWS API documentation. You could even
add conneg or client name interpretation to return a WSDL2.0
description if it's a machine that's accessing that URL.
-hilmar
On Mar 12, 2010, at 7:41 AM, Rutger Vos wrote:
> Hi all,
>
> I'm working on issue 2960840, and a conceptual issue has come up. What
> should http://purl.org/phylo/treebase/phylows/ itself, without path
> fragments, point to? I am of the opinion that, in a semweb world, this
> should be the canonical resource that identifies treebase and so this
> should be the One, True homepage of treebase - or even an RDF
> description of what treebase is. What do you think?
>
> Rutger
>
> --
> Dr. Rutger A. Vos
> School of Biological Sciences
> Philip Lyle Building, Level 4
> University of Reading
> Reading
> RG6 6BX
> United Kingdom
> Tel: +44 (0) 118 378 7535
> http://www.nexml.org
> http://rutgervos.blogspot.com
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Treebase-devel mailing list
> Tre...@li...
> https://lists.sourceforge.net/lists/listinfo/treebase-devel
--
===========================================================
: Hilmar Lapp -:- Durham, NC -:- informatics.nescent.org :
===========================================================
|
