[rfc-i] Referencing RFCs

Heather Flanagan (RFC Series Editor) rse at rfc-editor.org
Tue Jun 13 13:49:37 PDT 2017


On 3/11/17 7:04 AM, Julian Reschke wrote:
> <https://tools.ietf.org/html/draft-flanagan-7322bis-00#section-4.8.6.2>:
> 
>>    [RFC3080] Rose, M., "The Blocks Extensible Exchange Protocol Core,"
>>    IETF, RFC 3080, DOI 10.17487/RFC3080, March 2001, http://www.rfc-
>>    editor.org/info/rfc3080 .
> 
> I see two chaanges from RFC 7322 here:
> 
> 1) The addition of the stream name (which I believe is a good change).
> In V3, this could be implemented using (a)
> <https://greenbytes.de/tech/webdav/rfc7991.html#element.refcontent> or
> (b) using
> <https://greenbytes.de/tech/webdav/rfc7991.html#element.seriesInfo.attribute.stream>:
> 
> 
> a) would look like:
> 
> <reference  anchor='RFC3080'
> target='http://www.rfc-editor.org/info/rfc3080'>
>   <front>
>     <title>The Blocks Extensible Exchange Protocol Core</title>
>     <author initials='M.' surname='Rose' fullname='M. Rose'/>
>     <date year='2001' month='March' />
>   </front>
>   <refcontent>IETF</refconfent>
>   <seriesInfo name='RFC' value='3080'/>
>   <seriesInfo name='DOI' value='10.17487/RFC3080'/>
> </reference>
> 
> b) would look like:
> 
> <reference  anchor='RFC3080'
> target='http://www.rfc-editor.org/info/rfc3080'>
>   <front>
>     <title>The Blocks Extensible Exchange Protocol Core</title>
>     <author initials='M.' surname='Rose' fullname='M. Rose'/>
>     <date year='2001' month='March' />
>   </front>
>   <seriesInfo name='RFC' value='3080' stream='IETF'/>
>   <seriesInfo name='DOI' value='10.17487/RFC3080'/>
> </reference>
> 
> Both format require changes to the citations library.
> 
> Format (b) has the drawback of being ambiguous, because multiple
> seriesInfo elements might carry conflicting information. We'd also have
> to define the special cases, both for the vocabulary (what if a W3C
> document says stream="IETF"???) and the HTML spec.
> 
> 2) The URI appears without angle brackets. I'll guess that's a
> formatting error caused by xml2rfc not processing the <eref> in the
> source as intended.
> 

We can't use submissionType because it's not allowed in <reference>?

-Heather


More information about the rfc-interest mailing list