* Stefano Mazzocchi <[EMAIL PROTECTED]> [2004-03-02 03:01]:
> Joerg Heinicke wrote:
>
> >On 26.02.2004 22:04, Alan wrote:
> >
> >>>I would guess that Momento mainly would be accessed through the
> >>>document function in XSLT and XQuery. Saxon use JAXP 1.1 as external
> >>>API to the transformerand the URLs in the document functions are
> >>>resolved by using an implementation of
> >>>javax.xml.transform.URIResolver that is provided by the TraxTransformer.
> >>
> >>
> >>
> >>The above is somewhat confusing for me. Momento does support the
> >> JAXP API. XUpdate is implemented as a SAX filter. It seems like
> >> Momento would work nicely in as a source, sink, or filter for
> >> SAX events.
> >> I've imagined that a pipeline would start with a Momento
> >> document and an XSLT trasform or XQuery query.
> >>
> >> Something along these lines:
> >> <map:match pattern="index.html">
> >> <map:generate type="momento" src="momento.mx"
> >> xslt="index-document.xslt"/>
> >> <map:transform type="xslt" src="document-to-web.xslt"/>
> >> <map:serialize type="html"/>
> >> </map:match>
> >>
> >> (It is easier for me to express myself as a Cocoon user.)
> >
> >
> >It was already mentioned and I only want to repeat it here: Momento
> >should not be implemented as generator, but as source.
>
> I strongly disagree.
>
> XQuery is simply too complex to be passed as one URL. You should have
> something like
>
> <generate type="xquery" src="mystuff.xquery"/>
Yes. I choose Saxon to implement XQuery. I'm finding that XSLT is
just as good a query language, that's why I keep using XSLT in
my generator examples. Not mixing concerns, it is data store +
query, which strikes me as resonable parameters to a generator.
> I don't know if momento is good enough for what we need, but if we were
> to have an xquery processor, a generator is the way to go, not a source.
What do you need from Momento?
--
Alan / [EMAIL PROTECTED] / http://engrm.com/
aim/yim: alanengrm - icq: 228631855 - msn: [EMAIL PROTECTED]
