Re: SVG Accessibility API Mapping Specification

Hi Doug -

Great that this is ready to go. First question is, will you push the 
publication process through, or will I? We need to coordinate either way 
but exactly how might vary.

Here's what I understand needs to be done, in rough order:

 1. Review the Abstract and perhaps make editorial edits to help make
    sure it's a clear and concise description of the document. I usually
    do this as a Team task but run it by the group to make sure they
    don't disagree with my proposed edits. The Abstract is part of the
    Transition Request for FPWD and does get looked at closely.
 2. Prepare the Status of This Document for the publication (which I do
    this and subsequent steps in a branch so the main editors' draft
    doesn't show stuff that is only intended for the TR version). Beyond
    the boilerplate added by Respec, this should have a clear
    description of the goals of this particular publication, and a set
    of review questions we want public feedback on. This also is part of
    the Transition Request and important to pass Domain Lead review.
 3. Determine how public comments are enabled. I'm assuming you want to
    use the task force mailing list, public-svg-a11y@w3.org, as the
    comments list (although this is different from how my groups
    normally do it). Also will you be offering any Bugzilla or other
    comment tracker tools? I assume no, but some groups do. The other
    ARIA specs do reference Bugzilla, so I would normally including
    instructions for filing a bug for that (e.g., see
    http://www.w3.org/TR/accname-aam-1.1/, just updating the component
    in the link to be "SVG%20AAM").
 4. Sort out the Acknowledgements. Right now this document is pulling a
    boilerplate acknowledgements suitable for PF-only publications;
    we'll need to update this to reflect the SVG participants as well. I
    suggest a single sub-section entitled "Participants in the SVG
    Accessibility Task Force active at the time of publication", and
    we'll need to come up with the list of people to credit. We may also
    want to credit at least active members of the PF and SVG Working
    Groups, and we might also want to do special credits. It's also
    important that the "Enabling funders" section remain, and I'll need
    to double-check that it is current (though I think so).
 5. Prepare the Transition Request. I think in this case it has to go to
    Judy Brewer (WAI Domain Lead) and Philippe Le Hégaret (Interaction
    Domain Lead), and that we need formal assent from both of them.
 6. Draft announcements. WAI is very formal about this and announces to
    more places than other W3C groups, I think. We have at least a week
    review cycle on this before publication. Are there any
    considerations on this front for SVG?
 7. Stage the document for publication and run the publication checks,
    and fix issues found. For me this is usually broken links, and
    sometimes HTML validator fixes.
 8. Draft the publication request, including in particular the brief
    "description" for the TR pages, which I usually take from the Abstract.
 9. Send the publication request, and make sure the doc gets published.
10. Update relevant pointers on the PF and SVG WG pages.

The first two steps I think we need to be coordinated on, as well as 
step 4. I can take a first stab at those edits to the abstract and 
status, since the WAI Domain has the (in my experience) higher review 
requirements on those. Of course I would run those edits by you and the 
TF. Unless SVG has specific practices for doing announcements, I should 
probably lead that step, coordinating with you, since it requires great 
care in WAI to get the approval to go ahead.

The rest of the steps I think are easiest done by one or the other of us 
(except step 10 which we would each do for our group). Do you have a 
preference, do you want to run the publication process through, or do 
you want me to? As long as we're well coordinated I don't have a 
preference. Because this is part of a suite of other PF deliverables it 
may be easier for me to do it, using templates from similar 
deliverables, but if you want to do it yourself that's fine.

Michael


On 11/02/2015 6:48 PM, Doug Schepers wrote:
> Hi, Michael–
>
> I'd like to coordinate with you on this publication so I know what 
> steps are needed to satisfy the WAI requirements.
>
> Regards–
> –Doug
>
> On 2/11/15 5:59 PM, Richard Schwerdtfeger wrote:
>> Hi Michael,
>>
>> I was on the SVG working group call this evening and the SVG working
>> group resolved to move the SVG Accessibility API Mappings specification
>> to First Public Working Draft.
>>
>> http://rawgit.com/w3c/aria/master/svg-aam/svg-aam.html
>>
>> That completes the approvals by PF, SVG, and the SVG Accessibility Task
>> Force. So, I leave the publication in your good hands.
>>
>> Please make sure that the participants in the latest SVG working group
>> and and the PF working group are included in the acknowledgements.
>>
>> I would like to give a special thanks to Joseph Scheuhammer for doing
>> the lion share of the effort to refactor the Core and Name computation
>> accessibility API mapping specifications that made the development of
>> this spec much easier.
>>
>> This is a major step forward for SVG accessibility.
>>
>> Best,
>> Rich
>>
>>
>> Rich Schwerdtfeger
>>
>