“Sometimes, something is disallowed because allowing it would likely cause Author confusion.”
Which is kind of the sum of confusion with namespaces that are reserved, or prohibited, because the ‘Domain’ of thought and part of the infrastructure are unique.
Which led me to think about error types, one part of ‘Security’ is an understanding of the different systems, how they work and what they do.
Some of these errors, apply earlier on in the software life-cycle, but they could be useful in examining code during analysis, along with systems that are involved.
I found that the html spec had some interesting perspectives about errors
These are some of the topics about errors the spec mentioned:
Errors that would likely result in scripts failing in hard-to-debug ways
Errors that indicate a mis-use of other specifications
Errors that involve peculiarities of the parser
Errors that indicate a likely misunderstanding of the specification
Errors involving limits that have been imposed merely to simplify the language
Errors that involve a conflict in expressed semantics
Errors involving content with dubious semantics
Errors involving fragile syntax constructs
Errors that result in disproportionately poor performance
Unintuitive error-handling behavior
Errors where the error-handling behavior is not compatible with streaming user agents
Errors that can result in infoset coercion