Meeting minutes
<janina> brb
BCI Registry Specification
Commissions Workshop
Lionel_Wolberger: permissions workshop out of scope for this committee
BCI Registry Specification
janina: we have a call for consensus next Monday on the 28th on the Registry spec.
Lionel_Wolberger: did you get to the process ?
janina: thats in the adapt spec and yes I did. Messaging for both specs are in the works.
… , WAI- message how to comment, write it once and pull it in. There are 3 files both reg & adapt spec. TWEET / News item and / WAI- Announce messaging
… , Matt, Michael and Roy will talk and pass it onto Shawn.
… , we have 2 weeks to get this out.
Short name for the module, 'adapt-symbols' or 'adapt-symbol'
Lionel_Wolberger: Timebox for 3 min. Can we get a decision?
janina: I believe it is called Symbols.
Lionel_Wolberger: Anyone see we should call it adapt-symbol?
… , no objections, this is closed
Adapt Symbols Module Status
<janina> https://
Lionel_Wolberger: Module is done. Renamed, process section is done.
janina: questions on 2 sections, rewrote the conformance section.
From the Spec:
3. Conformance
As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.
The key words MAY and MUST in this document are to be interpreted as described in https://
This section is normative.
The content of WAI-Adapt Symbols consists of numeric values for the adapt-symbol attribute for any span of text and taken from the https://
nd there is no minimum.
janina: Section before "Properties" is this relevant to Symbols or is this a leftover?
… , one just attribute adapt-symbol.
Lionel_Wolberger: The entire section 1.3 should be removed.
Janina: in the registry spec defines 1 or more symbols.
matatk: I don't think we need 1.3 this is duplicative in the registry.
janina: I agree its defined more clearly in the Registry Spec.
… , there is a vocabulary section 4. is this section needed?
matatk: we have 2 nested sections. Vocabulary Symbol is an H3 should be H2, and Vocabulary doesn't need to be there.
… , I thought data-symbol to adapt-symbol, but I do see the "Symbol" attribute, its the adapt-symbol not just "Symbol" attribute we need to fix this in the examples.
<Zakim> matatk, you wanted to say there are some instances of "symbol" on its own (without adapt prefix), at least in 4.1.1
matatk: , 4.1.3 does not make any sense. we need to discuss this with WHAT-WG.
Janina, can't we put symbol on any span of text?
matatk: Yes
matatk: we can remove section 4.1.3
Lionel_Wolberger: We will remove Section 4.1.3
… , change the "Symbol" to be "adapt-symbol" in the example text.
janina: Roy can you merge my changes into Main
Roy: Yes
janina: once done Matt can make these new changes.
Roy: Merged.
<matatk> Kinds of content: https://
janina: should we throw in a real example adapt-symbol with BCI index for that span and show what the UI would display for this vs. that symbol set. Would that be useful?
Lionel_Wolberger: We have 3 examples of Cup of Tea and one has Hebrew.
… , why is there an example with 2 symbol numbers?
matatk: We need two symbols "her" + "Name"
… , there might be a symbol for "his Name" vs. "her Name". we are not use the word "translate". Editors Note: It is important to understand that support for the world's languages, and the translation of content from one language into another occurs between written natural languages.
Charles: This is a "Note" not an "Editors Note"
Lionel_Wolberger: We are referencing the registry now not the PDF.
janina: We are pointing to the PR not github. CR needs to point to the TR.
Lionel_Wolberger: We need to update the B.1 & B.2 move • Thaddeus Cambron (Invited Expert), down to B2.
janina: I can do that.
Explainers readiness
janina: I will send an email to TAG, that we are going to CR and Symbols are well defined, and nothing but that and the associated registry spec. Then go looking for implementations.
Lionel_Wolberger: Great.
janina: we want them to see the camera ready document.
Lionel_Wolberger: we may have to do a TAG explainer for just symbols.
janina: an explainer for ever module doesn't make sense.
… , some things may get handled in CSS etc. We may need adapt-(something). 99% confident to send out the WHAT-WG message at this point.
CSS (i.e., media-queries), Microformats, @autocomplete (Matthew)
matatk: on Rel issue thats not CSS stuff, but I am still thinking of css related to adapt. On Rel attribute, on the list, provided the rel attribute is a good fit for "destination" is for. It is todo with links where a link will take you.
… , it was discounted previously it is only allowed on certain attributes link related. I am not sure if you can put it on an element isn't a link but is acting like it. with role="link"
the Rel attribute looks like a very good fit. The main objective aside from rel, is that the place you register the values is not an official W3C property, but lots of folks point to the micro formats for the attributes there and another w3c on this wiki or something similar. I told maybe in the publishing sphere. attributes on a wiki, community site. on hosting the values. Maybe prior art here.
… , shouldn't be huge technical reasons for this. I need to figure out the w3c spec is. how does it work for this. if you have a community resource for this.
… , lot of specs are now going to this living spec approach.
Lionel_Wolberger: we may be loosing destination.
matatk: we are asking for the adapt attributes, for purpose auto-complete, destination could use rel. but I haven't gotten that far yet.
… , future modules for adapt help/tools clearer COGA attributes. ARIA wants to focus on Screen Reader a11y. so asking for the prefix "adapt" is the right thing to do, "Action" is quite likely as a separate attribute.
… , not clear cut.
Lionel_Wolberger: if we decide that rel and autocomplete we may need to publish a Note.