Personalization Task Force Teleconference -- 04 Nov 2019

<LisaSeemanKest> https://raw.githack.com/w3c/personalization-semantics/pre---wide-review-module-1/content/index.html#simplification-explanation

<sharon> scribe: sharon

<Roy> https://github.com/w3c/personalization-semantics/blob/pre---wide-review-module-1/content/index.html

<LisaSeemanKest> https://raw.githack.com/w3c/personalization-semantics/pre---wide-review-module-1/content/index.html#simplification-explanation

<CharlesL> https://github.com/w3c/personalization-semantics/compare/pre---wide-review-module-1

charles: Review commits in Github since we can't see rendered view.

<LisaSeemanKest> https://raw.githack.com/w3c/personalization-semantics/pre---wide-review-module-1/explainer.html

charles: Action to change Help to open help on the same page. Open in page and added open the same page was added.
... Next change in destination. We renamed comment to feedback. Now says submit feedback on the current item. There was a small changes to the help function from includes changed to go to.

Becky: Should we say navigates too?

<janina> +1 to Becky's point. More specificity would be good

Becky: If its on destination it implies a link which is navigation.

<scribe> ACTION: Charles Change destination help from go to navigates to.

<trackbot> Created ACTION-17 - Change destination help from go to navigates to. [on Charles LaPierre - due 2019-11-11].

<Becka11y> +1

Charles: Content distraction we removed advertisement and added offer. "An offer or advertisement of a product that is under the authors control..."
... Content simplification example became examples (plural).
... Reviewed examples for simplification critical. Might need changes to the language. Use case is valid.

<janina> +1 to the proposed approach

Charles: Any objections or comments?
... Changing definition of critical. Changing elements to controls and content.
... Everyone OK with this change?

<Becka11y> +1

<janina> +1

Charles: Same thing in medium and low are the same change.
... Added hide timer in vocabulary. Provides a mechanism to hide the count down clock in timed situations.
... That was moved and is not new. What we changed in helpful vocabulary. Change Feedback to status. Any issues with that?

Becky: What do we mean by immediate. What's right away?

Lisa: Gives feedback on the status that just happened.

Becky: Immediately identifies information of an action that just occurred?

<CharlesL> Current Definition: provides and identifies immediate information about any action that occurs.

<Becka11y> what about immediately provides and identifies information about an action that has just occured

Charles: Applies to any action. Notification is as soon as it happens.

Becky: Then take away the word just.

<CharlesL> Proposed Definition: immediately provides and identifies information about an action that has occurred.

Lisa: Can we have an example? We may need it in the use cases.
... We don't have examples for all, but we do need a use cases. COGA has a pattern but with name change people may not put the two together.

<CharlesL> https://w3c.github.io/personalization-semantics/help/index.html

Charles: Look down to use cases. There is nothing in there and it goes directly to vocabulary, so we should add use cases.
... Help 3.1.3 was changed from feedback to status.

Becky: We addressed it because we had a duplicate, so we are changing it now.

Charles: Below extra help in 3.1.3. There is also valuable feedback that we will need to tweak later.
... Single value of feedback was changed to status and the definition we discussed.

<CharlesL> Proposed Definition: immediately provides and identifies information about an action that has occurred.

<scribe> ACTION: Charles to make the change in the help module.

<trackbot> Created ACTION-18 - Make the change in the help module. [on Charles LaPierre - due 2019-11-11].

Charles: Everyone Ok merging those changes to master branch?

Finish Beckys questions she raised in her email.

Charles: Forgot to add that we wanted to do a tag review of the explainer in module 1 and review it to be sure we are all happy with it.

Janina: We should work the time line backward and get a tag review when we can. Will take it up with Michael. AP would request it.

Lisa: We discussed this on the coordination call. We need a tag review before we go to CR so there are no surprises. Its a good idea to look at it for next week to be sure we are happy with it.

Charles: Tag review should be inline with what is in the explainer.

<janina> https://w3ctag.github.io/explainers

<scribe> ACTION: Charles to compare the tags explainer requirements with out explainer and send an email to the list if discrepancies are found.

<trackbot> Created ACTION-19 - Compare the tags explainer requirements with out explainer and send an email to the list if discrepancies are found. [on Charles LaPierre - due 2019-11-11].

Lisa: We also have a requirements document that is much shorter. Is it Ok if it is at an earlier stage.

Janina: Where we need requirements are when we go from CR to PR.