Re: Proposal: Remove the mapping table from AccName "AAM"

+1

On Fri, Nov 17, 2017 at 12:55 AM Léonie Watson <tink@tink.uk> wrote:

> +1 Seems like a good idea to me. Duplicated content is rarely a good thing.
>
>
> On 16/11/2017 20:16, Joanmarie Diggs wrote:
> > Hey all.
> >
> > As was discussed during today's call, I would like to remove the mapping
> > table from AccName "AAM" because:
> >
> > 1. That information is largely already in Core AAM. I see no good reason
> >     to have duplicate information.
> >
> > 2. It would simplify testing of AccName (which hasn't yet entered CR),
> >     both in terms of tests we'd need to write and get results for and in
> >     terms of exit criteria.
> >
> > If you all agree, then I'd also want to tweak the name of the spec so
> > that it no longer contains the "AAM" since the "M" stands for "Mappings"
> > and those would have been removed.
> >
> > Since we need to write tests, get results, and define exit criteria
> > essentially now, having your thoughts on this matter soonish would be
> great.
> >
> > Thanks in advance!
> > --joanie
> >
>
> --
> @LeonieWatson @tink@toot.cafe tink.uk carpe diem
>
> --

Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*

Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>