This shows you the differences between two versions of the page.
— |
design:20150120-notes [2015/02/03 14:08] (current) rsewikiadmin created |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | Attending: | ||
+ | |||
+ | Julian, Nevil, Paul, Alice, Tony, Heather | ||
+ | |||
+ | 0. Agenda bash | ||
+ | |||
+ | 1. Draft review | ||
+ | - xml2rfc v2 draft - testing the *refs; Julian hasn’t had a chance to work on those; hopes to get to this before the end of January | ||
+ | |||
+ | - xml2rfc v3 | ||
+ | |||
+ | Paul: had a a few changes today thanks to some input from Miek Gieben through rfc-interest. | ||
+ | |||
+ | * What to do about xml:base and XInclude? | ||
+ | |||
+ | Julian: We decided that rather than inventing our won inclusion, we would use xincludes. | ||
+ | |||
+ | Having the attributes on the elements that were replaced can be useful, but if the processor includes that, then the resulting document will not be valid according to our vocabulary. | ||
+ | We can say if you want to validate the document according our schema you have to strip the attributes. | ||
+ | |||
+ | Tony: we should allow the attributes, at least where we expect includes to be generating stuff. | ||
+ | |||
+ | Julian: two obvious candidates: references and artwork | ||
+ | |||
+ | Paul: but if we do that, we have to say that those are the only places where you’ll have valid afterwords, so if you use xinclude anywhere else, then you are going to generate unvalidatable code OR we’re going to have to post-process and the processor will have to be smart enough to know what to strip and/or what to leave in. | ||
+ | |||
+ | Julian: if we allowed them everywhere, it would make the grammar ugly. | ||
+ | |||
+ | Tony: think we should allow it everywhere. | ||
+ | |||
+ | Paul: what if we have two different grammars - what we have today, and one with optional xml:base everywhere. | ||
+ | |||
+ | Tony: would need to very carefully describe what the differences are. | ||
+ | |||
+ | Need to discuss this on the list, including fleshing out actual use cases. | ||
+ | |||
+ | |||
+ | |||
+ | Tony: made a variety of edits to the document, still have more to make. Larry Master has a few sections to update as well. Note that Tony will be gone all next week, and really hopes to have an update by the end of this week. | ||
+ | |||
+ | 2. Timeline | ||
+ | - Action item from last call: timeline for examples draft | ||
+ | |||
+ | Paul: Note that the draft is not complete. | ||
+ | |||
+ | So, need to add more interesting things from v2 and how they will appear in v3, and more examples of v3 stuff. | ||
+ | |||
+ | Robert: is this document the place that will be a repository of instruction on how to deal with deprecated elements, or is that captured somewhere else? That’s captured in the v3 document. | ||
+ | |||
+ | Paul: the examples draft is for developers and people creating their own converters. It is not an instructional guide for upgrading. | ||
+ | |||
+ | Alice: the xml2rfc FAQ could be updated with “how do I get it to do foo” questions. | ||
+ | |||
+ | Robert: There is a test document that the xml2rfc code suite uses as part of regression testing. | ||
+ | |||
+ | http:// | ||
+ | |||
+ | Pointing to a v3 test document, based on the v2 test document, should go in the SoW. | ||
+ | |||
+ | Tony: the v2 to v3 converter didn’t have any errors when run against draft-mike-test. | ||
+ | |||
+ | Robert: looking at the publication converter, can finish up that SoW by pointing at the examples and the v3 document on how to deal with deprecated elements. | ||
+ | |||
+ | 3. AOB | ||
+ | |||
+ | Alice: Regarding the tables and whether a center attribute needs to added to every box, what was the conclusion there? | ||
+ | |||
+ | Paul: we should be explicit. | ||
+ | |||
+ | Julian: Are we sure that centering heading implies that the contents of the column should be centered? | ||
+ | |||
+ | Paul: OK with people being more specific. | ||
+ | |||
+ | Julian: v3 shouldn’t be harder than v2. | ||
+ | |||
+ | Paul: we are going to be arguing about what different kinds of users might like different things. | ||
+ | |||