ZedAI telcon 20081117
From zedwiki
Contents |
Present
Markus, Gregory, Matt, Marisa, Per, Ole, Stephen
Regrets: Kenny, Boris, Sam
Action Item Summary
New Action Items
- Per: continue frontmatter content model discussion on list (ref: RNIB Book DTD)
- Per: reiterate em+strong at list
- Matt: send ToC example to list
- Per: compare of Matts and Stephens ToCs
- Gregory: post NewsML G2 info to Wiki, notify list.
Action Items carried over
- Markus fix ZedAI main page, start a ZedAI Overview page
- Markus to follow up the contact with the xhtml2 WG.
- Markus/Per - discuss pros/cons of the XHTML2 modularization framework (started at ZedAI W3C Modularization and XHTML2.
Minutes
XHTML2
Gregory: on XHTML2 timing, the W3C WG will talk about this topic on Wednesday.
(Email: http://lists.w3.org/Archives/Public/public-xhtml2/2008Nov/0011.html)
Markus: these are estimated DAISY dates, based on the NISO process:
- November 2009: XHTML2 at least LC
- Six months NISO-mandated public review period which means April 2010 latest date for rec status of XHTML2.
Gregory: Role, Access and Curie modules are being finished, hoping by 1st quarter have CR for all of these
Then we need to go through again outstanding issues of XHTML2. Suggest we talk with Roland and Steven on this.
Telcon Time
Decide to postpone the time discussion to next week (need Sam and Kenny to be present).
Action Item Review
zednext-ai list is created.
Gregory has worked NewsML G2, far more suited for our needs. @Gregory post NewsML G2 info to Wiki, and notify list.
All other items carried on.
Discussion on simple/leisure book profile
Markus: remember that this is an iteration prototype only; we dont make any final decisions at this point. Final modifications will be made during public review period at the end of the NISO process.
front- and rear matter
For now, suggest to go for the content model: x:html/x:head, x:html/d:front, x:html/x:body, x:html/d:rear --
An alternative would be x:body/d:frontmatter, x:body/d:bodymatter, x:body/d:rearmatter -- which would be more compliant with classic XHTML expectations, but creates some pedagogic difficulties (body/bodymatter).
A third alternative would be to use xhtml2:section with @role -- but @role is not a substitution for a dedicated element.
Discussion on the axis on avoiding duplication and allowing restructuring at output rendering time, and at the same time allowing a faithful transcription. Use metadata only to capture author/title, or also provide means to capture it in frontmatter?
General consensus seems to be that frontmatter content model should be extended as compared to DTBook, as this is a prerequisite for output restructuring and machine-based decision-making.
Stephen mentions RNIB DTD frontmatter elements such as title, subtitle, author, dedication, epigraph, publishers-adress, copyright, toc @Per: continue with frontmatter content model discussion on list
pagebreak
No type attribute needed. (Refer to JPs argumentation at z3986 list) Suggest to go for the following: pagebreak @value="anyString" pagebreak with no attribute at all, for pages with no value (neither printed nor calculated)
w (word)
Do we need it in this profile? Yes, for i18n (xml:lang).
XHTML2 constructs to keep in simple profile
We need to add lists, tables, image (or rather, xhtml2:object module) to elements already included.
Markus: "Simple" vs "Advanced" may as stated before dissolve into one book profile, unless we opt to go for the inclusion of MathML, Ruby etc natively into the Advanced profile.
strong, em
Stephen: we are using italics, bold, underlined element names instead of em+strong @Per reiterate em+strong at list
front/toc (Pers example)
Stephen, we call it "contents", and not reusing listitem
Markus: Matt sent a DTD fragment to the list as well.
@Matt send ToC example to list
@Per compare of Matts and Stephens ToCs
quote
We need both quote and blockquote
poem
Markus: poetry books could deserve their own profile (as could plays). But this is about poems inlined in more standard leisure.
Decision to skip poetry entirely in this iteration and worry about it later.
Agenda
- Choice of time for the telcon. Is 13:00 UTC still our best choice?
- Previous Action Items
- @Markus Create a list where all the participants of this group could talk.
- @markus fix ZedAI main page, start a ZedAI Overview page
- @Markus to follow up the contact with the xhtml2 WG.
- @Kenny - Is NewsML modular? How is their schema built? Need more info on the wiki.(kenny and Gregory to post more information about NewsML g2 on the wiki)
- @Markus/Per - discuss pros/cons of the XHTML2 modularization framework (started at ZedAI W3C Modularization and XHTML2.
- Simple/Leisure Profile document model discussion
Recap questions asked by Per on list, and try to reach a tentative solution.
