Subject: Re: [xsl] XMLPipe model: should we change the name? From: Michael Pediaditakis <mp49@xxxxxxxxx> Date: Sat, 22 Feb 2003 17:47:18 +0000 |
Michael Pediaditakis wrote:Hmm... thanx.. t12nPipe (that's amazing).
We are in the process of finishing the implementation of a model (in Java) that realises a number of ideas on transformation pipelining, heterogeneous documents combination and handling and a way to semi-automatically produce the correct combination of transformations for a specific application profile.
Now, the core aspect of the whole architecture is the
pipelining of transformations (mainly XSL-T) for the
XML documents... And thus, the original name that I thought
to give to the whole model and the implementation is
"XMLPipe".
TransformationPipe? (t12nPipe?) XSLTPipe? Perhaps something incorporating the word "flow" or "chain"?
In that case I could keep the XMLPipe name and avoid changing vast amounts of (crapy Java) code!
XML* names should be reserved for W3C products and recommendations
Too late. Although in XML documents, yes, they reserve the xml* names :)
Well, the difference is that I'm not a company ...a poor research student instead.. and I used the original XMLPipe
So, my question is: Do you think that I should change the
name before we make a public release of the model and implementation?
I'm surprised you didn't lock yourself into a name when you were making the prototype, like the rest of us do :) Having the chance to change the name of your product just before release, and to put some serious thought behind it is a luxury many companies don't have.
My approach is to introduce a generic "context" information which is shared between different transformations.
One thing that we noticed when implementing stylesheet chaining/pipelining/ whatever in 4Suite (see, I can advertise, too) is the problem of what to do with external stylesheet parameters. Say you want to pass the output of stylesheet 1 to stylesheet 2, and stylesheet 2 needs some top-level parameters passed in. For now we just don't do anything; only the first stylesheet in the chain gets that privilege. So I'm curious... what does your system do in this regard? Or if you prefer not to divulge, what do people think a system *should* do?
Thanks for the comments, Mike.
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] XMLPipe model: should we , Michael Pediaditakis | Thread | Re: [xsl] XMLPipe model: should we , Michael Pediaditakis |
Re: [xsl] XSLT for the PocketPC, Daniel Veillard | Date | Re: [xsl] XMLPipe model: should we , Michael Pediaditakis |
Month |