[
Lists Home |
Date Index |
Thread Index
]
To make it clear, I have no qualms whatsoever about making this change
in practice. I don't believe there are many legacy programs which
exhibit the behavior you describe, nor do I feel that the cost of the
change is particularly difficult, especially moving forward.
Developers who follow my suggestion should be extremely unlikely to
create the brain-dead <x:foo bar="junk" x:bar="junque"> or even <x:foo
x:bar="junk">, thereby averting the continued creation of a larger mess.
XML right now just keeps growing by agglomeration. I'd like to propose
that users start chopping off the rotten bits even if the spec
developers are presently unwilling.
Jonathan Borden wrote:
> It has been generally acknowledged that you are correct
> in that there _ought not_ be such a distinction but the
> problem is that changing the specification at this stage
> of the game, actually would break any number of real
> world programs e.g.
>
> <xsl:template match="x:foo[@x:bar]"> ...
>
> now perhaps such XSLT could be recognized and auto-
> xformed into:
>
> <xsl:template match="x:foo[@bar]"> ...
>
> but I'm sure that I've written something like the above
> any number of times.
>
> Jonathan
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
>
--
Simon St.Laurent
Ring around the content, a pocket full of brackets
Errors, errors, all fall down!
http://simonstl.com
|
