- From: Chris Lilley <chris@w3.org>
- Date: Thu, 20 Jun 2002 14:03:02 +0200
- To: www-xml-blueberry-comments@w3.org
Hello www-xml-blueberry-comments, The consequences of section 2.13 Normalization Checking [NEW] plus section 4.3.4 Version Information in Entities [NEW] implies that an XML 1.1 editor might need to be able to edit an XML 1.0 entity as if it were XML 1.1 (ie, not taking the version information from the entity itself but from user option). This would be the case when an XML 1.1 document instance makes reference to an XML 1.0 external entitity, this requiring the external entity to be normalized, and when it is not desirable to edit the version information to upgrade the entity to 1.1 (for example, because it is also referenced by XML 1.0 document instances). It might be useful to suggest this option so that editing tool vendors are made aware of this useful capability. It might even be necessary to edit an XML 1.0 entity as if it were "XML 1.05" in other words, it conforms to the well formedness rules both of XML 1.0 and of XML 1.1. This is readily accomplished by taking a 1.0 instance, applying normalization, and not using the two new characters added to production [3] "S". This seems to follow from "XML 1.1 processors should accept XML 1.0 documents as well. If a document is well-formed or valid XML 1.0, and provided it is fully normalized as defined in Section 2.13, it may be made well-formed or valid XML 1.1 respectively simply by changing the version number." except without the "changing the version number" part. It should perhaps be noted that changing the version number is optional, in the above step, and may not always be desirable in the case of external entities used by both XML 1.0 and 1.1 documents. -- Chris mailto:chris@w3.org
Received on Thursday, 20 June 2002 08:05:25 UTC