15:35:02 RRSAgent has joined #coga 15:35:02 logging to http://www.w3.org/2016/03/14-coga-irc 15:35:20 regrets: JMary Jo Mueller, 15:36:29 agenda: this 15:36:31 agenda+ review actions, and timelines 15:36:32 agenda+ Michael - what help he needs for the issue papers 15:36:34 agenda+ Tables for roadmap 15:36:36 agenda+ What have we missed for issues page,Emma, globish etc 15:36:37 agenda+ be done 15:55:11 JohnRochford has joined #coga 16:02:41 Mike_Pluke has joined #coga 16:03:32 michae;, canyou unmute 16:03:37 michael 16:05:31 ddahl has joined #coga 16:06:26 Rich has joined #coga 16:07:04 present+ Janina 16:07:16 KurtM has joined #coga 16:08:17 scribe: janina 16:08:25 scribe Janina 16:08:37 next item 16:09:14 ls: Timelines are we wish we were already publishing 16:10:01 ls: Suggests we may be OK to ask our parent WGs for publishing permission 16:10:22 zakim, next item 16:10:22 agendum 2. "Michael - what help he needs for the issue papers" taken up [from Lisa_Seeman] 16:10:57 ls: Main question is how to clean up the docs ... 16:11:24 http://www.w3.org/2001/06/manual/ 16:11:31 mc: Main thing to know is to follow W3C manual of style 16:11:52 https://www.w3.org/respec/ 16:12:00 mc: Much literal styling is done by a respec script 16:12:23 mc: hrefs need to be styled appropriately per above URI 16:13:00 mc i.e. [wcag20] which is then referenced in its own section at bottom of doc 16:13:22 mc: Just putting in links is inappropriate 16:13:39 [[WCAG20]] 16:13:59 mc script would pick up the above and appropriately convert the shorname 16:14:31 john: I'm unclear ... 16:14:36 EA has joined #coga 16:14:40 mc: I'm mixing up two pieces ... 16:14:44 https://www.w3.org/2001/06/manual/#References 16:14:58 mc: This says how output doc looks 16:16:02 mc: However, we also use respec, and therefore 16:16:25 https://www.w3.org/respec/guide.html#references 16:17:27 mc: respec is a script already attached to our documents; offers a shorthand using double brackets 16:17:58 [[wcag20-ext-reqs]] 16:18:17 mc: e.g. 16:19:19 john: Is there a list of the shortnames? 16:19:21 mc: no 16:19:38 https://www.w3.org/TR/2016/WD-wcag2-ext-req-20160105/ 16:20:06 Latest published version: 16:20:06 http://www.w3.org/TR/wcag2-ext-req/ 16:20:06 mc: Look at "latest published version" in the document 16:20:08 Is there a template we can all use for our issue papers to get this all correct. 16:20:38 mc: for any W3C publication, it's after the tr/ and up to the next slash / 16:20:53 mc: There are some not in the db, however 16:21:09 mc: So we've created our own db listings 16:21:23 https://raw.githubusercontent.com/w3c/coga/master/common/biblio.js 16:21:38 mc: Unfortunately not the easiest to look at 16:21:51 "ADI-1": 16:21:54 mc: references al start in quotes followed by colon 16:22:01 "title": "World Alzheimer Report 2010", 16:23:01 "ADI-1": 16:23:01 { 16:23:01 "title": "World Alzheimer Report 2010", 16:23:01 "publishDate": "2010", 16:23:01 "authors": ["Alzheimer's disease International"], 16:23:02 "etAl": false 16:23:04 }, 16:23:52 mc: look up before the brace (curly bracket) 16:24:22 ls: If not referencing standard W3C doc, one looks into this resource 16:24:28 [[ADI-1]] 16:25:39 ls: If anyone uncomfortable about getting this right, contact me with complete reference -- and include a shortname, please 16:25:53 mc: Suggest Lisa or el choose the shortname 16:26:09 mc: I'm not suggesting everyone learn how to update the bib file 16:26:16 @@reference to docname 16:26:48 mc: the @@ is a W3C convention marking something that needs cleanup 16:27:07 ls: But check if it's already there! That will save time. 16:27:27 ls: If it was in the research docs, it's probably already there. 16:27:36 ls: Does this help? Are there questions? 16:27:42 q? 16:28:15 ea: Still a bit concerned that we have too few of us on the call, and yet so many docs to cover 16:28:42 ea: Wonder about how to be efficient 16:29:02 [[ea1]] 16:29:46 ea: Hoping we can develop a template by end of this call, something plain 16:29:54 +1 to EA's template idea 16:30:16 mc: Agree we should shift gears, there are other issues perhaps more tractable 16:30:53 mc: So, to recap, there's a W3C style sheet and scripts attached to our docs that help 16:31:09 mc: So, more detail on the email I sent ... 16:31:14 mc: First structure ... 16:31:30 mc: We need nested structure 16:31:41

Heading

Content

Sub-section

