Re: [Bug 7727] legacy doc type does not need to be discouraged by "SHOULD NOT"

>From the issue:

"There's no point in discouraging the legacy doc type with should not;
there is no interop problem being solved by it"

Does this also mean that we shouldn't discourage misnested tags? As
long as all parsers treat them the same way there also should be no
interop issues solved by it.

I guess this sort of leads back to the whole discussion about if
defining what is valid or not makes sense, or if just defining
processing is enough.

/ Jonas

Received on Wednesday, 30 September 2009 08:42:52 UTC