Re: definitions and aliasing

On Thu, Jul 9, 2015 at 2:11 PM, Shane McCarron <shane@aptest.com> wrote:
> On Jul 9, 2015 3:14 PM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote:
>> On Thu, Jul 9, 2015 at 12:16 PM, Shane McCarron <shane@aptest.com> wrote:
>> > Last October I did a ton of work implementing much of the Bikeshed
>> > definition aliasing stuff (so we could say <dfn title="the term|the
>> > terms|term|terms">The Term</dfn> and then references like <a>the
>> > terms</a>
>> > would just work.
>> >
>> > I somehow lost all that work, so I am starting again.
>> >
>> > I noticed that bikeshed has changed its attribute for the 'title' of a
>> > definition from 'title' to 'lt' and 'local-lt' (for a definition that
>> > shouldn't be exported).  I intend to implement this in baby steps.  I
>> > need
>> > the aliasing stuff RIGHT NOW.  I don't need the rest immediately.
>> >
>> > Anyway, we *must* keep support for @title because it would break every
>> > document if we did not.  My question is "should we also support @lt and
>> > @local-lt?"  A secondary question is "should we deprecate @title in
>> > favor of
>> > @lt?"
>>
>> When Bikeshed made the switch, I just turned off @title handling
>> entirely, and logged a warning message if I saw an <a> or <dfn> with
>> @title but not @lt.  People switched quickly, since it was an easy
>> search-and-replace.
>
> Sure, but since respec is client side and there are live specs that use it
> and are end user facing we need to be careful with that.

Are people embedding a tip-of-tree ReSpec link?

~TJ

Received on Thursday, 9 July 2015 21:36:42 UTC