[
Lists Home |
Date Index |
Thread Index
]
Not exactly right.
1. They weren't dumped. For XML, there is exactly one.
No one uses it for anything that I'm aware of because
XML systems are blithely unaware of it, which is what
'informative' means in standards.
2. When used, IME, they served as contract vehicles.
No one read them because only a few people could but
they were there to tell people what to expect. At
least, who to blame.
3. From time to time, here as you are aware, someone
proposes a requirement that might be met by some
descendant of the Declaration, but are shouted down
by "Ickypoo, that's the Declaration come back; handle
it in your code."
And so it goes. I don't expect to see XML evolve.
I do expect to see it hidden away under every more
abstract layers of code until it becomes irrelevant
and then the whole cycle will begin again.
Nothing declared lasts except the declarative act.
len
From: Joe English [mailto:jenglish@flightlab.com]
Sent: Friday, August 05, 2005 3:40 PM
What you advocate is reminiscent of the QUANTITY and CAPACITY
sections of the SGML declaration. These were a perpetual annnoyance
(the SGML declaration was the first thing that got dumped
when XML was being designed), and as far as I know they
never did anybody any good (i.e., they were never an accurate
indication of how large a document any particular application
could actually handle).
|
