Re: FYI: TMQL - New slides

On Sat, Apr 02, 2011 at 10:21:58AM +0200, Benjamin Bock wrote:

> If you store the homepage as xsd:string and want to retrieve it as
> string, you'd do:
> 
>     bb / homepage / value
> 
> . If you left out the "/ value", you'd get an occurrence object (as
> JTM or XTM fragment or TMAPI object or whatever... depending on the
> engine.

I'm not perfectly convinced that it would be wise to have the delivery
be dependent on the TMQL engine.

> I didn't find where TMQL@rho does the automatic conversion xsd:string
> to xsd:anyuri, though.

It doesn't.

> Can you point me to it? Or can I just assume you're looking for
> differences where there are none?

I'm just wondering about these details. Mostly for historic reasons,
and my memoires.

> > Again, this is all about speed: In
> >
> >   bb >> occurrence homepage
> >
> > I am ONLY looking for "homepage" occurrences, i.e. any multi-level
> > index on occurrences you might have can immediately be effective in
> > returning the correct results. No further filtering necessary.
> 
> It works exactly as you describe it in the new draft, too. I guess
> it's just the title of the slide which might be suboptimal and
> confused you.

Ah! Possibly so.

> A kind reminder: We're taking TMQL@rho as the base for our work. :)
> Obviously, we're still in the educational phase (for all parties).

> One reason why it works is that (currently) axes need parentheses
> while de the default axis parameter don't allow them.

The "default axes" ... is very ... perlish. :-)

\rho