ZedAI telcon 20100118
From zedwiki
Note: this meeting will be held at 2100h UTC. Find the meeting time in your geographical location.
Contents |
Present
Markus (scribe), Matt, Per, Kenny
Regrets
None so far
Previous Telcon
Action Items
New
@Matt: review inline markup in bibliography, glossary, index
@Kenny: send summary of use case for continuation indicator to list.
@Markus: close issue 44: deferred until proper Braille Feature is built.
Brought Along
- markus add issue to tracker: may be necessary with publisher address in inline reqd metadata.
- markus fix object mimetype enum before release {DONE}
- markus add simple SVG CDR feature before release {DONE}
- James take a stab at this tuesday, then notify Markus (DONE}
- Sam: go through contentselection feature sample with markus {DONE}
- dennis find out if math:switch supports mathml-for-css
- dennis, on MathML_ what symbols are used to denote the switch types? point us to where switch is explained. Need to figure out relation to our content selection feature.
- markus: add math role to vocab, add prose to MathML feature doc that explains its restricted use.
- markus check how math/@id and else/@xml:id works in RelaxNG and XSD.
- markus investigate pros/cons of going back to using id?
- markus implement simple SVG feature (object only) {DONE}
- Boris: start documenting object and annotation {ONGOING}
- Boris/Markus - ask ViewPlus et al about the SVG namespace-inject issue [ONGOING @markus]
- Kenny - own the page continuator issue (note, we have a similar lurker in terms of running heads)
- Boris: help deal with svg integration, help with object documentation and samples, address issue 9 [ONGOING]
- Dennis: solve Issue 60 {DONE}
- Dennis: solve Issue 61 {DONE}
- Dennis: solve Issue 46 {DONE}
- Josh: solve Issue 50 {DONE}
- Markus to add spec prose on cascading level for inline styles: "For the purposes of the CSS cascade, these values are considered author-level" {DONE}
Agenda/Minutes
Welcome Christian and Manfred, SBS
Refactoring Status Update
(Markus, Per to give short status update)
- Target 1 : replace the current "core markup model" part of the spec with a general abstract document model definition, and a listing of all modules in the "core module pool", abstractly defined
- Target 2 : enable features to use the same mechanism (in their Resource Directories) to define what they contribute, and where
- Target 3 : (Per), some changes/fixes/improvements to schemadoc generation
Once all this is committed (approx 2 weeks from now), focus on completion of grammars, proofing, bugfixing. More sample production will be necessary.
Timeline remains, but may not be DSFTU in april because of dependencies to ZedDist (this is a NISO decision); if not DSFTU, public review period (equally useful, and allows changes/fixes to be injected with minimum hassle).
Per: schemadoc version 2 will be done late february.
Remaining MathML work
This issue is deffered til next time Dennis joins
- Math role to vocab (see z3986-core.n3)
- other similar properties to add?
- prose to Math RD about the limited use of the role property
- built-in math:switch versus our content selection feature? Think we should choose one. Important to support copy-and-paste.
- (dennis) does the built-in math:switch support mathml-for-css?
Reminder: Dennis on MathML 'dialects':
The variety of schema choices permits use of particular subsets of MathML 3. As with MathML 2, MathML 3 provides two major "dialects" - content and presentation. MathML 3 adds "strict" and "pragmatic" variations to content MathML.
So which schema fragments to use will be determined by which type of MathML we support in Zed Next: Presentation, Strict Content, or Pragmatic Content.
I suggest we take the same approach as in the existing MathML-in-DAISY spec. It states that Presentation MathML MUST be used and Content MathML is optional via parallel mark-up. In parallel mark-up both Presentation and Content MathML are given and the rendering agent can choose between them.
If we take this approach, then we should use either the Presentation-only schema or the complete schema. To use the Presentation-only schema we use:
include "mathml3.rnc" {MathExpression = semantics | PresentationExpression}
according to http://www.w3.org/TR/MathML3/appendixa.html#parsing.rnc.module. To use the complete schema we use:
# A RelaxNG Schema for XHTML+MathML include "xhtml.rnc" math = external "mathml3.rnc" Inline.class |= math Block.class |= math
Inline markup in bibliography, glossary, index
Taker needed. Requirements for inline markup of these block-level elements not yet defined.
Probably does not require definition of new elements, rather refinements of existing content model.
@Matt take a look at this.
Running headers
See issue [44].
Taker needed. Is this 100% Braille-specific, or is there a use case for capturing page-headers and page-footers as they appear in the source?.
Matt: running headers for books and braille volumes are completely different things.
Kenny: print pages translated into Braille... running headers as Kate referred to the braille output pages. Is only relevant if there is a choice, else it can be autogenerated.
Matt: it cannot always be autogenerated, there are contractions of several headings etc done to make it fit on the top page line.
Kenny: is it possible do this contraction via automation? Matt: unlikely.
discussion on Duxbury formatting ensues...
Markus: should we approach this now? We dont have a Braille Feature at this point (trying to make the core grammar rich enough for most Braille needs, but this is 100% Braille specific.)
Matt recommends not opening this issue now, too Braille specific.
Conclusion to defer this until a real Braille Feature is built.
Page continuation markup in newsfeeds profile
This is an action item on Kenny. @Kenny send summary of use case for continuation indicator to list.
Next call
Monday 1st of February.
