On Thu Mar 18 03:27:30 2010, Phillip Hallam-Baker wrote:
That would meet most of my issues, provided of course that the
XML2RFC
format was published.
There's a rfc2629bis at/as
http://xml.resource.org/authoring/draft-mrose-writing-rfcs.html
Is there anything you feel that's not covering? (I agree much of
http://xml.resource.org/authoring/draft-mrose-writing-rfcs.html#anchor19
is now in such common usage a formal I-D submission would be useful).
Zero time spent going to an editable format is better than any
amount
of 'easy conversion'.
Indeed.
On Wed, Mar 17, 2010 at 9:03 PM, Tony Hansen <tony(_at_)att(_dot_)com> wrote:
> +1
>
> On 3/17/2010 12:18 PM, John R. Levine wrote:
>>
>> If we could agree that the final XML was authoritative, and if
>> necessary let them hire someone to fix xmlrfc so it can produce
the
>> text version without hand editing or postprocessing, that would
be a
>> big step forward.
I'm in agreement 99%.
I just think we've accumulated a lot of working experience with XML
editing forms both in the IETF and elsewhere, and it'd be useful to
attempt to consolidate that at this point in time before moving to
full adoption.
Dave.
--
Dave Cridland - mailto:dave(_at_)cridland(_dot_)net -
xmpp:dwd(_at_)dave(_dot_)cridland(_dot_)net
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
- http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf