[Bug 25290] [Custom]: Ban uppercase and leading "xml" in custom element names?

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25290

Robin Berjon <robin@w3.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |robin@w3.org

--- Comment #3 from Robin Berjon <robin@w3.org> ---
(In reply to Simon Pieters from comment #0)
> I guess leading "xml" is reserved by XML Core WG.

This is reserved so that XML Core can potentially add elements using their own
protected naming. I don't think that we should enforce this because:

  1) It seems extremely unlikely to ever happen.
  2) XML parsers don't enforce this (that I've ever seen).
  3) Because of (2), it is not entirely rare for people to actually use "xml"
in their element names.
  4) In the unlikely event that XML Core were to create such an element, I'm
guessing it would be far more likely for it to ever be supported as a custom
element than directly by the browser.
  5) It's unclear to me why XML Core would need this given that they can use
namespaces if they want to, too (notably xml:).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 14 April 2014 10:02:30 UTC