<Mark_Wilcock> @Lisa My current meeting is over running, I will try join when it is complete
<LisaSeemanKestenbaum> scribe: roy
<LisaSeemanKestenbaum> scibe: JohnRochforb
<LisaSeemanKestenbaum> scibe: JohnRochford
<JohnRochford> scribe not scibe
<LisaSeemanKestenbaum> scribe: JohnRochford
Lisa: we will wait until next
call to address document navigation
... about doc, likes John K's comments, and notes Jan asked for
more headings
Lisa, Glenda, and John R agree "helps" is better than "benefits".
John K: I'm not sure we are capturing purpose.
Lisa: Do we prefer more details or more notes?
Glenda: We could add the word "optional" to each.
John K: We could add the word "suggestions" to each.
Correction - Lisa: Which phrase do we prefer, "more details" or "more notes".
?
John K: Expresses ambiguity.
John R: forced by Lisa, choosed "more details"
chose
Lisa: "more details" it is!
John K: We should make sure breadcrumbs provides more detail than title, subtitle, heirarchy.
provide
John R: a title must be clear by itself, and not depend upon breadcrumbs for that
Glenda: I agree with John R.
Lisa: In doc, adds "Failure example:: heading that doesn't clarify the step in a form"
Lisa, in doc, adds "Heading need to clarify the purpose of this page specific page"
Glenda: I suggest headings are indented.
Lisa: We will later port this doc to a W3C template.
Glenda, to Lisa: May I show you what I mean by modifying 1.1?
Lisa: I added that to the ToDo list for when we publish.
Glenda and John K agree indenting is useful to understanding the doc.
Lisa: At bottom of doc, I put
what I think will be a voting box.
... The question would be, "Is this design requirement ready
for the next working draft? "
Glenda: I suggest that, above the voting box, we add "Future To Dos".
Lisa: I will add those to the box/table.
Glenda: I suggest that, near or at the top, we should add resources and history.
Lisa: I like that idea,
especially for policy creators.
... We could add them to a different table.
Lisa, to doc, added "Use 1.1 as an example."
Lisa, in reply to a question from Glenda about numbering: We will use the W3C's auto-numbering system.
Lisa, about "chunking" doc, says: We can do whatever we think it will make it more readable.
Glenda: I acknowledge John K: dislikes "manageable," but I think "manageable blocks" is better than "chunks".
John R: Suggests the word "chunks" may not translate to other languages well.
<LisaSeemanKestenbaum> scribe: roy
<JohnRochford> Thanks, Roy!
<JohnRochford> Gotta go to LVTF call.
Lisa: the paragraph should be
separated
... I will move it
... we should make it testable
... how about move it to notes?
... we can make it simple, single paragraph to show that
... put it more details
John: would like to use single paragraph
Glenda: short sentences and to link this section?
Lisa: like to use single point
per paragraph
... we are going have tables, we did samples, it's helpful to
people who has trouble in language, so chunks may help them,
that may be a place we try to do something
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) Present: kirkwood JohnRochford Glenda Roy Regrets: alister jan shari Found Scribe: roy Found Scribe: JohnRochford Inferring ScribeNick: JohnRochford Found Scribe: roy Inferring ScribeNick: Roy Scribes: roy, JohnRochford ScribeNicks: JohnRochford, Roy WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth 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: 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]