W3C home > Mailing lists > Public > public-rdf-in-xhtml-tf@w3.org > November 2007

Re: Understanding 'chaining'

From: Mark Birbeck <mark.birbeck@x-port.net>
Date: Thu, 29 Nov 2007 17:28:08 +0000
Message-ID: <a707f8300711290928i13506605oec65407cd3a569ff@mail.gmail.com>
To: "Ivan Herman" <ivan@w3.org>
Cc: ben@adida.net, public-rdf-in-xhtml-tf@w3.org

Hi Ivan,

I wrote:
> > That's right; since we're already passing a 'context' full of
> > properties via a stack, then as you say, this is nothing major.
> >
> > So essentially we'd just add a flag to the context to indicate that we
> > have a 'partially completed' triple, and then of course we'd also add
> > to the context the subject and predicate of that incomplete triple.
> > When something completes the triple, it would clear the flag before
> > any further recursion happens.
> >

You wrote:
> It is a little bit more I believe. If you have a chain of elements with only @rel, then you
> will have to accumulate hanging triples, ie, passing them 'on' to
> children before putting them (possibly) into the triple store.

That is true. But it has already been done for us. The current
processing steps already capture context and push it onto the stack
when recursing. If we were to add the 'incomplete triple' values to
the context, then they too would be pushed.

So you are right that you need to keep track of all other 'incomplete
triples' that are 'above' the current one, but they will simply be
sitting on the stack in the various contexts that have been pushed,
waiting to be used when the processor starts returning from recursed
processing.

Regards,

Mark

-- 
  Mark Birbeck, formsPlayer

  mark.birbeck@formsPlayer.com | +44 (0) 20 7689 9232
  http://www.formsPlayer.com | http://internet-apps.blogspot.com

  standards. innovation.
Received on Thursday, 29 November 2007 17:35:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:15:18 GMT