Lists Home |
Date Index |
- To: firstname.lastname@example.org
- Subject: Re: [xml-dev] Looking for an example of a name colliision
- From: "Thomas B. Passin" <email@example.com>
- Date: Sun, 01 Jun 2003 00:41:05 -0400
- References: <r01050400-1026-4A3971D493E211D7B5F00003937A08C2@[192.168.124.11]>
> firstname.lastname@example.org (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
> 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.
I'll go with that. Also, despite my wish expessed above, most of the
processing I do requires using contexts - and much of it is done with xslt.
But I was more thinking of SAX-like processing, where the more context to
keep track of the harder it gets. This strengthens Simon's point, I think.