[xml2rfc] Slides for edu presentation on xml2rfc in Dallas
julian.reschke at gmx.de (Julian Reschke) Tue, 14 March 2006 04:25 UTC
From: "julian.reschke at gmx.de"
Date: Tue, 14 Mar 2006 04:25:58 +0000
Subject: [xml2rfc] Slides for edu presentation on xml2rfc in Dallas
In-Reply-To: <A427D1CE-E02B-4E6D-BE90-1DC57EF1BE58@lurchi.franken.de>
References: <4415FA14.3080202@dial.pipex.com> <44168090.4050001@gmx.de> <44169BDE.4010009@dial.pipex.com> <44169E48.1090000@gmx.de> <Pine.LNX.4.64.0603141333200.27120@netcore.fi> <4416B2C8.2050209@gmx.de> <A427D1CE-E02B-4E6D-BE90-1DC57EF1BE58@lurchi.franken.de>
Message-ID: <4416B60A.2000403@gmx.de>
X-Date: Tue Mar 14 04:25:58 2006
Michael Tuexen wrote: > Julian, > > what is the alternative to > > <references title='Normative References'> > <?rfc include="reference.RFC.1321" ?> > <?rfc include="reference.RFC.2104" ?> > <?rfc include="reference.RFC.2119" ?> > <?rfc include="reference.RFC.2960" ?> > <?rfc include="reference.RFC.3436" ?> > <?rfc include="reference.FIPS.180-1.1995" ?> > </references> > > which I find pretty convenient... > > Best regards > Michael I didn't argue with it being convenient :-). The alternative is...: <!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ <!ENTITY rfc2119 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'> ]> and then.... <references> &rfc2119; </references> Best regards, Julian >From Michael.Tuexen at lurchi.franken.de Tue Mar 14 13:36:05 2006 From: Michael.Tuexen at lurchi.franken.de (Michael Tuexen) Date: Tue Mar 14 04:36:13 2006 Subject: [xml2rfc] Slides for edu presentation on xml2rfc in Dallas In-Reply-To: <4416B60A.2000403@gmx.de> References: <4415FA14.3080202@dial.pipex.com> <44168090.4050001@gmx.de> <44169BDE.4010009@dial.pipex.com> <44169E48.1090000@gmx.de> <Pine.LNX.4.64.0603141333200.27120@netcore.fi> <4416B2C8.2050209@gmx.de> <A427D1CE-E02B-4E6D-BE90-1DC57EF1BE58@lurchi.franken.de> <4416B60A.2000403@gmx.de> Message-ID: <F2F8B573-1C0C-4D4C-9AAD-97B99829AA8F@lurchi.franken.de> Seems to be usable... I'm normally doing copy&paste and then change the number. But I have to change the URL, if the references are moved to a different location, this is not the case with the <?rfc ...> stuff, right? Best regards Michael On Mar 14, 2006, at 1:24 PM, Julian Reschke wrote: > Michael Tuexen wrote: >> Julian, >> what is the alternative to >> <references title='Normative References'> >> <?rfc include="reference.RFC.1321" ?> >> <?rfc include="reference.RFC.2104" ?> >> <?rfc include="reference.RFC.2119" ?> >> <?rfc include="reference.RFC.2960" ?> >> <?rfc include="reference.RFC.3436" ?> >> <?rfc include="reference.FIPS.180-1.1995" ?> >> </references> >> which I find pretty convenient... >> Best regards >> Michael > > I didn't argue with it being convenient :-). > > The alternative is...: > > <!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ > <!ENTITY rfc2119 PUBLIC '' 'http://xml.resource.org/public/rfc/ > bibxml/reference.RFC.2119.xml'> > ]> > > and then.... > > <references> > &rfc2119; > </references> > > Best regards, Julian >
- [xml2rfc] Slides for edu presentation on xml2rfc … Elwyn Davies
- [xml2rfc] Slides for edu presentation on xml2rfc … Julian Reschke
- [xml2rfc] Slides for edu presentation on xml2rfc … Julian Reschke
- [xml2rfc] Slides for edu presentation on xml2rfc … Julian Reschke
- Including references, was: [xml2rfc] Slides for e… Julian Reschke
- [xml2rfc] Slides for edu presentation on xml2rfc … Elwyn Davies
- Including references, was: [xml2rfc] Slides for e… Michael Tuexen
- Including references, was: [xml2rfc] Slides for e… Julian Reschke
- Including references, was: [xml2rfc] Slides for e… Julian Reschke
- [xml2rfc] Slides for edu presentation on xml2rfc … Elwyn Davies
- [xml2rfc] Slides for edu presentation on xml2rfc … Bill Fenner
- [xml2rfc] Using &rfc.number; Bill Fenner