W3C

– DRAFT –
WAI Adapt Task Force Teleconference

27 June 2022

Attendees

Present
becky, janina, Lionel_Wolberger, Lisa, Matthew_Atkinson, mike_beganyi_, Roy
Regrets
-
Chair
Sharon
Scribe
Lionel_Wolberger

Meeting minutes

RESOLUTION: The group will not meet next week Monday July 4th. Happy holiday to everyone celebrating!

3.6 edit (see git link) (Janina)

Spec content is ready for CR

Janina: WHile editing, one issue was the way "distracting" and "distraction" appear in the spec
… And there is a PR against 3.6

3.6 edit (see git link) (Janina)

<Matthew_Atkinson> https://github.com/w3c/adapt/pull/209 - there is a link in there to the HTML preview, which is http://raw.githack.com/w3c/adapt/adapt-js2206a/content/index.html#symbol-explanation

<Matthew_Atkinson> Simplifications made in 3.6.1 (description) and 3.6.2 (examples); also two EdNotes have been added in 3.6.1 (description).

Sharon: Sounds like we are all OK to accept this wording.
… no objections

RESOLUTION: We agree to merge the PR 209 affecting the text of 3.6

Blog post draft ready (Lionel)

Sharon: check to be sure you are in the current, latest version

<Sharon> https://www.w3.org/WAI/cc/wiki/WAI_Announcement_Drafts#WAI-Adapt_-_Content_ModuleCandidate_Recommendation_.28CR.29_and_WAI-Adapt_Explainer_.28Update_publishedd

Sharon: The draft will go in the "Blog WAI-Adapt" slot of this wiki page
https://www.w3.org/WAI/cc/wiki/WAI_Announcement_Drafts#WAI-Adapt_-_Content_ModuleCandidate_Recommendation_.28CR.29_and_WAI-Adapt_Explainer_.28Update_publishedd

Lionel_Wolberger: I will have it up end of this week

janina: Better to have it before 0800 Tuesdeay
… as the next steps are (a) chairs to review Janina+Matt (b) Michael to review (c) Shawn to review
… then a CfC

janina: Once we finish document prep, we send the messaging up the chain. That includes approvals and reviews.
… that's step 1: complete the messaging
… step 2, Adapt logs a resolution that Adapt is ready for APA to announce a CfC to publish as a Candidate Recommendation
… this establishes a needed audit trail.
… given that CfC takes a week
… we are likely to publish 26th July

CR Announcement is teed up in the WAI wiki (Sharon)

Lionel: In conversation with a very knowledgeable W3C person, the question of <rel was raised
… see https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/rel

Lisa: This did come up near the beginning (this is now years ago)
… I believe I recall that the scope was the problem
… <rel does meet some of the needs here. It works very well in the link of a header, perhaps other links, but not everywhere else

<Matthew_Atkinson> https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/rel

Lisa: @rel tends to give meta-data on the page as a whole

janina: Suggest we add this to the explainer

Lisa: The mozilla doc opens with, "The rel attribute defines the relationship between a linked resource and the current document. Valid on <link>, <a>, <area>, and <form>, the supported values depend on the element on which the attribute is found."
… note [it relates to] "the current document"

Matthew_Atkinson: You can apply @rel to some elements, but not to buttons
… the mozilla doc lists <link>, <a>, <area>, and <form>
… not button

janina: What if WHAT-WG says, let's "fix" @rel so it can apply to buttons

Lisa: There is a temptation with semantics to overload what it actually is
… there will also be similar thoughts regarding the ability of RDF to do some of this semantic assignment
… and we will run into the same issues

Sharon: Lionel to respond with the summary of the above

Summary of resolutions

  1. The group will not meet next week Monday July 4th. Happy holiday to everyone celebrating!
  2. We agree to merge the PR 209 affecting the text of 3.6
Minutes manually created (not a transcript), formatted by scribe.perl version 185 (Thu Dec 2 18:51:55 2021 UTC).

Diagnostics

Succeeded: s/between HTML <rel>/between HTML @rel/

Succeeded: s/<rel/@rel/

Succeeded: s/<rel/@rel/

Succeeded: s/<rel/@rel/

Maybe present: Lionel, Sharon