W3C

- DRAFT -

SV_MEETING_TITLE

12 Mar 2018

Attendees

Present
(no, one), clapierre, thaddeus, Roy, MichaelC, Becka11y, Sharon
Regrets
Lisa
Chair
clapierre
Scribe
Becka11y

Contents


<thaddeus> +present

<clapierre> scribe:Becka11y

<clapierre> https://w3c.github.io/personalization-semantics/

<clapierre> https://w3c.github.io/personalization-semantics/content/index.html

first item: call for consensus on explainer and our content module

JoanMarie will put official call for consensus to entire ARIA WG, if no objections after 48 hours we can have Roy post draft

hopefully get done before CSUN - no meeting next Monday, March 19

Charles has completed all of the pull requests - feels that most have been discussed in the group

Michael wants to make sure we are all aware of the current content

<MichaelC> https://w3c.github.io/personalization-semantics/#vocabulary-identification

<MichaelC> proposed namespace: https://www.w3.org/ns/aui/

Michael add a section to describe aui prefix

and provided a namespace

<MichaelC> https://w3c.github.io/personalization-semantics/#html-microdata

<MichaelC> https://w3c.github.io/personalization-semantics/#rdfa

Michael: John Foliot thinks namespace might be incorrect but can fix later

Michael added an editorial note about RDFa may need some additional work

Correction: John Foliot is concerned with microdata (not namespace)

Michael: We need people to respond onlist with questions and concerns
... removed aui prefix in the modules but that confilict a bit with explainer. Just need the prefix when it is required by technology

<thaddeus> +1 for going forward and resolving issues after

Charles: Any concerns with current state of drafts? We know there are issues but we will continue to addressing in future working drafts

<MichaelC> s/; but that confilict a bit with/is address instead in the/

Charles: ARIA group is excited for us to continue work and issuing more drafts

<Sharon> +1

+1

<clapierre> 1+

Charles: Resolution: request publication of explainer and content module

RESOLUTION: request publication of explainer and content module

logs - edits suggested by Sharon

<clapierre> I've been reviewing the Logs section and had the following thoughts that I wanted to run by the group before making changes in GitHub:

<clapierre> 1 I was thinking it would be clearer if we changed log to stepindicator, which is similar to a term used in WCAG examples (see approach 4) they call it a step-by-step indicator. 

<clapierre> 2 Remove actiontaken and use status instead with values of completed (step is done), current (step the user is on), or null (haven't gotten to the step yet). actiontaken shouldn't be needed because the aria-label + status would already indicate the action that was taken. 

<clapierre> In the following example, the user would be booking a trip that has 4 steps. The first step is complete, the second step is currently the one they are working on, and the remaining steps are null because they have not been completed yet.

<clapierre>  

<clapierre> <div aui-stepindicator="book trip">

<clapierre>         <div aui-status="complete" aria-label="select flight" aui-step="1" aui-steplocation="uri" />

<clapierre>         <div aui-status="current" aria-label="book hotel" aui-step="2" aui-steplocation="uri" />

<clapierre>         <div aui-status="" aria-label="book car" aui-step="3" aui-steplocation="uri" />

<clapierre>         <div aui-status="" aria-label="purchase trip" aui-step="4" steplocation="uri">

<clapierre> </div>

<thaddeus> +1 to this

Sharon: want to make sure everyone agrees before updating github

+!

+1

<thaddeus> good work!

Sharon: there was a tag for status but wanted to simplify and fit in with what people are already doing. Left status but removed “actiontaken”

Charles: aui-status is already part of actions?

Sharon: is already part of logs

Michael: need to make sure we aren’t colliding with other vocabulary
... make sure our step means the same thing as HTM step -

<thaddeus> <input type="number" name="points" step="3">

Sharon: step is using in HTML only for numerical items
... this step comes from original logs item; Sharon looked it up in HTML and realizes it is a bit different but hoping aui- prefix differentiates it

Michael: Sharon can add this update, then raise an issue to address the naming later - can we actually use “step”

Sharon: will make edits, open issue and check on term “status”

Charles: Should we take up other issues?

Michael: we should continue addressing issues

Charles: add personalization task force members to participants acknowledgements - Thaddeus isn’t listed

<clapierre> https://github.com/w3c/personalization-semantics/issues/59

<thaddeus> Thadddeus Cambron if you need to add

Michael: Generally Michael or Roy’s responsibility - please open an issue

Charles: issue #59 for Roy

Michael: we should complete this before we publish

Charles: Does personalization semantics work as an aria module? should we try to tackle this right now?

Michael: too difficult to discuss right now but encourages people to think about this for further discussion

<clapierre> https://github.com/w3c/personalization-semantics/issues/53

Charles: RDFa issue

Michael: Michael will assign this to himself

<clapierre> https://github.com/w3c/personalization-semantics/issues/49

Charles: Missting attributes @context

Michael: suspect this is one of the items removed from the first round of publication
... add a comment to the issue - ask reporter to indicate where these references were found

Next issue: https://github.com/w3c/personalization-semantics/issues/47

issue is that “aui-symbol makes no sense”

Charles: the example there was unclear and needs better explanation. Goal is to replace text with symbol and there are conventions for that. Perhaps a better example of sentence “boy chases cat to tree “can be replaces by symbols

Becky: do we need confirmation that this example is correct?

Charles: Lisa has been working with people on better understanding symbols - we need to incorporate what she is learning and provide a concrete example
... Lisa have been meeting with Bliss folks on Symbols

<clapierre> https://github.com/w3c/personalization-semantics/issues/46

issue title: aui-distraction - Description and Supported Values

<clapierre> <aui-distraction="moving ad">

Charles: issues is that it it unclear that attribute (distractions) can support a space separated list
... Seems that we just need to clarify that this can be a space separated list in order to resolve this issue. Is there a formal way to describe this?

<thaddeus> I have to leave for a meeting. I am available to take on tasks

Michael: Yes, but will be different for each meta data language - in personalization we might say to do whatever the host language does. ARIA says that and provides a few host language examples
... We need to clarify the correct approach in each case - multiple values or not
... this structure was copied from ARIA spec, not sure we know enough about all of properties - since we are no longer doing this as an aria module we may want to change how these values work
... does provide a link to token-list (that link is broken and needs to be fixed).
... Assign issue #46 to Michael
... Roy needs to do a link checking pass
... generally link fixing is editorial

(discussion on how to assign issues in github)

<clapierre> https://github.com/w3c/personalization-semantics/issues/45

Issue: “Editorial change to 3.5.2 Example"

Charles: suggests using the example provided in the issue

Michael: suggests asking the filer to create the pull request - and make this a habit going forward

I (probably need to be added to the assignees list

Michael: will send invites to Becky, needs Sharon’s github email

<Sharon> sharondsnider@gmail.com

rssagent, make log public

rssagent, create minutes

Summary of Action Items

Summary of Resolutions

  1. request publication of explainer and content module
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2018/03/12 18:01:19 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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)

FAILED: s/; but that confilict a bit with/is address instead in the/
Succeeded: s/ARIA/HTM/
Succeeded: s/comma/space/
Present: (no one) clapierre thaddeus Roy MichaelC Becka11y Sharon
Regrets: Lisa
Found Scribe: Becka11y
Inferring ScribeNick: Becka11y

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


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

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.)


[End of scribe.perl diagnostic output]