[rfc-i] Embedding stuff (code, etc.) in RFCs

Julian Reschke julian.reschke at gmx.de
Fri Jul 12 13:36:08 PDT 2013


On 2013-07-12 21:57, Nico Williams wrote:
> On Fri, Jul 12, 2013 at 11:39 AM, Dearlove, Christopher (UK)
> <chris.dearlove at baesystems.com> wrote:
>> The .txt is the definitive RFC, so extracting from that has its advantages.
>
> Yes.  See RFC5662 for an example of how to do this reliably.
>
>> Perhaps we should have a <code> or whatever in the XML, and then xml2rfc to map that to something distinctive, plus a tool to pull the distinctive text out of the .txt, while extracting the code from <code> ... </code> in the XML would be trivial.
>
> The <figure><artwork> tags, with the 'type' attribute of <artwork>,
> should suffice -- certainly when consuming the XML (it should be
> trivial to extract artwork using XSLT).  xml2rfc could grow a new PI

<http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html#extract-artwork>

> by which to indicate whether (and how) to "quote for extraction"
> artwork of specific types, or perhaps this should be a new attribute
> for <artwork>.
>
> Nico
> --
> _______________________________________________
> rfc-interest mailing list
> rfc-interest at rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
>



More information about the rfc-interest mailing list