WD-xml-infoset-20010316

I think this WD is excellent. I think you've done a particularly good
job in handling the area which is probably the hardest and most
contentious, namely namespaces.  I hope you will keep the WD exactly as
it is in this respect.

Should not unparsed entity and notation information items have a [base
URI] property, which an application would use for resolving a relative
system identifier? Also unexpanded entity reference info items probably
need a base URI as well (corresponding to the base URI of the entity
declaration).

The note in 2.6 that end-of-line normalization is applied to character
info items applies equally to the content of comments and processing
instructions.  Maybe this is worth mentioning in the spec, since it's a
detail that implementors can easily forget.

The [character encoding scheme] and [system identifier] properties on
document information items trouble me a little.  Logically they are
associated with the document entity not with the document.  I think the
right way to deal with the removal of parsed entities is to remove these
properties altogether rather than transfer them to an information item
to which they do not logically belong.

I would also question [system identifier] and [public identifier] on the
document type declaration info item.  The external subset is just
another parsed entity.  If you are not providing system and public
identifiers for all parsed entities, why provide then for the external
subset?

James

Received on Thursday, 22 March 2001 23:11:49 UTC