Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Posted-Date: Thu, 30 Mar 2000 20:49:15 GMT
Date: Thu, 30 Mar 2000 22:49:15 +0200 (CEST)
From: Dirk-Willem van Gulik <dirkx@webweaving.org>
To: cocoon-dev@xml.apache.org
Subject: Re: [RT] latest wonderings around W3C land and surroundings
In-Reply-To: <38E3BAD6.C3276AA2@algroup.co.uk>
Message-ID: 
 <Pine.BSF.4.05.10003302248180.16600-100000@kim.ispra.webweaving.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Thu, 30 Mar 2000, Ben Laurie wrote:

> Stefano Mazzocchi wrote:
> > ----------- XBase ----------------
> > 
> > xbase is a simple way to make it possible for xml-handlers to know the
> > base URI of that document. At first, it looks like Cocoon _should_ be
> > able to use that information in order to locate URIs. The question is:
> > does XBase violate concern separation?
> > 
> > think about it: if you have xbase:base="http://myhost/mypath/" in your
> > document, how are you going to move it around?
> > 
> > Hmmm, makes me think that XBase is good on client side, but on server
> > side sucks.
> 
> Surely the server should generate it? Never quite understood the point
> of base stuff myself anyway.

Actually that depends, if you have some object store, or you start
shipping it around outside its context (we try to do something with URN's
for long term archvies where parts move with the scientist) then this
starts to make some sense.

Dw