Brainstorming .. how to get rid of aria-common

[jnurthen]

No description provided.

[jnurthen]

file	where used	proposed solution
acknowledgements/aria-contributors.html	core-aam, css-aam, aria, mathml-aam, accname
acknowledgements/aria-wg-active.html	core-aam, css-aam, aria, mathml-aam, accname
acknowledgements/aria-participants.html	unused?	remove
acknowledgements/funders.html	math-aam, math-aria, css-aam, graphics-aam, aria, css-aam, mathml-aam, graphics-aam, accname, dpub-aam, graphics-aria, pub-aria, svg-aam, core-aam, html-aam
css/common.css
css/editors.css	none?
css/mapping-tables.css	css-aam, graphics-aam, mathml-aam, dub-aam, svg-aam, html-aam, core-aam
css/slices.css	none?
img/downArrow.png	used in mapping-tables.css
img/rightArrow.png	used in mapping-tables.css
script/aria.js	aria	move to aria
script/ariaChild.js	math-aria, graphics-aria, annotation-aria, pub-aria	host somewhere
script/jquery-1.9.0.min.js		remove - no longer needed
script/jquery.details.min.js	css-aam, graphics-aam, mathml-aam, dub-aam, svg-aam, html-aam, core-aam
script/mapping-tables.js	css-aam, graphics-aam, mathml-aam, dub-aam, svg-aam, html-aam, core-aam
script/resolveReferences.js	math-aam, math-aria, css-aam, graphics-aam, mathml-aam, accname, annotation-aria, dub-aam, graphics-aria, svg-aam, dpub-aria, html-aam, core-aam, aria-practices	host somewhere
script/roleInfo.js	as ariaChild	host somewhere
script/utility.js	accname, core-aam
utility/aria-taxonomy.xml		remove
utility/aria-taxonomy.xml.zargo		remove
utility/roleXMlgenerator.xslt		remove
acknowledgements.html		remove
biblio.js	everything	host or eliminate?
terms.html		merge into specs

[pkra]

@jnurthen @daniel-montalvo a perhaps bold suggestion: could we move the useful/used bits into aria?

A quick review of James's table:

• acknowledgments folder: seems to be all about the WG, so the aria repository seems reasonable (just like we have onboarding information there)
• css folder: only common.css and mapping-tables.css seem to be used.
  • common.css has seen very little activity; does it matter where it's located?
  • mapping-tables.css could probably use some cleanup and integration into common.css
• js folder
  • ariaChild.js looks like an out of date copy of aria.js. It's used in repos that haven't seen (real) updates in quite a while so perhaps it's actually not used?
  • query.details is a summary/details shim - do we really need it in 2023? It also seems to have gone from several repos now.
  • mapping-table.js - could probably use some love and also seems like it wouldn't look out of place in the aria repository
  • resolveReferences.js: as a coordinating component seems to fit well in the aria repository
  • roleInfo - generated and like aria-child.js used in out-of-date specs. Is it still relevant?
  • utility.js - looks like an aam specialty. Since it deals with maintainers and bots, it seems like a good fit for the aria repository. (We might want to give it a better name to associate it with AAMs.)
• biblio.js - again, seems like a good fit in the aria repository if it's still needed
• terms.html - IIRC this has already been merged into the specs.

[pkra]

I filed w3c/core-aam#171.

[pkra]

I think only html-aam uses respec's gh-contributors and I think the hack in utility.js is no longer needed.

I think the history is

• Use auto imported aria-common scripts, fix mapping table duplication and ids! html-aam#406 triggered this
• @jnurthen added the hack in utility.js in remove bots from contributors list #85 and remove bots from contributors list #86
• @jnurthen also filed https://github.com/w3c/respec/issues/4169
• @jnurthen fixed that a month later in https://github.com/w3c/respec/pull/4195

So I think that part can go and the rest can be inlined into core-aam (cf. core-aam issue 171).

[pkra]

So I think that part can go and the rest can be inlined into core-aam (cf. core-aam issue 171).

Obviously needs testing.

[spectranaut]

I'll be working on removing mapping-tables.js -- I started writing a script to translate the giant tables to summary/details but I'm not sure I'll get back to it before the F2F, with other work things on my plate. We will see!

[pkra]

Thanks @spectranaut!