Re: definitions and aliasing

Okay - I was implementing this warning, and a side issue arose (shocking, I
know).

We use @title on abbr and acronym to provide an expanded title for all
matching abbr and acronyms.  Which is great.  When this appear in a dfn,
the dfn also inherits their @title (e.g., <dfn><abbr title="My Long
Term">MLT</abbr></dfn>).  I feel like this is a correct use of @title, and
therefore should not require a warning.  I also feel like if people want to
have aliases for this, they should do it using @lt on the dfn element.
Any objections to encouraging that behavior in the documentation?

On Fri, Jul 17, 2015 at 10:58 AM, Shane McCarron <shane@aptest.com> wrote:

> Yeah - I didn't mean tip-of-tree.  But lots of people use the latest
> release.  And they do so in production documents, not just Editor's Drafts.
>
> I like the idea of doing a warning on Title use when there is no @lt.  I
> will see about adding that.  I have an updated pull request.  Maybe I can
> squeeze it into that.
>
> On Fri, Jul 17, 2015 at 4:54 AM, Robin Berjon <robin@w3.org> wrote:
>
>> On 09/07/2015 23:35 , Tab Atkins Jr. wrote:
>>
>>> Are people embedding a tip-of-tree ReSpec link?
>>>
>>
>> Almost no one uses tip-of-tree. That's really only if you're working on
>> ReSpec code, and even then you wouldn't use it for anything other than a
>> test document — outside of a build it's way too slow.
>>
>> But everyone uses the latest release. That's the point at which
>> deprecation warnings start showing up everywhere. I think that's okay.
>>
>>
>> --
>> Robin Berjon - http://berjon.com/ - @robinberjon
>>
>
>
>
> --
> Shane McCarron
> Managing Director, Applied Testing and Technology, Inc.
>



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