W3C home > Mailing lists > Public > public-aria-editors@w3.org > April 2018

Re: SVG AAM and mpping table script

From: Michael Cooper <cooper@w3.org>
Date: Fri, 13 Apr 2018 17:44:59 -0400
To: Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com>
Cc: "Liam R. E. Quin" <liam@w3.org>, ARIA Editors <public-aria-editors@w3.org>
Message-ID: <b69874c2-9fc6-639b-834e-5da61d6ca47d@w3.org>
On 12/04/2018 11:02 PM, Amelia Bellamy-Royds wrote:
>
>
>     First, what are the broken links you have to Core-AAM? I just
>     checked Core-AAM and it seems I did apply the fix when publishing,
>     so the ids are there on <tr>s. And I just checked SVG-AAM in the
>     master branch (using a Respec snapshot) and don't find broken
>     links to Core-AAM (nor to the others).
>
>
> You're correct, sorry. Core-AAM was showing up as broken links when I 
> was testing the Editor's Draft, but they work for the TR version.  In 
> contrast, HTML-AAM was fine in ED, but not in TR. (Graphics-AAM is 
> broken in both.)
>
>
>     If there is a broken link that is the result of a publication
>     fault, I can ask the webmaster for permission to fix. ...
>
>     I wouldn't want to touch a Candidate Recommendation (though I can
>     ask the webmaster for permission to fix, as for Core-AAM).
>
>
>
> I'd *hope* this would count as a purely technical fix, not a 
> substantive change to the spec.  But either way, I assume its going to 
> require extra work for someone. So if Jason or someone else can fix 
> the script properly first, that's great.
>
> But if you are able to start the process of asking the powers-that-be 
> exactly how to make a fix like this to the published specs, that might 
> help move things forward faster.
I've asked the webmaster for permission to fix this in place for 
graphics-aam. I'll let you know when I have a response. Michael
>
> ~A
>
Received on Friday, 13 April 2018 21:45:03 UTC

This archive was generated by hypermail 2.3.1 : Friday, 13 April 2018 21:45:03 UTC