They were distinct.
Both now depend on unambiguous names. With the present namespace WD,
unambiguous names depend, in turn, in some cases, on attribute defaults. Which
is circular, since that depends on an unambiguous name for the respective
element, and makes validation depend on defaulting.
I would have prefered to keep the two orthogonal, but I'm just trying to
implement it, not design it...
>
> Exactly the same problem occurs with architectural forms, where you
> might want to derive an element of the same type from different
It's not _quite_ the same, since those _names_ are presumed unambiguous.
> architectural forms at different points in a document. From the
> perspective of DTD design, you have three major choices: