[
Lists Home |
Date Index |
Thread Index
]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
At 14:02 21/8/02, Elliotte Rusty Harold wrote:
>I suspect an irrational aversion to processing instructions killed this
>sensible scheme.
My recollection was exactly thus: even though compatibility with existing
Web browsers was explicitly not a goal of XML, the fact that browsers
displayed PIs made them a non-starter for namespaces in a mandate that came
down from the W3C Team. I seem to recall that this was just as RDF was
getting started, and it was Very Important that it be possible to embed RDF
in HTML pages without disrupting existing browsers, and also that RDF use
namespaces. (I think P3P uses RDF, and thus this requirement, but I can't
remember.)
>This would not have fixed the issues with unresolvable URLs or attributes
>in no namespace, but it would have neatly eliminated all scoping issues.
The scoping issue was independent from PI usage, though; there were
proposals to scope the PI syntax to the immediately containing
element. However, it was strongly argued that some processes might be
building multi-namespace documents on the fly, and not know that they
needed to declare a particular namespace until halfway through.
~Chris
- --
Christopher R. Maden, Principal Consultant, crism consulting
DTDs/schemas - conversion - ebooks - publishing - Web - B2B - training
<URL: http://crism.maden.org/consulting/ >
PGP Fingerprint: BBA6 4085 DED0 E176 D6D4 5DFC AC52 F825 AFEC 58DA
-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Privacy 6.5.8
iQA/AwUBPWYIN6xS+CWv7FjaEQKj8QCfZcf4ZyPqR/L/4ZRxgpyOLrMtsccAn0I2
ulrVwE9PwlcDMvgAhKveF2fn
=QqZj
-----END PGP SIGNATURE-----
|
