major thing about Xupdate

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

major thing about Xupdate

Oliver Charlet
... and has anybody thought about updating the XUpdate processor?
The Spex now shows some more interesting tags, like <rename>,
so it might be worth to take a look.
I really do like the XUpdate and I think it is rather underestimated.

Btw: did you guys implement the Xupdate procressor on your own, or did you
use some library?

:oliver

--
-----------------------
oliver charlet
software development

11-041 Olsztyn, Poland

[hidden email]
-----------------------




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: major thing about Xupdate

Erik Bruchez
Administrator
Olivier,

 > ... and has anybody thought about updating the XUpdate processor?
 > The Spex now

Unless I am mistaken, the draft you are referring to dates from year
2000 and has not evolved since them.

 > shows some more interesting tags, like <rename>

OPS does implement the <rename> tag :-)

 > so it might be worth to take a look.  I really do like the XUpdate
 > and I think it is rather underestimated.

We had discussions about XUpdate quite a while ago (last year), and
while we also like the language and its approach for updates, we
decided that we would no longer actively do work on it, because there
is zero momentum behind the language, and while XML databases often
support XUpdate, the trend there is to implement extensions to XQuery
instead.

So we currently advise instead to use XSLT 2.0 or XQuery whenever
possible, even if for some use cases XUpdate is more appropriate.

 > Btw: did you guys implement the Xupdate procressor on your own, or
 > did you use some library?

We did implement the XUpdate processor from scratch on our own. This
said, we are glad to encourage efforts by others to improve on the
XUpdate processor (start with XUpdateProcessor.java), and to answer
questions related to that work in the mailing-list.

-Erik




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: major thing about Xupdate

Oliver Charlet
Eric,

I didn't actually check the Spex' version, my fault!
But then the documentation on the Xupdate processor lacks some tags. the <rename> is not mentioned in the ops docs.
I tried to use the <xu:comment> tag, and that didn't work.
I can understand, that you don't want to invest anymore time in that "dusty" thing, altough it makes me kind of sad ;-)
Maybe I take a look at the processor, when i have too much time ;-).
thanks anyway.
:oliver

Erik Bruchez schrieb:
Olivier,

> ... and has anybody thought about updating the XUpdate processor?
> The Spex now

Unless I am mistaken, the draft you are referring to dates from year
2000 and has not evolved since them.

> shows some more interesting tags, like <rename>

OPS does implement the <rename> tag :-)

> so it might be worth to take a look.  I really do like the XUpdate
> and I think it is rather underestimated.

We had discussions about XUpdate quite a while ago (last year), and
while we also like the language and its approach for updates, we
decided that we would no longer actively do work on it, because there
is zero momentum behind the language, and while XML databases often
support XUpdate, the trend there is to implement extensions to XQuery
instead.

So we currently advise instead to use XSLT 2.0 or XQuery whenever
possible, even if for some use cases XUpdate is more appropriate.

> Btw: did you guys implement the Xupdate procressor on your own, or
> did you use some library?

We did implement the XUpdate processor from scratch on our own. This
said, we are glad to encourage efforts by others to improve on the
XUpdate processor (start with XUpdateProcessor.java), and to answer
questions related to that work in the mailing-list.

-Erik



-- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: [hidden email] For general help: [hidden email] ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

-- 
-----------------------
oliver charlet
software development

11-041 Olsztyn, Poland

[hidden email]
-----------------------


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: major thing about Xupdate

Erik Bruchez
Administrator
Oops,

Regarding the <xu:rename> element, I probably just dreamt that it was
implemented, but it's not the case, so feel free to implement that, it
should not be too hard.

<xu:comment> is also not implemented, but this would not be very useful
in OPS at the moment since XPL pipelines do not transmit comment
information.

-Erik

Oliver Charlet wrote:

> Eric,
>
> I didn't actually check the Spex' version, my fault!
> But then the documentation on the Xupdate processor lacks some tags. the
> <rename> is not mentioned in the ops docs.
> I tried to use the <xu:comment> tag, and that didn't work.
> I can understand, that you don't want to invest anymore time in that
> "dusty" thing, altough it makes me kind of sad ;-)
> Maybe I take a look at the processor, when i have too much time ;-).
> thanks anyway.
> :oliver


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: major thing about Xupdate

Alessandro  Vernet
Administrator
In reply to this post by Oliver Charlet
On 11/25/05, Oliver Charlet <[hidden email]> wrote:
>  I can understand, that you don't want to invest anymore time in that
> "dusty" thing, altough it makes me kind of sad ;-)
>  Maybe I take a look at the processor, when i have too much time ;-).
>  thanks anyway.

Hi Olivier,

I think that the code of the XUpdate is pretty simple to understand
and you should be able implement xu:comment and xu:rename in
reasonable amount of time. All those "constructs" are called
"statements" in the code and are implemented in their own class, in
the org.orbeon.oxf.transformer.xupdate.statement package.

Supporting xu:rename would mean adding such a class in that package
(you can look at the code for similar statements) and registering that
class in TemplatesHandlerImpl.parseStatements(). Of course, if your
code makes sense, we will include it in the builds. Let us know if you
need any help with this.

Alex



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
Reply | Threaded
Open this post in threaded view
|

Re: major thing about Xupdate

Oliver Charlet
I'll see what I can do...

Alessandro Vernet schrieb:

>On 11/25/05, Oliver Charlet <[hidden email]> wrote:
>  
>
>> I can understand, that you don't want to invest anymore time in that
>>"dusty" thing, altough it makes me kind of sad ;-)
>> Maybe I take a look at the processor, when i have too much time ;-).
>> thanks anyway.
>>    
>>
>
>Hi Olivier,
>
>I think that the code of the XUpdate is pretty simple to understand
>and you should be able implement xu:comment and xu:rename in
>reasonable amount of time. All those "constructs" are called
>"statements" in the code and are implemented in their own class, in
>the org.orbeon.oxf.transformer.xupdate.statement package.
>
>Supporting xu:rename would mean adding such a class in that package
>(you can look at the code for similar statements) and registering that
>class in TemplatesHandlerImpl.parseStatements(). Of course, if your
>code makes sense, we will include it in the builds. Let us know if you
>need any help with this.
>
>Alex
>
>  
>
>------------------------------------------------------------------------
>
>
>--
>You receive this message as a subscriber of the [hidden email] mailing list.
>To unsubscribe: mailto:[hidden email]
>For general help: mailto:[hidden email]?subject=help
>ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>  
>
--
-----------------------
oliver charlet
software development

11-041 Olsztyn, Poland

[hidden email]
-----------------------




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws