W3C home > Mailing lists > Public > public-publ-wg@w3.org > March 2018

Re: [affordances] Call for Participation: PWG Affordances Task Force

From: <deborah.kaplan@suberic.net>
Date: Wed, 7 Mar 2018 12:28:08 -0500 (Eastern Standard Time)
To: W3C Publishing Working Group <public-publ-wg@w3.org>
Message-ID: <alpine.WNT.2.20.1803071221290.13920@sierra>
I'd definitely like to encourage people who are intimidated by the jargon term to think of these as "features," as Jasmine and Katie said. I understand why, technically, we are distinguishing between "features" (which are active abilities of, say, a reading system) and the more passive "affordances" of a publication (action possibilities, as Laurent quotes). For our actual documentation and product we need to be careful about the precision of language, and distinguishing between features and affordances. But in laypeople terms, think "features". It's close enough that people who think of these as features should still be able to contribute to the conversation.

(This email brought to you by my whining at Benjamin until he explained to me in a way I understood about the difference between affordance and feature.)


Deborah

On Wed, 7 Mar 2018, Laurent Le Meur wrote:

> Starting from https://github.com/w3c/wpub/issues/149#issuecomment-369876025 and Benjamin's feedback, I suggest that we first defined the term in our context. And in https://en.wikipedia.org/wiki/Affordance, Gibson's definition is of
> no real help for us. I personally prefer the information given in the section "As perceived action possibilities" -> those action possibilities that are readily perceivable by an actor.
> In a generic way, an entity provides an affordance to an actor. And we are dealing with an actor - the User - and two entities: the User Agent and the Web Publication. 
> So we get two kinds of affordances:
> 1/ The User Agent (after having loaded a Web Publication) provides affordances to the User (think about the reader mode in Firefox)
> 2/ The Web Publication itself provides affordances to the User (think about interactive ebooks)
> 
> My take is that our work as a task force is to focus on item 1 = what the User Agent must/should/may present to the User as possible actions (for enjoying a great reading experience). 
> Would there be a consensus around that interpretation? 
> 
> Cordialement, 
> 
> Laurent Le Meur
> EDRLab
> 
>
>       Le 6 mars 2018 à 18:17, Jasmine Mulliken <jasmine.mulliken@stanford.edu> a écrit :
> 
> Hi, Katie. In this context "affordances" refer to the what web publications can offer that current electronic reading experiences don't necessarily--at least in a web browser. You could also see them as "features." Here is the
> open list we'll be looking at: https://github.com/w3c/wpub/issues?q=is%3Aissue+is%3Aopen+label%3Atopic%3Aaffordances
> 
> Hope this helps!
> Best,
> Jasmine
> 
> 
> From: Katie Haritos-Shea <ryladog@gmail.com>
> Sent: Tuesday, March 6, 2018 8:29:20 AM
> To: Schindler Wolfgang Dr.
> Cc: Teixeira, Mateus; W3C Publishing Working Group; Garth Conboy (garth@google.com); Ivan Herman; Jasmine Mulliken; Siegman, Tzviya - Hoboken
> Subject: Re: [affordances] Call for Participation: PWG Affordances Task Force 
> Mateus and Jasmine,
> 
> Question: Is the 'affordances' the same as the term 'accommodations' that is used in the US?
> 
> Thanks!
> 
> 
> 
>

-- 
Received on Wednesday, 7 March 2018 17:28:43 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 March 2018 17:28:44 UTC