16:32:23 mc: Every section needs a heading, the script will take care of the actual level number 16:33:05 mc: The script will generate a TOC using the nested structure 16:33:24 mc: So, look at the generated ToC to see whether nesting was done correctly 16:34:09 mc: Next item, we need well formed code. If some tag is opened, we need to be certain it's also closed at some point. 16:34:36 mc: Beyond that, spelling and grammar is also very important. 16:34:49 mc: Also, we need to check URI .. 16:35:06 As the WCAG extension requirements at https://www.w3.org/TR/2016/WD-wcag2-ext-req-20160105/ say 16:35:21 mc should be 16:35:40 As the WCAG Extension Requirements [[wcag2-ext-reqs]] 16:36:18 mc: Above is an example of cleaning up a naked URI 16:36:30 mc: We need also to check understanability of the document. 16:36:42 mc: Key to that is a very good intro section. 16:36:57 q+ 16:37:31 mc: There should be a direct flow, with concepts properly flowing one to the next 16:38:24 ls: Do we need to orient the reader on an issue paper by issue paper level, or does the global grouping cover the orientation 16:38:38 mc: We may need to work on this 16:38:55 mc: Probably needs something up top that explains how this issue paper is different from others 16:39:11 Ryladog_ has joined #coga 16:39:28 ls: Perhaps a boilerplate for our use? 16:39:33 Present+ Katie Haritos-Shea 16:39:37 mc: Sometimes these weren't filled out! 16:39:54 mc: If we do use, they need to be completed -- or an editorial note that it's yet to be done. 16:40:13 present+ Debbie_Dahl 16:40:31 Happy to follow a standardised boiler plate for issue papers as they are not too long. 16:40:52 i sent it a private chat katie 16:41:07 mc: TF should come up with the approach, but then follow through to be consistent and complete 16:41:24 ls: Questions? 16:41:41 MichaelC has changed the topic to: COGA TF WebEx https://mit.webex.com/mit/j.php?MTID=m27e5ef0c252bb8db450d25dcef93e8b8 pwd w3c meeting 649 368 070 16:42:28 ea: Happy to follow a structured template ... This is very helpful 16:43:00 ls: Would an example page be helpful? 16:43:03 ea: Yes! 16:43:29 +1 to example boilerplate 16:43:47 action lisa to write sample page 16:43:47 Created ACTION-157 - Write sample page [on Lisa Seeman - due 2016-03-21]. 16:44:05 ea: It's a challenge to do this correctly when other work has its own requirements. Good templates and specifics really help. 16:44:26 %s/john:/jr:/ 16:45:14 ea: Also a finished issue paper would be helpful! 16:45:35 ls: Good. I'll do one -- but may not succeed at grammar! 16:45:58 ea: Happy to correct spelling and grammar! That works for me! 16:46:24 Janina, what does the following mean? %s/john:/jr:/ 16:46:26 ls: OK. I'll do an example paper, and also create a checklist of what needs doing 16:46:56 ls: We should now decide what sentences we want at the top of each paper. 16:47:05 ls: Also, do we need github help? 16:47:13 khs: Need github help 16:47:47 mc: Let me talk github basics ... 16:47:54 mc: It's well documented 16:48:06 mc: First step is get an account on github.com 16:48:07 https://github.com/ 16:49:07 curt: Easy to find the docs when first you setup, but then becomes hard to find 16:49:49 mc: Most likely then you will want to download a github client 16:50:02 mc: Then you clone the repository 16:50:06 https://github.com/w3c/coga 16:50:22 https://github.com/w3c/coga.git 16:50:51 mc: This creates a local copy where you can edit and save 16:51:11 Ryladog_ has joined #coga 16:51:11 mc: Now the client will notify that there are changes you may want to do something about 16:51:23 mc: Next, you might commit the changes 16:51:49 mc: Will ask for a summary, so you say what you did so people can tell what your changes were 16:52:00 mc: Now only half way done! 16:52:12 mc: Above commits to a local db. Next need to be uploaded 16:52:20 mc: It's called either push or sync 16:52:32 mc: Which uploads my changes and grabs any others have made 16:52:57 mc: It's possible to run into conflicts if two people were making changes in the same part of a doc 16:53:28 mc: Strongly suggest editing in small chunks. Push early and often to avoid clashes! 16:54:41 Janina notes github also well supported at the command line 16:54:54 ea: Asking about a good Win client 16:55:09 mc: Suggest the official github client 16:55:34 mc: Noting that any git client can work with github, but may be more challenging to setup 16:56:06 This is an issue paper looking into how cognitive disabilities are affected by …. 16:56:07 It is part of a series of issue papers is part of the gap analiais of the 16:56:29 ... 16:56:35 what the xxxxx 16:57:01 ls: Asking for opinions on the above suggestion ... 16:57:32 rrsagent, make minutes 16:57:32 I have made the request to generate http://www.w3.org/2016/03/14-coga-minutes.html janina 16:58:11 mc: Notes that the issue papers inform the gap analysis, but are separate publications 16:58:20 ls: But would the above be sufficient 16:58:26 mc: Perhaps, if the cover page has more 16:58:47 ls: Something more? 16:59:02 mc: I haven't figured out how to put the issue papers into the overall mix 16:59:21 mc: One doc? Separate docs? 16:59:50 mc: If seperate, need a main file with overall TOC 17:00:46 ls: Expect we'll be adding issue papers as new issues arise. So perhaps we're publishing separately and adding to a main TOC? 17:01:17 mc: Either XX separate pubs, or one called "Issue Papers" were the entire doc is republished for each new added issue paper. 17:01:31 mc: Notes that all of HTML is republished daily now, for better or worse! 17:01:57 ls: Worried about versioning 17:02:19 mc: There's normally dated and undated. Recommendation is to href undated which gets the latest 17:03:04 mc: Suggest relying on the "latest" approach as a hard rule. 17:03:17 Rich has joined #coga 17:03:35 rrsagent, make log public 17:04:34 ddahl has left #coga 17:05:04 zakim, bye 17:05:04 leaving. As of this point the attendees have been Janina, Katie, Haritos-Shea, Debbie_Dahl 17:05:04 Zakim has left #coga 17:05:10 rrsagent, make minutes 17:05:10 I have made the request to generate http://www.w3.org/2016/03/14-coga-minutes.html janina 17:05:41 rrsagent, bye 17:05:41 I see no action items