scribe+

Feedback from TAG

<Wilco> https://github.com/w3ctag/design-reviews/issues/977#issuecomment-2730535113

daniel: TAG is Technical Architectural Group
... horizontal review process that every spec goes through
... more normative processes

wilco: are these ideas or need to do?

daniel: don't think it's a must, but good to address

wilco: we have test suites to check rules for order of headings, definitions exist, etc.
... test suite is in github repo

daniel: suggestions are to include normative prose for headings, for example

wilco: cannot do that because of internationalization

daniel: agree defining strings would not be a good idea

wilco: think this is a big ask, to require RDF schema
... we do not have the resources

daniel: is there anything easy from this suggestion that can be done?

wilco: I like the idea
... but a lot of work
... weeks of work
... can this be deferred to a future version of the rules format?

daniel: provided that comment since this is significant change, for version 2.0

wilco: validation of a rule is not trivial. coming up with the requested structure is a lot of work

sage: sounds like a lot of work

wilco: ARIA wg did not adopt it so ACT didn't as well
... suggest it for 2.0

daniel: will draft a response

<scribe> ACTION: Daniel will write a response and share with the planning team

Rule identifiers feedback

<Wilco> https://github.com/w3c/wcag-act/issues/572#issuecomment-2776513866

wilco: another feedback from internationalization group
... uppercase lower case conflicts

daniel: replied and waiting for input. PR 593 proposal
... we proposed choose visually distinctive identifiers

<Wilco> https://github.com/w3c/wcag-act/pull/593/files

daniel: use only lower case

wilco: can we remove "unique"?

daniel: concerned with having same identifier if remove unique

wilco: what is "require additional processing"?

daniel: unsure

wilco: where did visually distinct come from?
... more confusing

daniel: can wordsmith further

kathy: depends on font. some fonts do have lower case l and number 1 look very similar

daniel: can comment back to ask for clarification

wilco: if two identifiers use a lower case letter and another uses upper case of that letter, these identifiers are unique
... perhaps unique unicode

daniel: they suggest normative unique IDs
... in rules format

wilco: suggest unique string of Unicode chars
... does not need to be visually distinct

daniel: in addition, why not include lower case?

wilco: it would add a new requirement to the rules format
... would prefer to minimize changes
... adding lower case in PR as a suggestion
... in non-normative sentence of line 132
... have a proposal for internationalization

programmatic language

<Wilco> https://github.com/w3c/wcag-act/issues/573#issuecomment-2776110002

<Wilco> https://github.com/w3c/wcag-act/pull/592/files

<Daniel> https://w3c.github.io/string-meta/ -> Strings on the Web

<Wilco> +1

wilco: add +1 if ok to merge

<Helen> +1

+1

<Wilco> +1 from Sage

This is scribe.perl Revision VERSION of 2020-12-31
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/normative format/normative prose/
Default Present: todd, Kathy, Helen, Sage, Daniel, Wilco, suji, Rachael, sashanichols
Present: todd, Kathy, Helen, Sage, Daniel, Wilco, suji, Rachael, sashanichols
No ScribeNick specified.  Guessing ScribeNick: Kathy
Inferring Scribes: Kathy

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: daniel

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)