Ned Freed wrote:
> ...
> Another potential problem is that document generation from XML source may
> involve more than just running xml2rfc. Some documents are built up from
> multiple files in complex ways that cannot easily be duplicated by the I-D
> manager.
> ...
That's true. But at some point of time, XML source *was* fed into
xml2rfc, right?
Sure, but what about things like locally defined entity references? xml2rfc
handles these but they create an external reference that has to be there
alongside the main source.
I would argue that *that* XML source should be
submitted; submitting something that needs additional non-standard
preprocessing seems a bit pointless to me.
*That* XML source is still not necessarily self-contained. Indeed, one
model I've seen people use is to preprocess included materials but not
the main XML source.
> Only when the document is finished does it make sense to generate a
> self-contained XML source for it.
I don't agree with that.
Then you need to provide a viable alternative, because what you're suggesting
isn't compatible with how some people use the tools.
But anyway, if you think it doesn't make sense to generate
self-contained XML for each I-D, why submit the non-self-contained XML
source at all?
Obviously you don't submit XML source up until that point.
Ned
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf