13:23:26 <RRSAgent> RRSAgent has joined #adapt
13:23:26 <RRSAgent> logging to https://www.w3.org/2022/08/22-adapt-irc
13:23:28 <trackbot> RRSAgent, make logs public
13:23:28 <Zakim> Zakim has joined #adapt
13:23:30 <trackbot> Meeting: WAI Adapt Task Force Teleconference
13:23:30 <trackbot> Date: 22 August 2022
13:23:47 <Sharon> agenda?
13:24:10 <Sharon> chair: Sharon
13:25:10 <Sharon> agenda+ Reminder: Sept, 3 weeks without Adapt TF meetings
13:25:38 <Sharon> agenda+ TPAC Prep status
13:26:10 <Sharon> agenda+ Exit criteria status & comments
13:26:23 <Sharon> agenda+ Discuss @rel vs. purpose/destination/action -- add to the explainer
13:26:41 <Sharon> agenda+ TAG Response Resolution - media query test page
13:26:53 <Sharon> agenda+ BCI Registry Specification
13:27:04 <Sharon> agenda+ Respond to issue #203 (Janina)
13:27:04 <Github> https://github.com/w3c/adapt/issues/203 : Unclear how the Bliss symbol examples should work with i10n/i18n.
13:27:24 <Sharon> agenda+ Content Module Implementations Status, focus on new candidates
13:58:15 <janina> janina has joined #adapt
13:59:13 <Sharon> Sharon has joined #adapt
13:59:23 <Sharon> agenda?
13:59:27 <Github> https://github.com/w3c/adapt/issues/203 : Unclear how the Bliss symbol examples should work with i10n/i18n.
14:00:16 <janina> present+
14:02:03 <mike_beganyi> mike_beganyi has joined #adapt
14:02:10 <mike_beganyi> present+
14:02:22 <janina> regrets: Becky, Roy
14:02:56 <Lionel_Wolberger> Lionel_Wolberger has joined #adapt
14:03:03 <Lionel_Wolberger> present+
14:03:14 <CharlesL> CharlesL has joined #adapt
14:03:26 <CharlesL> present+
14:04:30 <mike_beganyi> scribe+
14:05:11 <Lionel_Wolberger> present+
14:05:13 <mike_beganyi> zakim, next item
14:05:13 <Zakim> agendum 1 -- Reminder: Sept, 3 weeks without Adapt TF meetings -- taken up [from Sharon]
14:05:33 <mike_beganyi> Sharon: one more meeting, then three weeks off
14:06:13 <mike_beganyi> janina: discuss what we want to achieve in next couple weeks. beings 6th-7th and goes through TPAC. if we want to update WD we might be able to achieve by next week
14:06:30 <mike_beganyi> zakim, next item
14:06:30 <Zakim> agendum 2 -- TPAC Prep status -- taken up [from Sharon]
14:07:12 <mike_beganyi> Sharon: discussed in planning meeting last week, potential meeting with COGA and TAG. will COGA be there at TPAC?
14:08:07 <mike_beganyi> janina: 4 people should attend in person. will end up verifying registration of COGA reps and decide from there. regardless, in terms of our meeting, I'd like to see an agenda before making a meeting
14:08:36 <mike_beganyi> ...as far as meeting with Adapt, let's get an agenda first
14:09:40 <mike_beganyi> Lionel_Wolberger: I have 7 topics for an agenda to discuss with COGA. what Adapt does, what the role is, what we do, what we don't do, what we need from COGA (use cases)
14:10:08 <mike_beganyi> janina: bad cop question: why does this have to happen at TPAC?
14:10:39 <mike_beganyi> Lionel_Wolberger: because COGA may benefit more from in-person meetings
14:11:26 <mike_beganyi> janina: send to Lisa if not entire COGA list. they're in charge of their agenda at Monday and Tuesday meetings. agreement between APA and COGA that it's a reasonable meeting
14:11:41 <mike_beganyi> janina: if TAAG shows up, it's higher priority
14:12:06 <mike_beganyi> s/ TAAG, TAG
14:12:29 <Matthew_Atkinson> Matthew_Atkinson has joined #adapt
14:12:41 <mike_beganyi> janina: have not had a response from TAG just yet. may need to follow-up
14:13:49 <Matthew_Atkinson> present+
14:14:02 <mike_beganyi> janina: did you get the breakout proposed, Lionel?
14:14:14 <mike_beganyi> Lionel_Wolberger: Adapt breakout proposed last week. it's on the Wiki
14:14:43 <Matthew_Atkinson> Here's the proposed Adapt breakout: https://www.w3.org/wiki/TPAC/2022/SessionIdeas#WAI-Adapt_Candidate_Recommendation_of_Content_Module_1.0:_Overview (thanks Lionel)
14:16:09 <mike_beganyi> Lionel_Wolberger: no other breakouts are needed currently. we need a joint meeting with TAG
14:16:11 <mike_beganyi> zakim, next item
14:16:11 <Zakim> agendum 3 -- Exit criteria status & comments -- taken up [from Sharon]
14:16:32 <mike_beganyi> Sharon: addressing MichaelC's comments
14:16:34 <Sharon> https://lists.w3.org/Archives/Public/public-adapt/2022Aug/0013.html
14:16:40 <mike_beganyi> janina: update our WD if we can before TPAC
14:17:32 <mike_beganyi> Lionel_Wolberger: will be able to review shortly
14:17:35 <mike_beganyi> Matthew_Atkinson: same
14:18:17 <mike_beganyi> janina: Michael saying this should be an appendix. other suggestion to highlight is that we need one MUST statement relating to user agents. did you catch that Matthew?
14:19:35 <mike_beganyi> Matthew_Atkinson: we were talking about this, Lionel and I. only place it makes sense is basically authors can do what they want. implementation: implement as many as you like, if you implement some, you MUST cover all the requirements
14:20:11 <mike_beganyi> janina: that sort of language is great, needs some review. will address prospective feedback that the spec doesn't require anything
14:20:28 <mike_beganyi> janina: wording is close, but still needs some review
14:20:56 <Lionel_Wolberger> The sentence in question: User agents MAY implement any set of attributes from this specificationthey wish. If a user agent implements an Adapt attribute, it MUST provide support for all possible values of that attribute.
14:21:06 <mike_beganyi> janina: if we can agree before next week and avoid CFC, would be good to have that done before TPAC. we can avoid having that conversation at TPAC. can have more productive conversations
14:21:37 <Lionel_Wolberger> New sentence:
14:21:37 <Lionel_Wolberger> User agents MAY implement any set of attributes from this specification. If a user agent implements an Adapt attribute, it MUST provide support for all possible values of that attribute.
14:22:01 <Lionel_Wolberger> User agents MAY implement any set of attributes from this specification. Whenever user agent implements an Adapt attribute, it MUST provide support for all possible values of that attribute.
14:22:06 <Lionel_Wolberger> User agents MAY implement any set of attributes from this specification. Whenever a user agent implements an Adapt attribute, it MUST provide support for all possible values of that attribute.
14:23:19 <mike_beganyi> Sharon: anything else to cover on MichaelC's comments? or just to update wording on main requirement before next week?
14:24:43 <mike_beganyi> zakim, next item
14:24:43 <Zakim> agendum 4 -- Discuss @rel vs. purpose/destination/action -- add to the explainer -- taken up [from Sharon]
14:25:47 <mike_beganyi> Lionel_Wolberger: discussed several times. main difference between rel and destination values is in help.
14:27:19 <Lionel_Wolberger> https://github.com/w3c/adapt/issues/172
14:28:11 <mike_beganyi> Sharon: so what is the next step? is this what we need to write up and add to the Explainer?
14:28:27 <Sharon> q?
14:28:43 <mike_beganyi> Lionel_Wolberger: because rel seems to pop up, it should be in the Explainer
14:28:54 <mike_beganyi> janina: it needs its own section maybe something about how rel is insufficnet
14:29:18 <mike_beganyi> janina: makes sense that Explainer should address this
14:29:19 <Lionel_Wolberger> Wiki page, "Comparison of ways to use vocabulary in content": https://github.com/w3c/adapt/wiki/Comparison-of-ways-to-use-vocabulary-in-content
14:29:53 <mike_beganyi> janina: would be good to be in Explainer before TPAC
14:31:00 <mike_beganyi> Sharon: could you find a place for rel in the Explainer, Lionel?
14:31:13 <mike_beganyi> Lionel_Wolberger: sure can
14:31:19 <Matthew_Atkinson> q+
14:31:32 <Sharon> ack Matthew_Atkinson
14:31:58 <mike_beganyi> Matthew_Atkinson: looking at MDN version of spec. rel only allowed on certain elements. depending on which elements, different values can apply.
14:32:22 <mike_beganyi> Matthew_Atkinson: why not make rel allowable on a wider range of elements? have more range of values on elements
14:33:04 <mike_beganyi> Matthew_Atkinson: could combine attributes. might be more applicable to developers. might not be technically feasible
14:33:13 <janina> q+ we won't mind becoming html 5.x!
14:33:20 <janina> q+
14:33:39 <Sharon> ack janina
14:34:08 <mike_beganyi> janina: I think it's worth checking. regarding picking up any attributes and values and migrating them into HTML 5. if HTML 5 picks up a spec we wouldn't object
14:34:47 <mike_beganyi> janina: Matthew_Atkinson might be something we put on the agenda. we might point out apparent overlap with rel and what we're doing technologically to address some COGA issues
14:35:04 <mike_beganyi> janina: if HTML picks up, we wouldn't object
14:35:12 <mike_beganyi> zakim, next item
14:35:12 <Zakim> agendum 5 -- TAG Response Resolution - media query test page -- taken up [from Sharon]
14:35:53 <mike_beganyi> Sharon: having that complete for TPAC, Matthew_Atkinson ?
14:36:30 <mike_beganyi> Matthew_Atkinson: noted it's on the right track by Sharon and Lionel_Wolberger. up for final review by the time of the next meeting.
14:37:11 <mike_beganyi> Sharon: a page with three different distractions: time ticker, banner, and a third that shows that we're on the element level and not page level
14:38:26 <janina> https://www.w3.org/wiki/Holidays
14:40:58 <mike_beganyi> janina: trying to coordinate all holidays in one location
14:41:21 <mike_beganyi> Sharon: might not be able to make it next week, Matthew_Atkinson? might be 4 weeks without discussing so we can take it to list to discuss
14:41:34 <mike_beganyi> zakim, next item
14:41:34 <Zakim> agendum 6 -- BCI Registry Specification -- taken up [from Sharon]
14:42:38 <mike_beganyi> janina: status of this is that we wanted MichaelC to follow up to e-mail. can't move forward until Russell gives us a response and a google sheet that MichaelC would like to work from
14:43:25 <mike_beganyi> Lionel_Wolberger: we thought MichaelC would give me a draft. would appreciate one
14:43:36 <mike_beganyi> Sharon: wait until after TPAC to follow up with MichaelC?
14:43:41 <mike_beganyi> janina: yes. will need to wait
14:44:25 <mike_beganyi> zakim, next item
14:44:25 <Zakim> agendum 7 -- Respond to issue #203 (Janina) -- taken up [from Sharon]
14:44:26 <Github> https://github.com/w3c/adapt/issues/203 : Unclear how the Bliss symbol examples should work with i10n/i18n.
14:44:50 <mike_beganyi> janina: will respond to 2 and 3 sometime soon!
14:45:07 <mike_beganyi> zakim, close this item
14:45:07 <Zakim> agendum 7 closed
14:45:08 <Zakim> I see 1 item remaining on the agenda:
14:45:08 <Zakim> 8. Content Module Implementations Status, focus on new candidates [from Sharon]
14:45:09 <mike_beganyi> zakim, next item
14:45:09 <Zakim> agendum 8 -- Content Module Implementations Status, focus on new candidates -- taken up [from Sharon]
14:46:12 <mike_beganyi> Lionel_Wolberger: more or less where it stood before
14:46:26 <mike_beganyi> janina: implementors will be present at TPAC, so discussion can occur there
14:50:53 <mike_beganyi> janina: might want to ask James (ARIA) about what's happening with Adapt at TPAC
14:52:53 <mike_beganyi> rrsagent, make minutes
14:52:53 <RRSAgent> I have made the request to generate https://www.w3.org/2022/08/22-adapt-minutes.html mike_beganyi
14:52:57 <CharlesL> CharlesL has left #adapt
14:53:00 <mike_beganyi> zakim, bye
14:53:00 <Zakim> leaving.  As of this point the attendees have been janina, mike_beganyi, Lionel_Wolberger, CharlesL, Matthew_Atkinson
14:53:00 <Zakim> Zakim has left #adapt