Re: WAI glossary start

The current respec strategy is to export definitions from the specs which really should own the definitions and remove from all other places. ARIA is currently doing the following - this is in PR Editorial: remove conflicting exports by marcoscaceres · Pull Request #1510 · w3c/aria (github.com)<https://github.com/w3c/aria/pull/1510> :

  *   moving all definitions from the common central location to the relevant specs (most in ARIA and a couple in ACCNAME and COREAAM)
  *   Removes definitions for things that didn't need to be defined or things that sere not used (examples below):
     *   Class (remove references to this)
     *   Informative (remove references to this)
     *   Primary Content Element (was not used)
     *   Normative (remove references to this)
     *   Root WAI-ARIA Node (was not used)
     *   Sub-document (was not used)
     *   Taxonomy (was not used)
     *   Text Node (was only used in definition of Node)
     *   Understandable (was not used)
     *   Valid IDREF (does not need to be defined - remove references to it)
  *   Removes definitons for things which should have been defined elsewhere and uses those definitions instead:
     *   Attribute (refer instead to [=attribute=] concept)
     *   DOMString (allow to reference WebIDL)
     *   Element (refer to [=element=] concept
     *   Node (remove reference or reference [=nodes=] concept if a DOM node)
     *   User Agent (refer to [=user agent=] concept

I would encourage this work to be done in consultation with Marcos as he will have opinions on the best way to make this type of thing work with the tooling.

If folks don't know w3c manual of style - Bing (respec.org)<https://respec.org/xref/> can be used to look up any definition that has been exported from other specs and tells you how to refer to that definition in a respec document.
Search cross references - ReSpec<https://respec.org/xref/>
Search for a term... Specification Spec id Type How to Cite? Data from WebRef.. Last updated: .....
respec.org
Regards,
James
________________________________
From: Janina Sajka <janina@rednote.net>
Sent: Thursday, September 16, 2021 5:16 PM
To: Katie Haritos-Shea <ryladog@gmail.com>
Cc: Michael Cooper <cooper@w3.org>; WAI Coordination Call <public-wai-cc@w3.org>
Subject: Re: WAI glossary start

Hi, Katie:

I think the proposal is to come up with a plan to adopt those
definitions we can use, and toss the rest.

We will, of course, also need to come up with procedures to add terms to
a joint glossary, and we'll need some process of quality control for
those. So, ongoing maintenance will need to be part of any useful
general glossary project.

All the above is over and beyond any tech we adopt to store our
definitions, date them, sign off on them, and use them in our documents,
I suppose via id href.

Best,

Janina

Katie Haritos-Shea writes:
> Michael,
>
> This is great news. Long ago U did such a thing, but it is obnoxiously
> outdated
>
> On Thu, Sep 16, 2021, 10:13 AM Michael Cooper <cooper@w3.org> wrote:
>
> > I have an action in WAI-CC to get a start on a WAI-wide Glossary. I've
> > compiled glossaries from all the WAI documents I knew about and sorted them
> > to allow comparison of terms, with indication of each term's source. The
> > result is, for now, at:
> >
> >
> > https://docs.google.com/document/d/1MDW5ja90OVuCSbirmOLfKcnHdgEKOUvqFy5icPwGsdY/edit?usp=sharing
> >
> > There is additional information and suggested next steps at the top of the
> > document. I think this is ready for review at an upcoming WAI-CC meeting.
> >
> > As far as a tool in which to host the glossary, I don't yet have a
> > proposal. The respec data-export feature and the webref database looked
> > like a central W3C glossary emerging, but the documentation is clear it's
> > only for "browser specs". But I'm sure we'll be able to sort that side
> > without too much difficulty.
> >
> > Michael
> >
> >
> >

--

Janina Sajka
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:       http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures     http://www.w3.org/wai/apa