Re: FYI: TMQL - New slides

On Fri, Mar 25, 2011 at 11:09:18AM +0100, Lars Heuer wrote:

> Although the discussion about TMQL stopped immediately, the editors
> have produced new slides:
> <http://www.itscj.ipsj.or.jp/sc34/open/1586rev.pdf>

Hi Rani et.al.,

Is it intentional that typing for assocs and for topics is treated
differently? For assocs (eg. Slide 15)

   t1 / typed

For topics (Slide 52):

   t1 / instances

------

I know that TMDM hold the "data type" within the occurrence node

   http://www.isotopicmaps.org/sam/sam-model/#sect-occurrence

[yes, weirder things have happened], but TMDM also assumes that values
are all strings.

As this cannot be the case for TMQL (it has to be able to apply numeric
operators), why is this maintained in Slide 21ff ?

------

On slide 65 filtering is introduced using []. But throughout the
earlier slides an implicit filtering is always provided inside ():

  t1 / occurrences(address)

Not to mention that this is more typing than

  t1 / address

which we already had and where I do not remember many people had issue
with. Or is this a shortcut I missed somewhere when I skimmed through
the doc?

------

Slide 72: in

 // topics(composer)

what exactly is the relevance of // ? Would not

  topics(composer)

or better

  topics[composer]

achieve the same?

------

Slide 72: Are these ops REALLY meant to be SET operations? I hope you
understand the relevance of that question in respect to performance.

------

I am also - amused ;-) by the reemergence of functions aka
user-defined axes. The world is indeed a round thing....

------

Slide 78, lower half: I would love to see a 'formal', complete
definition of this. I suspect that you will encounter quite some
rather counter-intuitive effects:

  select $topic / shoesize, $topic / birthdate
  from $topic / type = very-weird-person

may give you 4 results with 2 birth-dates and 2 shoesizes.

Delete the shoesizes and the query never returns you something.

OTOH

  select $topic / shoesize, $topic
  from $topic / type = very-weird-person

will give you always one result per weird person.

------

Slide 79: Also here I would like to see a more comprehensive
description what it means to have unbound variables inside the SELECT
clause.

\rho