<LisaSeemanKestenbaum> scribe: sharon

review survey https://www.w3.org/2002/09/wbs/101569/Data-Dash2019/results

Lisa: People don't like data-field. Data-purpose, but 2 people didn't like it. Reviewing a couple together and see what we can resolve.

<LisaSeemanKestenbaum> https://www.w3.org/2002/09/wbs/101569/Data-Dash2019/results

Lisa: No one supported merging them together.
... Merging is off the table. No merging at this point.
... Is survey open for responses until May 5th.

<LisaSeemanKestenbaum> resoleved: no merging destination and action into Purpose

<JF> Non-responders The following persons have not answered the questionnaire: Janina Sajka <janina@rednote.net> Michael Cooper <cooper@w3.org> Andy Heath <andyheath@axelafa.com> Jason White <jjwhite@ets.org> Ruoxi Ran <ran@w3.org>

Janina: Didn't respond so she could hear more.

<LisaSeemanKestenbaum> at this point

John: data-purpose, data-field, data-*. What about the other options.
... Does not see an option for data-action or data-destination

<LisaSeemanKestenbaum> posal 1. data-purpose , data-action, data-daestingatio

<LisaSeemanKestenbaum> posale 1. data-purpose , data-action, data-destination

<JF> data-purpose, data-action, data-destination - see https://github.com/w3c/personalization-semantics/wiki/Prototypes-with-data-dash-*-(Take-2)

<LisaSeemanKestenbaum> posal 2:data-purpose, data-purpose-action, data-purpose-destination

<LisaSeemanKestenbaum> maybe data-purpose-field

<LisaSeemanKestenbaum> posal 3: data-purpose-feild, data-purpose-action, data-purpose-destination

John: An action is applied to a button, destination to a URL and purpose is applied to a field.

<LisaSeemanKestenbaum> posale 1. data-purpose , data-action, data-destination

<LisaSeemanKestenbaum> posal 2:data-purpose, data-purpose-action, data-purpose-destination

<LisaSeemanKestenbaum> posal 3: data-purpose-feild, data-purpose-action, data-purpose-destination

<JF> What is the purpose of this field? What is the purpose of this button? What is the purpose of this link?

Becky: Thinks we are saying you should just need data-purpose, actions apply to button and destination apply to links. Lets get rid of extra things and just use data-purpose.
... data-purpose and define action based on the control.

Lisa: If you want to change your vote do it as we go.

JF: We don't want a general term for all attributes, they take one of a specific value. We could run into conflicts. The sortable table is to help find duplicates.
... Does not want the attribute to be the same term. At the end of the day we have 3 functions. Does not understand why can't have 3.
... Concerns about one attribute, the sortable table had duplicate values.

<LisaSeemanKestenbaum> posale 1. data-purpose , data-action, data-destination

<LisaSeemanKestenbaum> posal 2:data-purpose, data-purpose-action, data-purpose-destination

Becky: OK with having 3 attributes for now.

<LisaSeemanKestenbaum> posal 3: data-purpose-feild, data-purpose-action, data-purpose-destination

<LisaSeemanKestenbaum> posal 3: data-purpose-feild, data-purpose-action, data-purpose-destination, data-purpose

Lisa: There is an advantage for proposal 1. Any other reasons people prefer proposal 1?

JF: Suggests that by adding data- is that it is experimental. We'll end up with purpose, action, destination. At this point we agree that having just purpose is stretching the boundaries.

Lisa: Anyone wants to change their vote? Please change it with the idea that "can live with" is OK.
... It would be easier to understand purpose- hyphen would make it easier.

JF: Purpose for symbol is confusing. Does not see an author doing that.

Lisa: Shelf symbol for now.
... There are people who write content with symbols for different users. Content needs to be recreating for their own users. They can point to a node. Enable people to load an alternative symbol sets.

<stevelee_> ack

<JF> https://github.com/w3c/personalization-semantics/wiki/Prototypes-with-data-dash-*-(Take-2)

<Zakim> JF, you wanted to respond to Steve.

JF: We are talking about why is this here and what am I supposed to do with it.
... Can you think of another purpose? If its not on a button or link what else has a purpose?
... Discussed the example page. Different symbols at some level, they are not using the same symbol set. Idea is mapped to a symbol in a symbol set.

Lisa: Thinks she agrees. They have ways to create a new symbol quickly. Its a URI rather then a token because we will never get the full list.
... 1. Agreed no one wants data field. 2. data-field gets replaced with data-purpose.

<LisaSeemanKestenbaum> posale 1. data-purpose , data-action, data-destination

<LisaSeemanKestenbaum> posal 2:data-purpose, data-purpose-action, data-purpose-destination

<LisaSeemanKestenbaum> posal 3: data-purpose-feild, data-purpose-action, data-purpose-destination

<JF> +1, -2, -3

<JF> +1, 2, -3

<Becka11y> +1, 2, -3

<JF> (proposal 2-b: data-purpose, data-purposeaction, data-purposedestination - i.e no double hyphenation, using ARIA notation instead)

<LisaSeemanKestenbaum> thadd: +1,2,?

+1, 2, -3

<stevelee_> +1, 2, 3 -2b

<Becka11y> +1, 2, 2-b, -3

<LisaSeemanKestenbaum> 1,2,+3

<janina> +1 -2 -3

<LisaSeemanKestenbaum> data-purpose , data-action, data-destination

Lisa: Anyone disagree?
... We will go with proposal 1.
... Move on to including alt in the attribute name.

stevelee: May cause confusion.

JF: Reading that we don't need alt in the attribute name.

Thadd: Can live with us not including it.

<LisaSeemanKestenbaum> resolutions : data-purpose-feild, data-purpose-action, data-purpose-destination

<LisaSeemanKestenbaum> resolution 2 : do not include alt in the attribute name

<LisaSeemanKestenbaum> +1

<janina> +1

<JF> +1

+1

<stevelee_> +1

<LisaSeemanKestenbaum> thadd:+1

<LisaSeemanKestenbaum> 0

<Becka11y> +1 for resolution 2

RESOLUTION: do not include alt in the attribute name

RESOLUTION: data-purpose, data-action, data-destination

RESOLUTION: do not include alt in the attribute name

RESOLUTION: data-purpose, data-action, data-destination

<JF> +1 to both resolutions

<stevelee_> +1

+1

<janina> +1

<Becka11y> +1 to both resolutions

Lisa: Next week we can discuss symbol and any new proposals.

<JF> I do have a proposal for symbol, please see: https://github.com/w3c/personalization-semantics/wiki/Prototypes-with-data-dash-*-(Take-2)#attribute-to-provide-symbols-goal-images-to-replace-on-screen-text

Becky: Didn't we say we would ask someone to join us regarding symbols.

<janina> Need to go, all! Bye

Lisa: Will ask someone who is familiar with symbols.

This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/Resolution:  data-purpose, data-purpose-action, data-purpose-destination//
Present: stevelee_ JF Becka11y Roy janina MichaelC
Found Scribe: sharon
Inferring ScribeNick: sharon

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

Found Date: 15 Apr 2019
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)