- From: Doug Schepers <schepers@w3.org>
- Date: Sun, 21 Feb 2010 16:44:48 -0500
- To: Ian Hickson <ian@hixie.ch>
- CC: Anne van Kesteren <annevk@opera.com>, Spec Prod <spec-prod@w3.org>, Geoffrey Sneddon <gsneddon@opera.com>
Hi, Folks- I started writing this up in the spec conventions document, but stalled when I tried to provide a rationale for using these codes. I like the idea of using @title, but aren't these values a bit cryptic for the final output? For the authoring syntax, these may be short and convenient, but there doesn't seem to much utility in presenting that to authors... couldn't the processing script expand that into something a bit more... decoded? Regards- -Doug Schepers W3C Team Contact, SVG and WebApps WGs Ian Hickson wrote (on 2/17/10 4:11 PM): > On Wed, 17 Feb 2010, Doug Schepers wrote: >> > > >> > > What's the example usage here? Like, for @bar of<foo>, is this right? >> > > >> > > <a href="#foo-element" title="foo"><code class="element">foo</code></a> >> > >> > In the source (before running anolis) this would just be: >> > >> > <code>foo</code> >> > >> > ...because the title="" can be omitted if it matches the element's >> > textContent. >> >> Makes sense. >> >> >> > > <a href="#bar-attribute" title="attr-foo-bar><code >> > > class="attr">bar</code></a> >> > >> > This would just be: >> > >> > <code title="attr-foo-bar">bar</code> >> > >> > Anolis takes care of making all the cross-references (<a>s). >> >> Right. I'm most interested (for this document) in the resulting markup, >> rather than the tool-specific inputs. > > Ah, ok. > > For the first: > > <code><a href=#autogeneratedid>body</a></code> > > For the second: > > <code title=attr-foo-bar><a href=#autogeneratedid2>bar</a></code> > > The auto-generated IDs should probably have some correlation with the text > near the corresponding<dfn>, so as to be more stable; for example, using > the "title" attribute if there is one. >
Received on Sunday, 21 February 2010 21:44:52 UTC