[xml2rfc] Slides for edu presentation on xml2rfc in Dallas

elwynd at dial.pipex.com (Elwyn Davies) Tue, 14 March 2006 10:07 UTC

From: "elwynd at dial.pipex.com"
Date: Tue, 14 Mar 2006 10:07:50 +0000
Subject: [xml2rfc] Slides for edu presentation on xml2rfc in Dallas
In-Reply-To: <4416F1C5.6050508@att.com>
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> <4416F1C5.6050508@att.com>
Message-ID: <44170701.9020901@dial.pipex.com>
X-Date: Tue Mar 14 10:07:50 2006

You need an entity definition for *each* reference

    <!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
       <!ENTITY rfc2119 PUBLIC ''
    'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
       <!ENTITY rfc2045 PUBLIC ''
    'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2045.xml'>
       <!ENTITY rfc2822 PUBLIC ''
    'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2822.xml'>
       <!ENTITY rfc3028 PUBLIC ''
    'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3028.xml'>
       <!ENTITY rfc2047 PUBLIC ''
    'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2047.xml'>
    ]>

/elwyn

Tony Hansen wrote:
> I tried converting a document from using <?rfc include...>.
>
> My DOCTYPE looks like
>
>     <!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
>        <!ENTITY rfc2119 PUBLIC ''
>     'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
>     ]>
>
> and my <references> looks like:
>
>     <references title="Normative References">
> 	&rfc2045;	<!-- mime part 1 -->
> 	&rfc2047;	<!-- mime part 3 -->
> 	&rfc2119;	<!-- keywords -->
> 	&rfc2822;	<!-- message format -->
>         &rfc3028;	<!-- sieve -->
>     </references>
>
> Now I get an error message like this:
>
>     Unable to Convert File
>
>     can't read "xref(RFC3028)": no such element in array around input
>     line 69
>
>     Context (format:  "file_basename:line_in_file:#elem_num:<elem
>     ...>"):
>         CGI16048.2:66:#38:<t>
>         CGI16048.2:65:#37:<section title="Introduction">
>         CGI16048.2:64:#36:<middle>
>         CGI16048.2:11:#1:<rfc ipr="full3978" category="std"
>     docName="draft-ietf-sieve-mime-loop-01.txt">
>
> The reference there looks like
>
>     <xref target="RFC3028" />
>
> Where am I doing something wrong?
>
> 	Tony Hansen
> 	tony@att.com
>
> Julian Reschke wrote:
>   
>> 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>
>>     
>
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@lists.xml.resource.org
> http://lists.xml.resource.org/mailman/listinfo/xml2rfc
>   
>From dworley at pingtel.com  Tue Mar 14 14:08:38 2006
From: dworley at pingtel.com (Dale R. Worley)
Date: Tue Mar 14 11:08:46 2006
Subject: [xml2rfc] Error traceback
In-Reply-To: <441607FE.3070204@dial.pipex.com>
References: <4414774D.4030408@dial.pipex.com>
	 <1142192781.2561.6.camel@cdhcp139.pingtel.com>
	 <44148413.3050007@dial.pipex.com>
	 <1142287701.4729.38.camel@cdhcp139.pingtel.com>
	 <441607FE.3070204@dial.pipex.com>
Message-ID: <1142363318.17936.12.camel@cdhcp139.pingtel.com>

On Tue, 2006-03-14 at 00:02 +0000, Elwyn Davies wrote:
> Hopefully Charles Levert will fix up the error if it isn't already 
> mended in the experimental 1.31 release, but in the meantime ...
> Are you aware of the bibliographic citation libraries?
> 
> These can save you a whole raft of typing for RFC and I-D refs.. see 
> either the bottom of the xml2rfc web page or slides 55 onwards of the 
> slide pack I just posted a pointer to on the mailing list.

OK, thanks, I'll probably use those for RFC references.

> BTW Two points about the source below:
> - If you are hand crafting references, you can omit the <format> element 
> - it is never displayed and is optional

I assume <format> is used to generate a link in the HTML version, and
some sort of pointer to the URL in the text version.  Else, what is it
for?

> - Author elements have a required component 'organization' - but it can 
> be empty in references if there is a person author.

> (Also the fragment has no author in the main front element.)

True, but I didn't need <author> for my test case.

Dale