W3C home > Mailing lists > Public > public-sml@w3.org > December 2007

[Bug 4687] Handling of DTDs when composing an IF document

From: <bugzilla@wiggum.w3.org>
Date: Wed, 05 Dec 2007 16:57:59 +0000
CC:
To: public-sml@w3.org
Message-Id: <E1IzxZP-00047o-4s@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=4687


sandygao@ca.ibm.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |




------- Comment #14 from sandygao@ca.ibm.com  2007-12-05 16:57 -------
Sorry for not having reviewed this earlier and having to reopen it.

1. I'm surprised to see that definition documents don't get to use
<base64Data>. I think it's better to treat definition and instance documents
consistently. There is no reason to believe that producers can always
"normalize" definition documents so that they don't need DTDs.

2. I'm also surprised to see "Instance documents that do not contain a DTD MUST
be embedded as the content of a model/instances/document/data element". A
producer may choose to embed all documents using base64Data, for simplicity.
And there may be cases where the embedded document does *not* want to get the
"global" DTD. Then "base64Data" is a good solution.

3. It may help to clarify what's actually encoded in "The document MUST be
encoded in base64 format." It could be interpreted as encoding the Unicode
characters. I think we really mean the octet stream (in the original encoding).

4. "as a embedded instance document" -> "as *an* embedded instance document"

Again, please accept my apologies for not having reviewed this before the call.
Received on Wednesday, 5 December 2007 16:58:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:56:08 UTC