RE: RFC production center XML format usage, was: [IAOC] xml2rfc and legal services RFPs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> From: ietf-bounces@xxxxxxxx [ietf-bounces@xxxxxxxx] On Behalf Of Henrik Levkowetz [henrik@xxxxxxxxxxxxx]
> 
> Only errors will prevent an automatic draft submission from going through;
> ignore the warnings and comments to your heart's content for that purpose.

Are you saying that one can order the draft submission process to
continue even if the submission tool considers the draft to violate
idnits?  I had no idea that was possible; I believe (from memory) that
that is not clear from the error output.

> The ratio of gripes against idnits to actual bug reports is getting to
> be a bit annoying; and I'd like to suggest that people either submit
> bug reports, or direct the complaints against the requirements of
> 1id-guidelines.txt rather than against the tool which checks the
> requirements if the problem is that the requirements are too strict.

Based on the user interface principle that each error message should
make it clear what possible next steps are, perhaps your advice
"either submit a bug report about the tool or direct a complaint
against the requirements of 1id-guidelines.txt [give link]" should be
provided in any message that the idnits-checker has rejected a draft.
It would probably reduce the number of non-useful gripes.

"There is a Toyota in the driveway.  I am holding the keys in my hand.
What do I do next?"

Dale
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf


[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]