[
Lists Home |
Date Index |
Thread Index
]
- To: xml-dev@lists.xml.org
- Subject: Re: [xml-dev] Looking for an example of a name colliision
- From: Arjun Ray <aray@nyct.net>
- Date: Sun, 01 Jun 2003 06:25:24 +0000
- In-reply-to: <m3brxih26c.fsf@t-port.lib.aero>
- References: <ab7bdvs3gol4j4trlefsiq6g4bfbaou70f@4ax.com> <3ED5B096.9080102@textuality.com> <3ED6062E.4080403@bitworking.org> <014f01c326ba$5d609890$b6f5d3ce@L565> <3ED860C6.5060207@dehora.net> <001701c3277e$f2b84130$6401a8c0@tbp1> <74thdv4ngtrbjakbft8l1j798veddmnbsv@4ax.com> <m3brxilnhr.fsf@t-port.lib.aero> <003f01c327d9$583c5000$6401a8c0@tbp1> <m38ysmr1ev.fsf@t-port.lib.aero> <007d01c327ee$70cf0120$6401a8c0@tbp1> <m3brxih26c.fsf@t-port.lib.aero>
ari@cogsci.ed.ac.uk (K. Ari Krupnikov) wrote:
| "Thomas B. Passin" <tpassin@comcast.net> writes:
|> Arjun seems to want us to disambiguate everything
|> with some combination of control attributes plus context.
I'm not sure how I introduced the notion of context.
| Exactly what I said. Instead of (attribute name fixed, value affects
| interpretation)
|
| xmlns:xsl="http://www.w3.org/1999/XSL/Transform";,
|
| Arjun proposes
|
| xslLiteral="true"
|
| (attribute value fixed, name affects interpretation).
I didn't propose this. My proposal is based on
(attribute name declared, value affects interpretation - including
non-assertion of the attribute altogether)
The difference between "fixed" and "declared" is that "fixed" applies
across all instances, "declared" for only this instance.
| The same scoping problems remain.
There are no scoping problems unless one chooses to implement an inference
scheme. But infering the value of a missing attribute specification (as
"scoping problems" typically become) is not the point. It's to treat
non-assertion as significant.
|
