12:30:01 RRSAgent has joined #restyle 12:30:01 logging to http://www.w3.org/2012/10/31-restyle-irc 12:30:15 Zakim has joined #restyle 12:30:22 RRSAgent: help 12:30:37 RRSAgent: start logging 12:30:37 I'm logging. I don't understand 'start logging', Lachy. Try /msg RRSAgent help 12:31:20 Topic: Restyling the Web 12:31:28 ScribeNick:Lachy 12:32:23 present+ fantasai, divya, rigo, tab, simon, oliver, richard 12:32:28 SimonSapin has joined #restyle 12:32:28 present+ Lachy 12:32:40 present+ Robin 12:32:41 Lachy: ping 12:34:47 olivier has joined #restyle 12:34:54 divya has joined #restyle 12:35:04 TabAtkins_ has joined #restyle 12:35:14 RRSAgent: make minutes public 12:35:14 I'm logging. I don't understand 'make minutes public', Lachy. Try /msg RRSAgent help 12:35:23 RRSAgent: make public 12:35:23 I'm logging. I don't understand 'make public', Lachy. Try /msg RRSAgent help 12:35:25 darobin has joined #restyle 12:35:28 RRSAgent: make logs public 12:35:32 fantasai has joined #restyle 12:35:32 RRSAgent: make minutes 12:35:32 I have made the request to generate http://www.w3.org/2012/10/31-restyle-minutes.html Lachy 12:35:35 rock and roll 12:35:50 r12a has joined #restyle 12:36:44 [Showing humerous "under construction" themed spec on screen.] 12:37:00 fantasai: we are gathered here today to bring the W3C spec styling up to date 12:37:04 present+ Matt 12:37:09 present+ Dom 12:37:36 fantasai: this is what our current drafts look like. 12:37:59 … header information is part of the official boiler plate, but it's not consistent. 12:38:08 … Well, it's slightly more consistent than the status section/ 12:38:26 … here's a status section, the TOC, conformance section, acknowledgements 12:38:30 divya: some specs have a list of changes 12:38:39 fantasai: some people find this useful. 12:38:54 dom has joined #restyle 12:39:15 fantasai: the point of this is that there's a lot of junk here. Our goal is to cut the junk and hand it off to a designer 12:39:42 rigo: I have a suggestion. I'm a fan of the Opera bork browser. When it hits the Microsot site, it changes everything to "bork bork bork" 12:39:54 … We could hae CSS to change the status section to this :-) 12:40:10 … Seriously, we coul dhave sections that collapse and expand as needed 12:40:14 matt has joined #restyle 12:40:27 fantasai: so tantek and I got togethet and said, what metadata needs to go into the spec? 12:40:35 … this is the list we came up with. 12:40:42 rrsagent, draft minutes 12:40:42 I have made the request to generate http://www.w3.org/2012/10/31-restyle-minutes.html matt 12:40:53 … e.g. W3C logo, which WG, title, 12:41:05 … Pub date. Needs to front and centre, so you know how recent it is. 12:41:07 Meeting: TPAC 2012 Restyling W3C Specs 12:41:18 olivier: you don't really need the WG. 12:41:20 Chair: fantasai, darobin, divya 12:41:26 fantasai: Status. CR, WD, etc. 12:41:42 MikeSmith has joined #restyle 12:41:49 … status disclaimer. It's long, no-one reads it. But we need something to say that it's a work in progress. 12:42:06 r12a: are you saying we need to have them at the beginning or anywhere in the document? 12:42:13 fantasai: we need them to be easy to find. 12:42:48 rigo: Sometimes there is text for the "Cover Your Arse" case. Rephrasing is not an option. [Legal reasons] 12:43:12 … the question is, how can we maintain a kind of a hint to the "bla bla" that is kind of sufficient, that a court say someone can't have overlooked it. 12:43:20 robin: We have ideas for that. 12:43:27 rigo has joined #restyle 12:43:29 fantasai: hopefully there will be a standard place for that. 12:43:36 … some disclaimer for people new to specs 12:43:50 dom has joined #restyle 12:43:59 … We need a copyright, patent policy, where to find disclosures, errata, issues list, FAQ link. 12:44:06 … Something that not all specs would have, but a common desire. 12:44:12 darobin has changed the topic to: restyling paraphernalia 12:44:25 … the at-risk list, discussion fora (mailng list), editor's draft. 12:44:40 … we'll talk about dealing with the editors draft issues later. 12:44:51 MikeSmith_ has joined #restyle 12:44:59 … test suite link, who are the editors. Important for directly contacting them rather than via mailing list. 12:45:09 … translations and other formats (PDF, etc.) 12:46:01 zakim, mute rigo 12:46:01 sorry, matt, I don't know what conference this is 12:46:06 fantasai: then there's prose things that are common. The TOC, intro and background sections. Some specs have this. 12:46:07 RRSAgent, draft minutes 12:46:07 I have made the request to generate http://www.w3.org/2012/10/31-restyle-minutes.html dom 12:46:22 … Example, use cases and requirements. Transition criteria is needed somewhere. 12:46:25 Meeting: ReStyle W3C specs break otu 12:46:28 s/otu/out/ 12:46:28 … References, indexes, glossaries, etc. 12:46:30 RRSAgent, draft minutes 12:46:30 I have made the request to generate http://www.w3.org/2012/10/31-restyle-minutes.html dom 12:46:35 q+ matt 12:46:42 XXX: It would be great to have a link to the source of the spec. 12:46:58 s/XXX/Tobie/ 12:47:22 … Community groups are often putting their specs on github. It would be useful to link to that from the spec. 12:47:33 MikeSmith: Do you have change logs in that list? 12:47:38 fantasai: We should have that. 12:48:01 MikeSmith: separate links directly to source and change log 12:48:10 dbaron has joined #restyle 12:48:12 tobie: similarly a link to the bug tracker. 12:48:20 dbaron has left #restyle 12:48:29 MikeSmith: do you have the thing for filing the bug? 12:48:30 fantasai: yes 12:48:39 http://www.w3.org/wiki/SpecProd/Restyle/Content 12:48:53 q- 12:48:55 tpacbot has joined #restyle 12:48:57 ACTION fantasai: add changelog link, spec source link 12:49:17 larry: I've been going to meetings in the IETF. Some people are proposing that the IETF specs should be in HTML. 12:49:22 MikeSmith: sounds radical. 12:49:24 sangwhan has joined #restyle 12:49:31 Present+ Larry_Masinter 12:49:33 larry: many people are producing specs with an XML DTD 12:49:38 present+ Tobie 12:49:48 rrsagent, draft minutes 12:49:48 I have made the request to generate http://www.w3.org/2012/10/31-restyle-minutes.html sangwhan 12:50:35 larry: There's been some tooling development. interesting one: A tool tha adds all the boiler plate. Is there any overlap in the tooling for producing RFCs, vs W3C specs. 12:50:43 … particularly, biblio 12:51:26 … One thing I like about tooling is that it's has a property of being idempotent. There is some input format, it populates it with the boilerplate, but that output is suitable for the input. 12:51:43 Lea_ has joined #restyle 12:51:43 … I thought it might be useful for sharing some of the tooling 12:52:15 … That group is meeting to consider their rules for allowing RFCs in HTML. There's been a long discussion and requirements document. 12:52:30 Robin: There's a different session later about the publication process. This is more about styling. 12:52:47 r12a: You've got index/glossay. Why are they together? 12:53:07 tobie has joined #restyle 12:53:12 fantasai: They are separate, but there's a whole bunch of different types of indexes, glossaries, etc. 12:53:17 … can't list them all. 12:53:19 present+ Tobie_Langel 12:53:26 is there something that we've missed? 12:53:36 ACTION fantasai: add changelog link, spec source link 12:53:50 Lea_: http://www.w3.org/wiki/SpecProd/Restyle/Content 12:53:55 dom: It's not something we currently put in W3C specs, but appears in WHATWG specs. Implementation status 12:54:00 … that might be a bit out of scope. 12:54:09 … Not something most specs do nowadays, though 12:54:29 larry: There's a topic that has come up in the TAG re the relationship of specs that normatively reference each other. 12:54:41 ACTION fantasai: Add item for upcoming/previous versions of the technology (if any) 12:54:46 … references to the latest version, specific version, work in progress version, etc. 12:55:29 … If you're making a normative reference to something in the same group, you might want to check that things don't break when a spec updates. 12:55:55 … but referencing work from an external group requires a bit more collaboration to ensure things don't suddenly break with normative changes to the referenced spec. 12:56:43 robin: At least where it concerns W3C specs, We're going to do QA tools that will spider things to notice that you're doing things that aren't a definition. 12:57:25 matt: Deadlines are important. 12:57:36 robin: Last call needs deadlines 12:58:00 q+ 12:58:00 … I don't think we need to find every last peiece of information. We have a lot of high level stuff, we should move on. 12:58:06 matt: Also some specs have not just editors, but also authors, contributors 12:58:30 q? 12:58:34 ack olivier 12:58:34 ack olivier 12:58:59 olivier: there's a number of things that we want to think of in terms of content. Where and whether do we need to list things like IDL, definitions. Is that out of scope? 12:59:01 fantasai: yes. 12:59:24 robin: We will look at that eventually, but not today. This is more focussed on restyling the header and layout. 12:59:40 olivier: I have learned to completely skip that section and go to the "meat" of the spec. 13:00:03 fantasai: the goal is to make sure we have all of the content that we want to have in the boiler plate, and then how to mock up that design. 13:00:19 … brainstorming of what we want to design to be like, but not the specific design. 13:00:24 … that will take about 10 minutes 13:00:33 … we're not going to do any visual designs. 13:00:48 fantasai: mike is bad at design 13:01:25 fantasai: karl dubost took some ideas and produced a sample mockup of what it could potentially look like. 13:01:32 http://www.la-grange.net/2011/12/05/w3c-spec-status-prototype 13:01:42 http://lists.w3.org/Archives/Public/spec-prod/2011OctDec/0095.html 13:01:55 fantasai: this isn't to say it's what it's going to look like, just to show some possibilities. 13:02:10 … this is a blog where someone took boarding passes and started to make them more useful. 13:02:38 … there's a lot of creativity that is not present at all in our concept of what the spec should look like 13:02:48 … but if we provide the parameters, then someone can go and do that. 13:02:55 [[That spec design with ED/WD/LC/etc at the top reminds me: I saw some other orgs specs where they showed what status it was at by listing all status and putting a big X through other statuses, made it very clear. Also appeared to be in (rough?) order, which was nice.) 13:03:17 larry: People like things like seeing a graph of dependencies. Looking at the broader collection of specs, in a group, is useful 13:03:26 fantasai: that's the job of the TR index, not individual specs. 13:04:04 q? 13:04:36 rigo: first of all, I believe on patent policy. It's ok to say there is no incident or there is incident. 13:04:50 … but if there was incident, you need to link to the PAG report. 13:05:21 … Apart from that, it's already sufficient to send this table to the designers and let them unleash the creativity. 13:05:22 MikeSmith has joined #restyle 13:05:43 … what's missing is the concrete markup that is used for each of these sections. Relevant to the selectors used in CSS. 13:05:46 masinter has joined #restyle 13:06:07 … If you do the restyle, please check that there is supportive markup for all sections. 13:06:23 robin: that's not going to be a problem. 13:06:44 robin: We're going to reinvent styling and do it right. 13:06:57 rigo: styling has a semantic aspect. 13:07:04 Robin: yes. 13:07:21 https://datatracker.ietf.org/doc/draft-rfc-format-flanagan/ 13:08:09 fantasai: Robin and I sat down, took karl's design as a starting point and try and put it together as a rough design. Here's an example of the speech module where we tried to do that. 13:08:49 tantek has joined #restyle 13:09:45 http://fantasai.inkedblade.net/style/design/w3c-restyle/ 13:10:11 fantasai: the markup and CSS in this file is really horrible. It needs improvment. 13:10:57 rigo: you can't just show some "bork bork". You should show all of it 13:11:03 dom: Yes you can 13:11:25 rigo: bork bork bork 13:11:26 rigo: You have a sentence that takes a lot of realestate, but no colour difference. 13:11:33 divya: this is just a proof of concept. 13:11:39 matt, better bork bork than nothing 13:11:46 robin: We made this to show that it was possible to take the information. But it's not a design. 13:12:02 fantasai: we're going to throw this out. This is just showing the information in a differnet way as a prototype. 13:12:12 rigo: Why do you have this note and not others? 13:12:23 robin: it's a design decision. 13:12:29 plinss has joined #restyle 13:12:43 dom: You can find the other "bork bork" information later on in the document. This was a design decision based on importants. 13:12:56 s/importants/importance/ 13:12:59 there's a workflow for spec development, have you done the right steps to support the workflow 13:13:39 Present+ Carrine 13:13:44 I question that importance of text is a design decision (and agree what dom said) 13:14:17 s/Carrine/Carine/ 13:14:20 lachy: It's useful to be able to display the information quickly, via icons, etc, like Creative Comments, which expresses large parts of legalese in a small set of icons. 13:14:44 s/Creative Comments/Creative Commons/ 13:14:49 yoshiaki has joined #restyle 13:16:14 fantasai: there's a history section, feedback, 13:16:28 … Licensing is under paraphernailia because we couldn't find a better name 13:16:44 … We tried to group these things to make them easier to find, without putting lots of text right up front. 13:17:09 … Lots more stuff, ending with copyrights and acknowlegements 13:17:11 If I can be a bit of a party pooper, a misc section is a bit of a cop-out though 13:18:12 [[I think that might also be under a label that is perhaps just not the best for now olivier]] 13:18:21 https://npmjs.org/package/html-rfc 13:18:34 tobie: Could it be possible to have different views for different audiences? 13:19:05 dom: More importantly, if you have different views, not all the content will be seen by everyone. No-one will see a lawyer specific view 13:20:22 Lachy: The WHATWG spec tried this. 13:20:50 robin: That creates problems for review. We found in the HTML spec that there were incorrect annotations about what was for authors and what was for implementers 13:20:50 http://www.ietf.org/proceedings/84/slides/slides-84-rfcform-2 13:21:07 dom: Developers don't read specs. 13:21:30 http://cursive.net/draft-hildebrand-html-rfc-2012-07-07.html 13:21:33 rrsagent, make minutes 13:21:33 I have made the request to generate http://www.w3.org/2012/10/31-restyle-minutes.html matt 13:22:10 fantasai: when we redesigned the CSS WG homepage, which is not live, divya came up with a fantastic design. The designer asked the CSSWG how we want the design to feel. Came up with 5 adjectives. 13:22:30 … I want to do the same thing here. Come up with 5 adjectives for specs 13:22:47 sangwhan has joined #restyle 13:22:50 Larry: The formatting should be reviewable. 13:22:56 readable 13:22:58 … form follows function 13:23:03 trustable 13:23:12 approachable 13:23:28 Present+ sangwhan 13:23:31 yoshiaki has joined #restyle 13:24:25 divya: everyone in here should join spec-prod mailing list 13:24:35 http://lists.w3.org/Archives/Public/spec-prod/ 13:24:58 RRSAgent: make minutes 13:24:58 I have made the request to generate http://www.w3.org/2012/10/31-restyle-minutes.html Lachy 13:34:49 rigo has joined #restyle 13:35:25 rigo has left #restyle 13:36:12 r12a has joined #restyle 13:36:34 Lachy has joined #restyle 13:36:50 Lachy has joined #restyle 13:37:17 Lea_ has joined #restyle 13:39:16 dom has joined #restyle 13:39:29 yoshiaki has joined #restyle 13:39:36 sangwhan has joined #restyle 13:39:43 sangwhan has joined #restyle 13:42:48 masinter has joined #restyle 13:45:54 SimonSapin has joined #restyle 13:53:23 MikeSmith has left #restyle 14:04:21 SimonSapin has joined #restyle 14:07:05 tantek has joined #restyle 14:19:30 tantek has joined #restyle 14:28:45 yoshiaki has joined #restyle 14:35:39 public 14:51:19 r12a has joined #restyle 14:55:40 Lachy has joined #restyle 14:57:09 yoshiaki has joined #restyle 15:11:29 tantek has joined #restyle 15:11:47 r12a has joined #restyle 15:13:26 sangwhan has joined #restyle 15:14:05 olivier has joined #restyle 15:14:12 SimonSapin has joined #restyle 15:24:59 Zakim has left #restyle 15:28:26 olivier has left #restyle 15:36:13 masinter has joined #restyle 15:55:02 yoshiaki has joined #restyle 16:08:31 yoshiaki has joined #restyle 16:12:05 SimonSapin has joined #restyle 16:22:15 SimonSapin has left #restyle 16:33:19 Lachy has joined #restyle 16:40:52 yoshiaki has joined #restyle 17:21:25 tpacbot has joined #restyle