[rfc-i] xref extensions

[ietf at augustcellars.com (Jim Schaad)]

> -----Original Message-----
> From: Julian Reschke [mailto:julian.reschke at gmx.de]
> Sent: Thursday, November 06, 2014 9:45 PM
> To: Jim Schaad; rfc-interest at rfc-editor.org
> Subject: Re: [rfc-i] xref extensions
> 
> On 2014-11-06 12:37, Jim Schaad wrote:
> > After reading this, I guess I am going to post my latest wish list item.
> >
> > I would like to propose the following addition to the v3 vocabulary.
> >
> > 1) define a new element <anchorSet> to be a child of reference.  The
> > element is for grouping and has no attributes.
> > 2) define a new element <anchorPoint> to be a child of <anchorSet>.
> > Multiple elements can occur here.
> >      It has the following attributes:
> > 	anchorName - the name of the anchor begin exposed in the
> referenced
> > document
> > 	partNumber - the partNumber of the anchor being exposed in the
> > referenced document
> > 	text - what is generated for the "default" format of xref for the
> > anchor being exposed
> >      An xml2rfc processor that generates reference.xml output would
> > generate these as part generated reference item.
> >
> > 3) augment xref by adding a new attribute that allows one to say <xref
> > target="RFC99" anchorName="foo"/>.
> >
> >
> > The above would allow one to use the anchor points defined in one
> > document in a second document.  This would be especially useful when
> > one is writing sets of documents that are going to make references
> > back and forth between them.  Doing so would require that xml2rfc be
> > run twice, the first time to generate the reference.xml document and
> > then the actual document to be created (txt, xml, html, ebook).
> 
> I've been doing this for quite some time using
> <http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html#ext-
> rfc2629.xref>.
> For instance, from my RFC 7230's XML:
> 
>    <xref target='RFC7234' x:rel='#caching.overview'/>
> 
> In V3 this would be:
> 
>    <xref target='RFC7234' relation='#caching.overview'/>

Yes, but this does not the "Section 2 of [RFC7234]' in the text
automatically, but cause it does not know it is section 2.


Jim

> 
> Best regards, Julian