Including references, was: [xml2rfc] Slides for edu presentation on xml2rfc in Dallas

[julian.reschke at gmx.de (Julian Reschke)]

Michael Tuexen wrote:
> Well, I have to be more precise...
> 
> Since I can not reference old IDs, I always have to reference the latest 
> version.
> I, at least this is what I think, I have to check if the contents is 
> still that
> way I was referring to. Sometimes, procedures, packets or something else 
> gets
> deleted or modified....

Exactly. That's why any kind of automatic update of a reference is 
dangerous. Automatic *checking* is good, though.

Best regards, Julian
>From tony at att.com  Tue Mar 14 15:29:55 2006
From: tony at att.com (Tony Hansen)
Date: Tue Mar 14 12:30:08 2006
Subject: [xml2rfc] Slides for edu presentation on xml2rfc in Dallas
In-Reply-To: <[e-mail]>
References: <[e-mail]> <[e-mail]>
	<[e-mail]> <[e-mail]>
	<[e-mail]> <[e-mail]>
	<[e-mail]>
	<[e-mail]> <[e-mail]>
	<[e-mail]>
Message-ID: <[e-mail]>

Aha, that's the magic I was missing. So instead of the single <?rfc
include/> line, we now have to put in *two lines* for each RFC.

I missed that as part of the cookbook on this one.

	Tony Hansen
	[e-mail]

Elwyn Davies wrote:
> 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
>>     [e-mail]
>>
>> 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
>> [e-mail]
>> http://lists.xml.resource.org/mailman/listinfo/xml2rfc
>>   
>From elwynd at dial.pipex.com  Tue Mar 14 20:49:46 2006
From: elwynd at dial.pipex.com (Elwyn Davies)
Date: Tue Mar 14 12:47:28 2006
Subject: [xml2rfc] Slides for edu presentation on xml2rfc in Dallas
In-Reply-To: <[e-mail]>
References: <[e-mail]> <[e-mail]>
	<[e-mail]> <[e-mail]>
	<[e-mail]> <[e-mail]>
	<[e-mail]>
	<[e-mail]> <[e-mail]>
	<[e-mail]> <[e-mail]>
Message-ID: <[e-mail]>

Yes: Unfortunately it appears that the price of creating generic XML as 
opposed to using an xml2rfc specific capability is that we get to type 
the number three times.  On the other hand it would be easy enough to 
write a script to do it!

/Elwyn

Tony Hansen wrote:
> Aha, that's the magic I was missing. So instead of the single <?rfc
> include/> line, we now have to put in *two lines* for each RFC.
>
> I missed that as part of the cookbook on this one.
>
> 	Tony Hansen
> 	[e-mail]
>
> Elwyn Davies wrote:
>   
>> 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
>>>     [e-mail]
>>>
>>> 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
>>> [e-mail]
>>> http://lists.xml.resource.org/mailman/listinfo/xml2rfc
>>>   
>>>       
> _______________________________________________
> xml2rfc mailing list
> [e-mail]
> http://lists.xml.resource.org/mailman/listinfo/xml2rfc
>   
>From dbharrington at comcast.net  Tue Mar 14 16:54:33 2006
From: dbharrington at comcast.net (David B Harrington)
Date: Tue Mar 14 13:54:54 2006
Subject: [xml2rfc] Slides for edu presentation on xml2rfc in Dallas 
In-Reply-To: <[e-mail]>
Message-ID: <0a6301c647b1$e15c3da0$[e-mail]>

FYI. I am developing an xml2rfc template for documents containing MIB
modules, with all the necessary boilerplates and sections, plus hints
and tips about xml2rfc usage.

David Harrington
MIB Doctor
[e-mail] 

> -----Original Message-----
> From: [e-mail] 
> [mailto:[e-mail]] On Behalf Of Elwyn Davies
> Sent: Monday, March 13, 2006 6:03 PM
> To: xml2rfc mailing list
> Subject: [xml2rfc] Slides for edu presentation on xml2rfc in Dallas 
> 
> 
> Hi.
> 
> I have created a set of slides based fairly heavily on the flow of 
> material in RFC2926bis plus the xml2rfc README and then  
> larded with my 
> own and other peoples' experiences in the hints and tips.
> 
> I'd appreciate any comments on the set of slides which can be 
> downloaded 
> from
> http://psg.com/~avri/ietf/edu/xml2rfc-10.ppt
> or
> http://psg.com/~avri/ietf/edu/xml2rfc-10.pdf
> according to taste.
> 
> I am also creating a new and larger template file that I hope will
be 
> useful.
> 
> Regards,
> Elwyn
> _______________________________________________
> xml2rfc mailing list
> [e-mail]
> http://lists.xml.resource.org/mailman/listinfo/xml2rfc
>