Design Questions

[Seth Ladd]

On 8/17/05, Daniel Leuck <dan at ikayzo.org> wrote:
> > I would have suggested a # to use as a pointer, but that's used for
> > comments.
> 
> I just realized that will bite us for anchors in URLs if we introduce a URL
> literal as well.  I suppose we could treat it specially for URLs...

Ah yeah, good point.  Should work OK if you enclose it in quotes somehow.

> 
> > foo attr=@bar
> > bar some object
> 
> That makes sense.  So bar is a tag elsewhere in the document (or another
> document?)  Can it point to specific values or attributes within the
> referenced tag?

hehe Now you're talking SDLPath.  The notation above simply references
another Tag.  If you wanted a value of a tag, you'd have to use
@bar[0] (for "some") or @bar[1] (for "object")

And of course you can do @bar['attr'] to refer to an attribute of a
tag.  And if you want to refer to nested tags, simply use '/'.  For
instance:

example @ref/nested[0]
ref value {
  nested foo
}

@ref/nested[0] == value foo

Which is all well and good.  I'm most interested in getting an
equivalent to the xml id and idref constructs, but a more full
featured SDLPath would be nice, especially to have to avoid traversing
the giant graph by hand when it comes time to process it.

Seth