Re: Definitions, references, and tooltips

I realized this thread got sort of off topic.  What I was really trying to
determine was if anyone wanted ReSpec to continue to leave the 'title'
attribute on dfn elements.  Here is what I have decided:

For legacy purposes, title will continue to work as it always has in
ReSpec.  It influences the way that the definition is referenced, and is
left in place to act as a tooltip.

ReSpec will also support data-dfn-title (or whatever Bikeshed actually
uses) as a way of naming the way the definition can be referenced.  This
will support the Bikeshed syntax that includes 'aliases' for the
definition.

I will also add support for the related data-dfn attributes to ReSpec so
that you can scope your terms, mark them for export or not, and have local
aliases.



On Sunday, November 2, 2014, Tab Atkins Jr. <jackalmage@gmail.com> wrote:

> On Sun, Nov 2, 2014 at 3:05 AM, Shane McCarron <shane@aptest.com
> <javascript:;>> wrote:
> > On Nov 2, 2014 1:11 AM, "Tobie Langel" <tobie.langel@gmail.com
> <javascript:;>> wrote:
> >> > On Nov 1, 2014, at 20:09, "Tab Atkins Jr." <jackalmage@gmail.com
> <javascript:;>> wrote:
> >> > For ReSpec, the document looked at by scrapers is the
> >> > source doc, so feel free to remove from the post-JS document.
> >>
> >> Actually, I'm also writing a scrapper right now, and I look at the
> >> rendered output, not the raw one. So please don't do anything that
> >> would prevent that.
> >
> > To the extent possible. Obviously the rendered output should be valid.
> Or at
> > least very close to valid.
>
> Bikeshed's output is valid HTML, so if you just copy its output format
> (which, per your request, I'm documenting), you'll be fine.
>
> ~TJ
>


-- 
Shane McCarron
Managing Director, Applied Testing and Technology, Inc.