Hi, devs.
I'm working on JCRStore and QueryPlugin and I want to get some feedback
about
http://dev.xwiki.org/xwiki/bin/view/Design/XWiki+Query+Language+Specificati…
1. Why our QueryPlugin's xpath isn't sufficient? (except it doesn't work
now and some features are unimplemented :))
2. Are we sure to use sql-like query language?
I think sql isn't user friendly language.
Also many features of sql (such as joins) is impossible for JCR.
XPath makes a lot of sense and user friendliness if we ignore its (scary)
name:
if we look at a wiki as a file system, XPath is perfectly usable as a file
system path referencing: all data would be nodes, all metadata would be
attributes.
I think that, put this way, besides being clear as daylight for developers
(as Thomas mentioned), it can also be easily understandable by users (as
Guillaume proved).
Besides that, since it is based only on a few simple rules (once axis
implemented), we would be exposing less unimplemented features to the user
than with our own, sql-like-but-not-quite-sql query language.
As well, an XPath query language would allow us to implement the support
of sheets (currently Velocity code or Groovy code) as XSL Sheets, using
the wiki as one big input document. I know I would definitely love this
'feature'.
Of course, I agree that SQL might be a little more natural or easier for
users / developers, but I think its popularity and it being here for a
longer time than XPath has much to do with it.
3. What user query language would you prefer for
xwiki?
3. so I'm for full, clean XPath
Happy coding!
Anca Luca
--
Artem Melentyev
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs