[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Looking for an example of a name colliision

• To: "Simon St.Laurent" <simonstl@s...>, <xml-dev@l...>
• Subject: Re: Looking for an example of a name colliision
• From: "Jonathan Borden" <jonathan@o...>
• Date: Sun, 1 Jun 2003 14:35:22 -0400
• References: <r01050400-1026-4A3971D493E211D7B5F00003937A08C2@[192.168.124.11]>

Simon St.Laurent wrote:

> tpassin@c... (Thomas B. Passin) writes:
> >We all have to code to context, but I'll bet that just about everyone
> >tries to minimize context-sensitive processing whenever possible.  I'd
> >rather not do anything that adds to the context that needs to be
> >handled.
>
> The biggest change in my recent work is that I'm taking context more and
> more seriously.  I think it may be something we avoid early on, but
> value later.
>
> The big lesson I get from XPath is that it's a great, even easy, way to
> specify context.  That's something worth building on.
>

The big lesson that should be realized is that this success of XPath is an
example of handling "context" in a declarative rather than processing based
(e.g. stack) fashion.

That is to say: one way of handling context is via code in a SAX event
handler (and this code is often rewritten by each programmer who codes an
event handler) vs. by defining context as (a function of) the "semantics" of
an XPath string.

That might sound like a mouthful, and we know many many programmers who
liberally sprinkled profanity on their initial experiences with XSLT, but
once the cognitive hurdle of XSLT has been overcome, declaring context
rather than coding it, is a liberating experience.

Jonathan

• Prev by Date: Re: Looking for an example of a name colliision
• Next by Date: Re: Data vs. Process was Re: Vocabulary Combination ...
• Previous by thread: Re: Looking for an example of a name colliision
• Next by thread: Re: Looking for an example of a name colliision
• Index(es):
  • Date
  • Thread