On Wed, Sep 03, 2003 at 09:46:09AM -0400, Rosen, Brian wrote:
What if the version of the tool the author used is different
from the I-D editor?
The tool itself has -in theory :)- no incidence. Only the DTD has, and
it is not expected to change very often.
What if the xml is not well formed and
the tool does something unexpected?
Well-formedness and validation against dtd MUST be checked by I-D
editor, and SHOULD by authors. Note that this pb is the same with
current scheme: authors can provide messy, bad formatted documents with
ansi escape sequences, etc.
What do we do when we
upgrade the xml schema (that is, do we have to go back and
edit older documents)?
This is a general pb. Let's assume we change formatting rules for txt
IDs. Then, how do we upgrade to new format ? As for many document
formats, ascendant compatibility is a legitimate expectation, and is
easily granted. When a design flaw from previous models has to be
corrected, then most of the time, it should be easy to move old doc to
the latest model with a batch xsl tranformation; this sometimes happens.
All of these questions would have to
be answered, and answered well enough to satisfy some pretty
demanding people, some of whom are pretty content with the status quo.
Sure.
BTW, note that the xml source actually contains in the clear the content
of the draft. Information can not be lost.
My proposal avoids such discussions. It makes no requirements
other than if xml is submitted, then it SHOULD be in conformance
to 2629.
In my opinion, it MUST be in conformance to 2629 DTD (or later
version). If everyone designs one's own DTD, then the advantages from
sharing the xml source are greatly reduced.
I also think it is MUCH better to start with the I-D archive and
not change the RFC process.
I certainly agree.
Among other things, I-Ds expire.
If this change doesn't work, in 6 months, we can be rid of any
vestiges. RFCs don't expire (although they get obsoleted), and
the time frame is much longer. Let's stick to I-Ds only, please.
Brian
--
Jean-Jacques Puig
[homepage] http://www-lor.int-evry.fr/~puig/