<rdeltour> scribe: Romain

<Rachel> scribe: Rachel

mateus: our role is defining what personalization means to web publications. I drafted an early agenda that I sent via the invitation

what does personalization mean and how does it relate to us

mateus: for the purposes of web publications do we need to go any further that the existing list of recommendations. Do we need the option of overriding personalization options.

Laurentlemeur: maybe we could focus on how we ask the reading system to personalize (or not) the display. As of now this doesn't exist.

mateus: where do we draw a boundary between authoring and personalization
... do we need to identify a need to override within the system
... I'm thinking of some of dauwhe's proposals, ie full bleeds
... is there anything else that we should consider here besides the traditional personalizations?
... do we know who is using these use cases and how (ie accessibility)

clapierre: there is a lot of personalization that we can envision - for example simplification of the page
... being able to change color scheme, margin widths, line spacing
... customizing font - there are mixed reviews about dyslexia (the font was recently added to Readium c/o Benetech)
... I'm going to be joining the ARIA folks and see what they are starting work on and seeing how it relates to the publishing group

mateus: with that in mind, do we need to prescribe anything for web publications to support

clapierre: there may be markup required (ie footnotes, running headers, etc) - it could be dpub-aria and then it would be up to the reading system to interact with those

mateus: so this is really about content structure and as long as there is proper semantic inflection the reading system and user should be able to make use

clapierre: we tried this at a codesprint by adding semantic markup to content and then used js to find those tags and change content reresentation on the fly

mateus: so is personalization really about how the reading system interprets the content? That seems to be where we're leaning.
... where are we on content authoring and user choices. If it's critical to the presentation of the content that it's done in a certain way - where does the boundary lie in whether publishers should be ableto allow to override settings

mattg: its inevitable that publishers will override and we need a way of reporting that
... ie font size

laurentlemeur: an accessible book requires that you not have nonmodifiable content

mateus: does it fall on us to define this in the manifest?

clapierre: we've added a lot of accessibility metadata including access modes, summary (human readable), etc
... we can add in more features that address personalization and loop in mattg and Madeleine Rothberg
... that's more for discovery than anything else

mateus: I think that would be very helpful

+1 clapierre and mateus

mateus: there seems to be some overlap, especially with the accessibility task force - we should reach out to avneesh and george to weigh in
... the primary use case is accessing content in a structured manner
... that aids in ease of use/better user experience

Evan: the personalization semantics group would be most helpful
... i could see a publishing specifc version of that being helpful

mateus: sounds like our work is simpler than it seemed. We need to identify in the personalization part of the spec that we can surface requirements that are in other ares of the spec

clapierre: are we going to think about where the content is being consumed - the web on a large screen, cell phone or tablet (with little space)

mateus: my thought is that it should
... do we define a specific way of addressing this so there is a universal system for applying the override
... for example nightmode
... especially if we consider the possibility of packing and leaving the web envirnment

laurent: I am in favor of that - there is lack of interoperability btwn readers, if we can have mobile rules then it will make a better future

clapierre: one thing we might also have to talk about fixed layout

mateus: we will try to loop in new members who are passionate about these topics

clapierre: there is a task force for mobility that we could reach out to

laurent: some people in the working group think that reading systems should not exist and that everything should beincluded inside the publication. I think that this task force should take a position. IMO the reading system should be able to apply overrides for a universal experience within the system

mateus: if we were to leave these options to the individual publications, there would be a 100 unique approaches
... it created a nightmare for interoperability
... we can curtail the question and say 'these are rules by which this is read by the user agent'

How do we relate to other working groups in w3c

mateus: clapierre has offered to reach out to the aria group
... I can also reach out to dave and tzviya
... are there any other points for discussion?

laurent: have you drafted anything yet?

mateus: not yet
... once we have more info about the interplay with other groups we can start drafting, but I'll start with github issues
... we dont have a good idea from the manifest task force about how that will be defined

clapierre: please tag for personalization in github

Evan: it's going to be difficult to define how wp personalization is going to be different from general personalization until wp itself is defined

mateus: thanks - I'll start opening up issues

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: mateus laurentlemeur rdeltour Rachel mattg clapierre
Found Scribe: Romain
Found Scribe: Rachel
Inferring ScribeNick: Rachel
Scribes: Romain, Rachel

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 27 Jul 2017
Guessing minutes URL: http://www.w3.org/2017/07/27-pwg-ptf-minutes.html
People with action items: