[
Lists Home |
Date Index |
Thread Index
]
Aaron Skonnard asks:
> I think I understand what you're saying. What I'm failing to see is
> how this simplifies anything from the coder's perspective if it
> doesn't impact the way attributes are reflected in the APIs (as Tim
> Bray noted). Developers still have to know your rule when writing the
> code. How would it be any less confusing than it is now?
As with all Best Practices recommendations, its effectiveness is
determined by how widespread its use is, and whether or not it
eventually influences specs.
At least I'm hoping to provide a rule-by-reference, rather than having
developers discover this over and over independently.
Also, for future reference, monasticxml.org isn't particularly
interested in the "coder's perspective". It's squarely and very
deliberately focused on markup works, not what's easiest for programmers
from other perspectives.
--
Simon St.Laurent
Ring around the content, a pocket full of brackets
Errors, errors, all fall down!
http://simonstl.com
|
