This shows you the differences between two versions of the page.
— |
design:20140626-notes [2014/06/26 12:57] (current) rsewikiadmin created |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | === RFC Format Design Team call, 26 June 2014 === | ||
+ | Attendees: | ||
+ | Paul, Joe, Heather, Alice, Nevil, Julian, Tony, Robert | ||
+ | |||
+ | Absent: | ||
+ | Adam, Ted, Dave | ||
+ | |||
+ | |||
+ | 0. Administrivia | ||
+ | * Next call scheduled for 10 July 2014; that is the last call we have on the calendar | ||
+ | Heather to send out a poll after the next agenda update so that the design team can meet. | ||
+ | Joe is tentative for July 10 | ||
+ | |||
+ | |||
+ | 1. Status of existing drafts | ||
+ | * xml2rfc v2 | ||
+ | * draft-reschke-xml2rfc-09 posted | ||
+ | So far, only small editorial improvements, | ||
+ | |||
+ | * xml2rfc v3 | ||
+ | Paul has a stack of small to medium sized things to put in. Some will be impacted by conversations today or on the list. A significant rev is scheduled for next week. | ||
+ | Some of the bigger ones (e.g., are we going to have a micro format for particular kinds of tables?) should be discussed in Toronto. | ||
+ | |||
+ | |||
+ | * draft-hansen-rfc-use-of-pdf | ||
+ | |||
+ | * HTML | ||
+ | * discussion topic: retention of [none|some|most|all] semantic info from the XML? | ||
+ | Joe is willing to back to back off of the strong stance on | ||
+ | Julian is a metadata junkie, and likes having as much in the HTML, so let’s back off on ALL. So, what additional information do we want in the HTML for which there are customers (e.g., search engines). | ||
+ | |||
+ | (Paul) the semantics we currently have for ‘id=‘ will help with this quite a bit. (Joe) we could also use classes; the less that we polite the name space in IDs with semantics will be helpful. | ||
+ | |||
+ | (Paul) Like using id’s for single sections that we know what they are - any objection? | ||
+ | |||
+ | (Paul) this will make things easier in the XML draft, and make the the HTML | ||
+ | auto generated id’s for: section, figure, paragraph (numbered within a section) | ||
+ | |||
+ | (Joe) prefer prefix to blacklist or whitelist; search engines will still find something like prefix-copyright. | ||
+ | |||
+ | (Paul) prefix shouldn’t be “rfc-” or “id-” or “x-", | ||
+ | |||
+ | The advantage here is that people who haven’t seen this RFC can still index into it in relevant places. | ||
+ | |||
+ | Paul will need to add auto generating paragraph to the xml2rfc v3 draft; (Julian) adding paragraph will be a bit of an exercise to figure out tables and figures; a complete list will still be a paragraph when it is not a top level. | ||
+ | |||
+ | Section 2 starts with a heading, then a whole paragraph, then a free standing list, then a paragraph. | ||
+ | |||
+ | (AOB) 2119 markup | ||
+ | * the concern of many people is that if we start doing things differently, | ||
+ | * (Paul) should the canonical RFC retain what the author did? (Julian) if it has no significance other than styled differently, | ||
+ | * (Paul) then propose we come up with something like <em> (which would turn into a span of the appropriate class) that says you can do < | ||
+ | * (Julian) has been doing that with his extensions for a while, and can come up with a concrete proposal right away. (Paul) that’s not the concern; needs to know the restrictions, | ||
+ | * (Joe) capitalization can remain up to the author, and we might decide to provide entities for people that don’t want to type the closing tags every time. We are already going to have to expand the I-Ds anyway. | ||
+ | In HTML this will turn into <span class = bcp 14> | ||
+ | |||
+ | |||
+ | 2. Remaining drafts to be created | ||
+ | * XML examples: " | ||
+ | |||
+ | Julian and Paul haven’t start on this, and probably won’t have it this week. May have a -00 when the window opens in Toronto. | ||
+ | |||
+ | Remember Tony has a fairly complete conversion tool drafted. | ||
+ | |||
+ | |||
+ | 3. IETF 90 | ||
+ | * IAB session on RFC Format expected | ||
+ | * topics for that session: update on each draft from the authors; estimated timeline for project; CSS prototypes | ||
+ | |||
+ | |||
+ | 4. AOB | ||
+ | ** (Julian) if we have time I'd like to demo by new XSLT/ | ||
+ | ** (Heather) plain text brouhaha | ||
+ | ** (Nevil?) anything more to say about the SVG draft? |