Silver Community Group Teleconference

24 Aug 2018


KimD, jemma, jeanne, Lauriat, AngelaAccessForAll
John_Kirkwood, jan_mcsorley
Jeanne, Shawn


<scribe> scribe:Jemma

Survey on CSUN F2F meeting

<jeanne> https://lists.w3.org/Archives/Public/public-silver/2018Aug/0045.html

<jeanne> https://docs.google.com/forms/d/15VnXYivdrLjOe17Jt9ZkrF6EphS1aQCPwfgct_JYfcM/edit

Combined Plain Language prototype update

<AngelaAccessForAll> https://docs.google.com/document/d/1D-4Uro0KX_Q4BtsPblIgyHc2AVKeW8Bq3VeBMkXd_Do/edit?usp=sharing

angela: What I did was that I took into consideration for several prototypes and combined each
... I appreciate any feedback for the proposal

jeanne: should we need to use WCAG numbering?
... we can add numbering as reference, ie. (formerly WCAG 2.4.10)

jemma: "who must do this section" has object and platform(ie. simple website, mobile application), not only "who".

shawn: yes, it seems that we are mixing plain lanuage prototype with conformance model prototype.

jeanne: "linking to point system" here is a hook
... we can take out this into conformance seciton. - updated the doc.

jemma: these are all the good info but it seems to be lengthy.

Shawn: similar opinion with Jemma - Furthermore, it may get longer if we get to the complex example. we may try to use a complex example to see.

angela: good idea.

rrsagents, make minutes

shawn: it would be good we just do one prototype for each model and test it out.

kimd: wondering "How" section fits into SC content

shawn, LuisG: we can keep the structure and translate other info into another doc.

jeanne: silver proposal is having the same SC heading and put "understanding doc" under the SC heading

jemma: clear project scope definition for each model would be beneficial.

New information architecture proposal

<jeanne> https://docs.google.com/document/d/1CBk9qG5u5LGJa9pIvou5JsqxnZFiROyeuUN6fmhU3D8/edit#

The group discuss the info architecture doc- taging system, flattening the structure, API consumption- and comments from Alastair

shawn: we can aim for creating example and testing for each.

jeanne: this data structure will be many to many relationship according to the chat with MichaleC yesterday.

shawn: that would be fantastic.

jeanne: please add feedback and comments to the doc.

shawn: one thing I would like to suggest is that testing whether this data structure will be scalable and flexible to add more technologies and examples.

kimd: tagging will be the key things.

for this

jeanne: do we have already tagging doc for this? If not, I will start one.

rrsagents, make minutes

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2018/08/24 19:02:28 $

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)

Succeeded: s/other doc/another doc/
Present: KimD jemma jeanne Lauriat AngelaAccessForAll
Regrets: John_Kirkwood jan_mcsorley
Found Scribe: Jemma
Inferring ScribeNick: jemma
Found Date: 24 Aug 2018
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]