Hi, On Thu, Apr 07, 2011 at 09:09:35PM +0100, Michael Walker wrote:
> > I don't think the XSLT translator should present a directory tree as > > output. Nothing in XSLT requires the output to be XML. > > Aha, I had a feeling I was misunderstanding something somewhere. In > that case, xslt would be even simpler - the code would be pretty much > the same as unxmlfs (turn an xmlfs directory tree into an internal DOM > representation and present it as output via trivfs), but just with a > transformation performed. > In fact, if that's the case maybe even just a "--xslt=FILE" option to > unxmlfs would do the trick. I briefly considered this, but I think we should rather go for the opposite: let the XSLT translator take files as input. If directory input is desired, it can always be set on top of unxml. (BTW, the naming is rather confusing -- unxml actually turns the underlying structure *into* XML... Maybe we should use more explicit names instead: something like xml2dir and dir2xml perhaps.) > However, XSLT is commonly used to turn one XML document into another, > so perhaps there should be an option to try and present it as a > directory tree, Again, it seems saner to put another xmlfs on top if this is required. -antrik-
