in-line targets in IETF RFCs?

[Dan Connolly]

I've got a draft that I want to publish as an Internet Draft:
  http://www.w3.org/html/wg/href/draft.html

so I'm writing an XSLT transformation from (a dialect
of) XHTML to the IETF's XML format:
  http://bitbucket.org/DanC/urlp/src/tip/wah5/

but I can't find any IETF construct for
  <dfn id="lollypop">Definition: a lollypop is a
   spherical confection</dfn>
  ...
  Place <a href="#lollypop">lollypop</a> in mouth...


The closest I could get was to make each definition
into a figure, but one reviewer (ht) found that
very distracting.
http://www.w3.org/html/wg/href/draft-ietf.html

Help!?

FYI, for context...
toward Internet Draft for URLs in HTML 5
http://lists.w3.org/Archives/Public/public-html/2009Apr/0199.html

and http://www.w3.org/html/wg/tracker/actions/118

--
Dan Connolly, W3C http://www.w3.org/People/Connolly/
gpg D3C2 887B 0F92 6005 C541  0875 0F91 96DE 6E52 C29E

[Julian Reschke]

Dan Connolly wrote:

> I've got a draft that I want to publish as an Internet Draft:
>   http://www.w3.org/html/wg/href/draft.html
>
> so I'm writing an XSLT transformation from (a dialect
> of) XHTML to the IETF's XML format:
>   http://bitbucket.org/DanC/urlp/src/tip/wah5/
>
> but I can't find any IETF construct for
>   <dfn id="lollypop">Definition: a lollypop is a
>    spherical confection</dfn>
>   ...
>   Place <a href="#lollypop">lollypop</a> in mouth...

<t anchor="lollypop">
   Definition: a lollypop is aspherical confection
</t>

(*)

<t>
   Place a <xref target="lollypop">lollypop</xref> in mouth...
</t>

> The closest I could get was to make each definition
> into a figure, but one reviewer (ht) found that
> very distracting.
> http://www.w3.org/html/wg/href/draft-ietf.html

It totally is :-)

> Help!?
 > ...

Hope this helps,

Julian

(*) When using rfc2629.xslt, you may also want to look at:
<http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html#ext.element.dfn>

[Dan Connolly]

On Fri, 2009-05-01 at 15:52 +0200, Julian Reschke wrote:
> [...]...
> >   Place <a href="#lollypop">lollypop</a> in mouth...
>
>
> <t anchor="lollypop">
>    Definition: a lollypop is aspherical confection
> </t>

<t> is a like paragraph, no? I want something *inline*.


--
Dan Connolly, W3C http://www.w3.org/People/Connolly/
gpg D3C2 887B 0F92 6005 C541  0875 0F91 96DE 6E52 C29E

[Julian Reschke]

Dan Connolly wrote:
> On Fri, 2009-05-01 at 15:52 +0200, Julian Reschke wrote:
>> [...]...
>>>   Place <a href="#lollypop">lollypop</a> in mouth...
>>
>> <t anchor="lollypop">
>>    Definition: a lollypop is aspherical confection
>> </t>
>
> <t> is a like paragraph, no? I want something *inline*.

For the reference, or for the reference target?

BR, Julian

[Dan Connolly]

On Fri, 2009-05-01 at 21:15 +0200, Julian Reschke wrote:

> Dan Connolly wrote:
> > On Fri, 2009-05-01 at 15:52 +0200, Julian Reschke wrote:
> >> [...]...
> >>>   Place <a href="#lollypop">lollypop</a> in mouth...
> >>
> >> <t anchor="lollypop">
> >>    Definition: a lollypop is aspherical confection
> >> </t>
> >
> > <t> is a like paragraph, no? I want something *inline*.
>
> For the reference, or for the reference target?

for the target. <dfn> is inline markup.

> BR, Julian
--
Dan Connolly, W3C http://www.w3.org/People/Connolly/
gpg D3C2 887B 0F92 6005 C541  0875 0F91 96DE 6E52 C29E

[Julian Reschke]

Dan Connolly wrote:

> On Fri, 2009-05-01 at 21:15 +0200, Julian Reschke wrote:
>> Dan Connolly wrote:
>>> On Fri, 2009-05-01 at 15:52 +0200, Julian Reschke wrote:
>>>> [...]...
>>>>>   Place <a href="#lollypop">lollypop</a> in mouth...
>>>> <t anchor="lollypop">
>>>>    Definition: a lollypop is aspherical confection
>>>> </t>
>>> <t> is a like paragraph, no? I want something *inline*.
>> For the reference, or for the reference target?
>
> for the target. <dfn> is inline markup.

The RFC2629 vocabulary has been designed with TXT output in mind, so it
really supports references to things for which a description can be
generated automatically (such as "Section 1.2" or "Figure 1").

That being said, with the extensions supported in rfc2629.xslt, you can
put an @anchor almost everywhere (should work on <spanx>, for instance),
  but it won't auto-generate the text for you (so you'll always need
<xref> with text content).

BR, Julian