Re: Well-formed Blueberry

[Jeff Greif <jgreif@alumni.princeton.edu>]

This will add some obscure cases to document editing:
 -- by turning a link into an inclusion, a document may have to change from
an XML 1.0 doc to a Blueberry doc
 -- by going the other way (turning a subtree into a link), a Blueberry doc
will be forced to become a 1.0 doc

It's easy to imagine a utility program that takes an element name and an
attribute (e.g. ID) as an argument and converts a document containing such
elements into one containing links to other documents which hold the actual
subtrees rooted in such elements.  Such a utility would then have to scan
the new master document to see if it was still a Blueberry or 1.0 document.
Otherwise, this would have to be done manually, potentially by someone who
would not be expected to know about this subtlety.

Jeff

----- Original Message -----
From: "Elliotte Rusty Harold" <elharo@metalab.unc.edu>
To: <xml-dev@lists.xml.org>
Cc: <www-xml-blueberry-comments@w3.org>
Sent: Friday, July 13, 2001 6:33 AM
Subject: Well-formed Blueberry
|
| I think there's a way to limit the damage this does to the existing
infrastructure. Whatever the eventual identifier is chosen for Blueberry
(version="1.1", unicode="3.1", etc.) I think it should be a *fatal error* to
use this identifier in a document that does not actually use any of the
newly introduced characters in an XML name somewhere.
|
| In other words, if a document can be an XML 1.0 document, it must be an
XML 1.0 document.
|