W3C home > Mailing lists > Public > spec-prod@w3.org > January to March 2010

Re: Proposed W3C Spec Conventions

From: Doug Schepers <schepers@w3.org>
Date: Wed, 17 Feb 2010 16:00:26 -0500
Message-ID: <4B7C58EA.1090004@w3.org>
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, Ian-

Ian Hickson wrote (on 2/17/10 3:36 PM):
> On Wed, 17 Feb 2010, Doug Schepers wrote:
>>
>>  Is this all of them?
>>  [[
>>  dom-InterfaceName-attributeOrMethodName
>>  event-eventname
>>  elementname
>>  attr-elementname-attributename
>>  dom-elementname-attributeOrMethodName
>>  concept-word
>>  InterfaceName
>>  ]]
>
> and just use the whole string for long algorithm names.

Right, thanks.  I assume there's a cut-off point, but that's not vital 
to capture.


>>  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.

Regards-
-Doug Schepers
W3C Team Contact, SVG and WebApps WGs
Received on Wednesday, 17 February 2010 21:00:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:19:16 GMT