Comments on: WebDAV, DASL, XQUERY and XPATH 2.0 http://www.goland.org/dasl/ Technology, Politics, Food, Finance, etc. Thu, 04 Mar 2010 05:45:06 +0000 http://wordpress.org/?v=2.9 hourly 1 By: Julian Reschke http://www.goland.org/dasl/comment-page-1/#comment-780 Julian Reschke Sat, 22 Jan 2005 06:41:08 +0000 #comment-780 <br/>Hi,<br/><br/>some more comments...<br/><br/>To clarify: I absolutely agree that this (or a similar) approach would give both a powerful query language and a compact spec. However, I don't believe that currently many people will be able to implement it, thus DASL will still require a much simpler default grammar if we want to achieve interoperability. Of course, the more time passes without DASL/DAV:basic-search progressing, the less important this will be. Maybe at this point DASL should be stripped down to the bare minimum (no sorting, no typing, no query grammar discovery) and be published as "Experimental"... Feedback (and help) appreciated... (mailing list: www-webdav-dasl@w3.org).<br/><br/>The latest version of the bindings specification is draft-ietf-webdav-bind-10 () which is currently in working group last-call. People who are interested in this spec should review it now; it's not going to change substantially anymore.<br/><br/>The Ordered Collections Protocol has been published in December 2003 as RFC3648 (). Hi,

some more comments…

To clarify: I absolutely agree that this (or a similar) approach would give both a powerful query language and a compact spec. However, I don't believe that currently many people will be able to implement it, thus DASL will still require a much simpler default grammar if we want to achieve interoperability. Of course, the more time passes without DASL/DAV:basic-search progressing, the less important this will be. Maybe at this point DASL should be stripped down to the bare minimum (no sorting, no typing, no query grammar discovery) and be published as “Experimental”… Feedback (and help) appreciated… (mailing list: www-webdav-dasl@w3.org).

The latest version of the bindings specification is draft-ietf-webdav-bind-10 () which is currently in working group last-call. People who are interested in this spec should review it now; it's not going to change substantially anymore.

The Ordered Collections Protocol has been published in December 2003 as RFC3648 ().

]]> By: Yaron http://www.goland.org/dasl/comment-page-1/#comment-781 Yaron Thu, 11 Nov 2004 09:28:01 +0000 #comment-781 <br/>Julian Reschke, the man who is pretty much single handedly keeping DASL alive, thought the idea interesting and had done some work in the same area himself but ultimately rejected it for the base draft.<br/><br/>His argument was that even a paired down XQUERY was more than most people could handle implementing. I don't agree with him. I think hooking up an existing open source XQUERY engine would be a lot less painful then having to write an entire query system from scratch. I also think that customers would be a lot more willing to invest in using DASL if they knew that the investment was leverage-able in other areas. Learning DASL's basic query means you know DASL's basic query. Learning a XQUERY based query systems gives you knowledge you can leverage elsewhere.<br/><br/>Technically it's not a big deal since DASL is carefully designed to allow for pluggable query languages and even specifies how to discover what languages are supported. So it wouldn't be a big deal to create a XQUERY for DASL sub-set and publish it as a spec that could then be used in the DASL framework. <br/><br/>But I think DASL will not gain as much interest as it could have had it gone out the door with a sub-set of XQUERY instead of inventing its own query language. <br/><br/>Still, if it wasn't for Julien and a few other people there wouldn't be a DASL at all so I'm not going to complain. Julian Reschke, the man who is pretty much single handedly keeping DASL alive, thought the idea interesting and had done some work in the same area himself but ultimately rejected it for the base draft.

His argument was that even a paired down XQUERY was more than most people could handle implementing. I don't agree with him. I think hooking up an existing open source XQUERY engine would be a lot less painful then having to write an entire query system from scratch. I also think that customers would be a lot more willing to invest in using DASL if they knew that the investment was leverage-able in other areas. Learning DASL's basic query means you know DASL's basic query. Learning a XQUERY based query systems gives you knowledge you can leverage elsewhere.

Technically it's not a big deal since DASL is carefully designed to allow for pluggable query languages and even specifies how to discover what languages are supported. So it wouldn't be a big deal to create a XQUERY for DASL sub-set and publish it as a spec that could then be used in the DASL framework.

But I think DASL will not gain as much interest as it could have had it gone out the door with a sub-set of XQUERY instead of inventing its own query language.

Still, if it wasn't for Julien and a few other people there wouldn't be a DASL at all so I'm not going to complain.

]]> By: Eric Hanson http://www.goland.org/dasl/comment-page-1/#comment-782 Eric Hanson Wed, 10 Nov 2004 18:30:04 +0000 #comment-782 <br/>Great proposal! I'm curious, have you gotten much interest in this topic? I have some immediate and real-world needs for this exact thing.<br/><br/>Regards,<br/>Eric Great proposal! I'm curious, have you gotten much interest in this topic? I have some immediate and real-world needs for this exact thing.

Regards,
Eric

]]>