Re: [Treebase-devel] treebase.domain.name

[Vladimir G. <vla...@du...>]

On Jan 13, 2010, at 2:32 PM, William Piel wrote:

> my $0.01 thought is that using purls for all phylows URIs is  
> something we, at one point, decided to do.

Since I am late to the party, could someone point me to more details  
on this matter?

At the moment, I have trouble seeing why TB should in any way depend  
on a third-party URL redirection service.  The only valid reasons for  
PURLs that I see mentioned at http://en.wikipedia.org/wiki/PURL apply  
to poor people without their own domains.  As far as I understand the  
problem, the real stability issues of a URL like http://purl.org/phylows/study/TB2:S1020 
  lie not in its "http://purl.org/phylows" part but in its "study/ 
TB2:S1020" part -- and a redirect to http://treebase.org/phylows/study/TB2:S1020 
  does not help solving these issues at all, while http://treebase.org/phylows 
  is as stable as http://purl.org/phylows.

For a context: I am concerned with the matter only as far as  
considerations like
> So, for example, our dev-build would be built using the global  
> phylows-property parameter "http://treebasedb-dev.nescent.org:8180/treebase-web/ 
> ", while the deployment build would be built using the global  
> parameter "http://purl.org/phylo/treebase/". That way we can easily  
> test new changes to TreeBASE on the dev server without all of its / 
> phylows/ links rerouting us to the deployment build.

lead to complications of builds that could be avoided.

--Vladimir