Re: explainer

Hi Lisa,

My edits were informed by TAG's comments.

About the only major change I made to the previous structure was to move
the Non-goals higher up (as in the original template
<https://w3ctag.github.io/explainers#explainer-template>), as I wanted to
ensure they clearly understood the first bullet point: *Develop an API for
browsers or other user-agents* (Out of scope). I did that primarily because
the TAG template appears to be looking for / wanting information about
"APIs", which is not what we are doing.

I also tried to focus on editing the use-case and user-stories: there was
some duplication there, and hopefully the new, linked structure and
'ordering' of that section is easier to digest.

Looking forward to a review on Monday!

JF

On Tue, Apr 14, 2020 at 1:36 AM lisa.seeman <lisa.seeman@zoho.com> wrote:

> Thanks John
> It looks good but they asked us to follow the template And remove some
> sections.
> Could you take a look at the tags comments? We need to adress them as well
> as make a good document.
>
>
> All the best
>
> Lisa Seeman
>
> LinkedIn <http://il.linkedin.com/in/lisaseeman/>, Twitter
> <https://twitter.com/SeemanLisa>
>
>
>
> ---- On Tue, 14 Apr 2020 02:01:53 +0300 * john.foliot@deque.com
> <john.foliot@deque.com> * wrote ----
>
> Hi Lisa, Sharon,
>
> Spent some time today with the draft, and have made some at-times
> significant changes:
> https://github.com/w3c/personalization-semantics/wiki/restructure-of-the-explainer
>
>
> Essentially, I've moved the Use-cases / User-stories down further in the
> body of the document, and instead tried to bring the 'technologies'  up and
> forward to sooner in the document (a.k.a. "know your audience"). I've also
> applied some formatting, added hyperlinks where I thought appropriate,
> removed some duplicate content, added some illustrations, and have added
> some additional internal notes for further discussion.
>
> Because I've been dragging my feet on this task, I am also sharing it to
> the entire TF for wider review/comment now. Bricks and bouquets as seen fit.
>
> JF
>
> On Mon, Apr 13, 2020 at 11:04 AM John Foliot <john.foliot@deque.com>
> wrote:
>
> This has been on me for a while now - apologies for the tardiness.
>
> I'll take a crack at this today/tomorrow and advise.
>
> JF
>
> On Mon, Apr 13, 2020 at 10:23 AM lisa.seeman <lisa.seeman@zoho.com> wrote:
>
> Hi Sharron and John
>
> Would either of you have time to edit the restructuring the explainer?
>
> See https://github.com/w3c/personalization-semantics/wiki/restructure-of-the-explainer
>
>
> The point is to respond to the TAGs comments at https://github.com/w3ctag/design-reviews/issues/476
> So we need more examination of use cases and some other content removed. It is already in the Tag's template. (note the content in squire  brackets is from the template instruction)
>
> Beyond normal editorial, we want to keep it short, so any content that does not explain what we are doing or meet the TAG's questions/template can be edited out.
>
> I can add screen shots and worked expample they requested (if that helps).
>
> All the best
>
> Lisa Seeman
>
> LinkedIn <http://il.linkedin.com/in/lisaseeman/>, Twitter
> <https://twitter.com/SeemanLisa>
>
>
>
>
>
>
>
> --
> *​John Foliot* | Principal Accessibility Strategist | W3C AC
> Representative
> Deque Systems - Accessibility for Good
> deque.com
>
>
>
>
> --
> *​John Foliot* | Principal Accessibility Strategist | W3C AC
> Representative
> Deque Systems - Accessibility for Good
> deque.com
>
>
>
>

-- 
*​John Foliot* | Principal Accessibility Strategist | W3C AC Representative
Deque Systems - Accessibility for Good
deque.com