Return-Path: Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 71007 invoked by uid 500); 15 Jul 2003 20:39:17 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 70989 invoked from network); 15 Jul 2003 20:39:16 -0000 Received: from mhub-m2.tc.umn.edu (160.94.23.45) by daedalus.apache.org with SMTP; 15 Jul 2003 20:39:16 -0000 Received: from umn.edu (rose.ce.umn.edu [134.84.148.222] (may be forged)) by mhub-m2.tc.umn.edu with ESMTP for dev@cocoon.apache.org; Tue, 15 Jul 2003 15:39:02 -0500 (CDT) X-Umn-Remote-Mta: [N] rose.ce.umn.edu #+HF+LO Message-ID: <3F1466A0.5080304@umn.edu> Date: Tue, 15 Jul 2003 15:40:00 -0500 From: Tony Collen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en,pdf MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [RT] The perfect repository might be just under your eyes References: <61A2F881-B6FF-11D7-A769-000393D2CB02@apache.org> In-Reply-To: <61A2F881-B6FF-11D7-A769-000393D2CB02@apache.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Stefano Mazzocchi wrote: > NO! that's the beauty > > echo "application/xml" > /document/@mime-type > > Voila' ;-) > > Actually, even better > > echo "xml" > /document/@syntax > echo "text/xhtml" > /document/@mime-type > > because MIME is getting it all wrong with this stupid +xml by mixing > concerns between the syntax and the semantics. > > Do you see the potential? > >> The obvious question is what happens when you try to do an xpath >> expression on a file that is not XML. Perhaps the filesystem module >> would know enough to check for ? > > > ARRRRRGGGG! > >> >> Lots of potential though :) Maybe you could tie a service to a >> virtual device. Like /dev/xupdate or /dev/xalan, and output to > STDOUT? >> > > That's much better talking, bro ;-) More RTing: Imagine having an XSL processor in the kernel: You could "execute" .xsl files, bypassing having to run a processor manually. prompt$ page2html.xsl < input.xml > output.html Borrowing the pipeline concept from Cocoon: prompt$ cat input.xml | page2foo.xsl | foo2bar.xsl | bar2html.xsl > output.html One could even invent files which are actually transformation pipelines -- ones which you might not be able to directly edit (or maybe be able to edit a transformation in the middle): prompt$ make-virtual-file-pipeline virtual.xml --generator=input.xml --tranformers=page2foo.xsl;foo2html.xsl --serialize=text/xml Now you can just go prompt$ cat virtual.xml And get the output of the pipeline defined above, which you can then link to other pipelines, etc. It's no wonder that this all fits in very well with what Cocoon does, since Cocoon is patterned after this concept. I'm sure if I stew on this concept enough I'll come up with more ideas and uses. Tony