Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: forrest-dev@xml.apache.org
Date: Thu, 19 Dec 2002 02:17:40 +1100
From: Jeff Turner <jefft@apache.org>
To: forrest-dev@xml.apache.org
Subject: Re: File prefix again (Re: Cocoon CLI - how to generate the whole
 site)
Message-ID: <20021218151740.GA2922@expresso.localdomain>
Mail-Followup-To: forrest-dev@xml.apache.org
References: <20021216055750.GB1708@expresso.localdomain>
 <3DFD87E4.1090508@apache.org> <20021216120309.GA2355@expresso.localdomain>
 <3DFDCEC0.1060109@apache.org> <20021216142017.GC2355@expresso.localdomain>
 <3DFDEC75.1020700@apache.org> <20021217043902.GA1977@expresso.localdomain>
 <3DFF2FBD.5020601@apache.org> <20021217155222.GC8629@expresso.localdomain>
 <3E0084C7.2000100@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3E0084C7.2000100@apache.org>
User-Agent: Mutt/1.4i

On Wed, Dec 18, 2002 at 03:23:03PM +0100, Nicola Ken Barozzi wrote:
...
> >Firstly: do you agree that there _are_ two Sources?  That the user
> >_could_ create an index.pdf?  In fact, considering that the user isn't
> >meant to know that index.xml even *has* a PDF rendition, why shouldn't
> >they create an index.pdf?
> 
> I don't agree here. The user creates documents to explain a concept. 
> "index" means it's the index.

Since when do semantics come into the business of ensuring every source
has a URI?

Fact: users _can_ create an index.pdf.  Whether this is a good idea is
irrelevant: as a source of content, it deserves a source URI.  We can
then say, "by the way, it's really dumb creating index.pdf when you've
got index.xml", but that's a layer above the raw URI space addressing
issue.

Popping the argument stack a bit, remember that this whole silly example
of index.xml/index.pdf is a pathological case, that won't have the
desired effect no matter what the URI is.  You have ignored my main
argument, that the 'cocoon:' prefix is implicit and _conceptually_ a
file: scheme is required.


--Jeff

> Who cares what the rendition is.
> Imagine the user making an index.xml and index.xhtml file in the same 
> dir. Does it make sense?
> 
> >Secondly, do you agree that conceptually, any source of content should be
> >assigned a Source URI?  _Regardless_ of whether it has a Destination URI?
> >Because Source and Destination URI spaces have no direct relation.  Heck,
> >I could generate a single PDF containing the entire site, thus mapping
> >lots of Source URIs to a single Destination URI.
> 
> Yes, on this I agree. We should always link to source URIs, so that what 
> you explain about a single PDF can be possible. And it's also easier for 
> the user. +1
> 
> -- 
> Nicola Ken Barozzi                   nicolaken@apache.org
>             - verba volant, scripta manent -
>    (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
>