- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Fri, 01 May 2009 21:39:06 +0200
- To: Dan Connolly <connolly@w3.org>
- CC: "Henry S. Thompson" <ht@inf.ed.ac.uk>, spec-prod <spec-prod@w3.org>
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
Received on Friday, 1 May 2009 19:39:59 UTC