Lists Home |
Date Index |
W. E. Perry wrote:
> ... The 'markup' answer to the original question is
> that the type of a document is the GI of its root element. The wisdom of
> definition, as expressed by DOCTYPE, seems to become ever clearer as this
> of discussion progresses.
It is not totally clear to me that the GI and DOCTYPE definition need define
the same 'type'. That is to say, the GI of the root element, particularly
when the element is namespace qualified, points to the namespace as 'half'
of the type and the 'local name' which is qualified by the namespace, as the
DOCTYPE however, allows the document instance to have a particular
association of root element name and a DTD. Presumably the DTD _could_
change from instance to instance. In practice, DTDs, when they do change,
may change over the lifespan of an instance, e.g. during edit mode, and are
more properly associated with the how the document is to be processed,
rather than some 'instrinsic' property of the instance itself. I suspect
that you would agree with this, as I am restating the 'local control'
>... I would argue that, if we allow markup to control,
> there might in a native XML database be many document instances which must
> considered of the same type though they exhibit vastly different
> below the name of their root element. And of course there many be many
> and document processing strategies anchored to that one
> root element type.
The question is whether a non-DTD hardwired replacement for DOCTYPE would be
The position that 'document type' has primacy over root element name is
(e.g. AF is an easy way to change the root element name).
I posed the hypothetical question in order to help sort out this issue
("Strategies for a lowly XML document"):
Gavin feels strongly that the instance ought not dictate the processing:
So perhaps the conclusion is that 'document type' is not a useful way to
direct processing. The question remains whether 'instance centric semantics'
has meaning beyond 'root element name' but this remains a theoretical
issue -- that is to say, the user of the document 'knows' what he or she
wants to do with it, and has final say.
When the author of a document has a specific and single intended 'semantics'
to be associated with the instance, the markup ought be highly constrained
and reflex this intent. In such cases the root element name does need to
know, or have the means to find out about, all its offspring. It is in such
cases where XML namespace qualification is particularly helpful, because the
root element namespace name/URI is a means of obtaining information about
the namespace and hence the intended semantics of the root element. The
creator of such a document has the responsability to ensure that users will
have the means to obtain its _intended_ semantics, because ultimately the
processor has the final say. RDDL via the namespace name is a means of