Thank you, Jim. That's what I expected. I'm just hoping for 1.0 final is close enough.


On Nov 12, 2007 4:31 PM, Jim Wilson <> wrote:
Although I am in favor of {{#ask:}} at the earliest possible
conveneince, after a cursory look through the code, I'm fairly certain
this extension will fail to operate as expected.

The first reason is that <ask>, which is an extension tag, will always
return fully qualified HTML.  The output of a parser function is
expected to be wikitext, which will be further processed.  The result
is that if the output of the {{#ask:}} call contains any links,
they'll be HTML links (like <a href="something">something</a>), not
wiki text (like [[something]]).  When the Parser reads these HTML tags
during subsequent processing, it'll convert the '<' and '>' symbols to
their entity equivalents '&lt;' and '&gt;' so in the browser you
actually see '<a href="...">whatever</a>', not a nice link.

The second reason is that one of the huge benefits of having an
{{#ask:}} parser function is nesting.  The idea that you could
{{#ask:something={{#ask:something else}}}}.  I'm not sure if SMW
supports nested <ask> tags, but if not, this would also be a failure
mode of the aforementioned extension.

Again, I would like nothing more from SMW than an {{#ask:}} template -
which would be a __HUGE__ improvement for advanced use cases, but I
don't think that this extension is the answer everyone hopes it is.

-- Jim R. Wilson (jimbojw)

On Nov 12, 2007 10:38 AM, Sergey Chernyshev
<> wrote:
> Yaron noticed that there is new inline query extension posted on
>  I'm definitely going to install it and see if it'll work for my needs, but
> what bothers me is the size of it - it seems to be too simple ;)
> I also noticed that it's not going to support '=' or '|' in the queries, but
> it's easy to implement it using the code I sent in before.
> Markus, could you please look at it and let us know if you anticipate any
> problems with this code?
>          Sergey
> --
> Sergey Chernyshev