<scribe> scribe: Jean-Yves
Wilco: TF is running out of work. But there is movement on our part.
<EmmaJ_PR> +present
Jean-Yves: mine are waiting fro presentational role conflict resolution
Daniel: updating mine
<Daniel> https://github.com/act-rules/act-rules.github.io/issues/1258
Shadi: not sure what is happening
Wilco: for proposing rule: update
according to design document (e.g. test cases description). for
resolving TF feedback: go through TF issue, make changes and
open PRs, answer questions (especially for changes we don't
want to do…)
... discussing TF feedback on issue handled by Shadi.
... ideally, rules are shepherded by the writers.
Jey: mine have PRs to address review or prepare them.
Carlos: mine are PRs for addressing review.
Jean-Yves: these PRs are without review requested, which may take long before they are reviewed…
Wilco: assigning people is a good idea.
Daniel: it's OK to get a lot of request for reviews. I know what I have to do.
Carlos: same feeling.
Emma: same feeling.
Daniel: (on 1258) titles of the rules are not super good, should be updated to better match what they do.
Jean-Yves: need to reach balance between long/precise titles.
Emma: composite titles don't need to include everything, should more refer to SC. Atomic rules should have more precise title.
Jean-Yves: agree.
Wilco: "audio or video *avoids*
…" (to have positive formulation, not "has no")
... make a separate PR for title change.
Wilco: custom elements should be
considered HTML element. Make a definition?
... separate issue, will create it.
Jean-Yves: I remember reading that aria-* attributes need value.
Wilco: I was thinking this example works. Maybe needs more testing.
Emma: we should write examples according to spec
<Wilco> https://www.w3.org/TR/wai-aria-1.1/#state_prop_values
Carlos, Emma, Jean-Yves, Wilco: discussing specs and trying to make sense out of them…
Wilco: the issue is that this is
(maybe) invalid HTML. This doesn't really cause problem with
the rule. I don't think we should change it.
... put a note to explain the situation
Jean-Yves: many example with inputs and no label. Should we add them?
Wilco: I think we should. Makes
examples more realistic.
... also makes manual testing easier (by actually saying what
the input is…)
Daniel: provides context useful for testing.
Emma: design says that "examples should demonstrate good practice without code irrelevant to code". I think that inputs should have labels.
Wilco: I'll take it.
<Wilco> https://act-rules.github.io/glossary/#explicit-role
Jean-Yves: explain issue and
proposed fix (splitting def).
... no need to physically split file.
Carlos, Wilco: agree.
Emma: implicit/explicit role should explain what make them explicit/implicit.
Wilco: there are places where the defs are used separately.
Jean-Yves: I'll try and come up with something.
Wilco: will discuss 7 with JY.
Please get a look at 8.
... final thoughts?
Shadi: understand better what need to be done.
Daniel: great discussion.
Jean-Yves: scribing is always tiring.
Jey: good discussions. Need reviews!
Carlos: good discussion and progress. Need clarification that we migrate to W3C slack.
Emma: I volunteer for scribing next time! Will try to look at things I have to do.
Wilco: need reviews on github guideline PR.
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Default Present: Jean-Yves, Daniel, Carlos, Wilco, EmmaJ_PR, present Present: Jean-Yves Daniel Carlos Wilco EmmaJ_PR present Jey Found Scribe: Jean-Yves Inferring ScribeNick: Jean-Yves WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth 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: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. 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.)[End of scribe.perl diagnostic output]