ZedAI telcon 20091130
From zedwiki
Note: this meeting will be held at 2100h UTC. Find the meeting time in your geographical location.
Contents |
Present
Markus (scribe), Boris, Per, Dennis, Josh, Sam
Regrets
Kenny
Previous Telcon
Action Items
New
- sam: go through contentselection feature sample with markus
- dennis find out if math:switch supports mathml-for-css
- dennis what symbols are used to denote the 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)
Brought Along
- Boris: start documenting object and annotation
- Sam - write a sample of content selection feature - multilingual document - declaration of human rights DONE - NEEDS REVIEW, see Issue 87 @markus and sam talk on friday
- 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)
- Markus Matt, James, to create a wiki formulating an out-of-line metadata proposal. Then circulate to interested parties (IFLA group, WIPO, board, etc) [ONGOING]]
- Boris: help deal with svg integration, help with object documentation and samples, address issue 9 [ONGOING]
- Dennis: solve Issue 60
- Dennis: solve Issue 61
- Dennis: solve Issue 46
- Josh: solve Issue 50
- Markus to add spec prose on cascading level for inline styles: "For the purposes of the CSS cascade, these values are considered author-level"
Previous Minutes
Agenda/Minutes
Reminder: ZedAI_Iteration4_Report#Deliverables_for_the_next_iteration deliverables for the next iteration
Note: discussions ongoing with W3C PF re the future of W3C Role (help by Gregory)
Note: [r451], done today, includes the current state of lists and metadata changes.
SVG feature
Decision to do the first version as an object-only feature.
Timelines
Markus and George talked to NISO. We need three dates:
- date for this iteration release (can postpone SVG): December 21
- date for RC draft iteration release (must include all artifacts we intend to ship, only documentation polishing and bugfixes after this release) February 15
- date for submission as draft standard for trial use: End March 2010
Major remaining items before RC:
- schema and module documentation (the latter is abstract definitions of core modules (in spec) and feature modules (in feature RDs)). @Per and Markus talk about that
- spec finalization, primer updates
- SVG integration
- object mimetypes
- (optional but lots of fun) magazines+journals profile
- (optional but lots of fun) drama feature (TEI P5), drama profile
Metadata
Are we ready to commit to the new solution? Topic page: ZedAI_Meta_Data_-_OutOfLine_Proposal
(Spec editors: see ZedAI_Meta_Data_-_OutOfLine_Proposal#Consequences_on_the_spec)
Current vocab: z3986-decl-rdfa-vocab.html
Q to James: is publisher contact info needed.
Markus: meta[record] should reference a resource... if resource="." then you can use the document rdf/a to make the document its own bibliographical record if you want to.
Lists
Status update
Topic page: ZedAI_Lists_Proposal
Current state on trunk:
- z3986-list.rng
- z3986-bibliography.rng
- z3986-index.rng
- z3986-glossary.rng
- z3986-feature-rend.rng (list/listitem prefixes)
Markus: bibliography, index, glossary are strikingly similar, may change later on.
Boris: is the recommended way to use CSS for styling, or inline via the rend?
Per: Index: will there be any mechanism to point to a specific page? The reference element is a natural member of the index/entry content model.
Dennis on Math types (Issue 61)
Issue 60
David Carlisle's response suggest to use plain-old ID.
Pro: copy/paste will work
Con: we get two attributes with the ID type. @markus check how this works in RelaxNG and XSD.
Boris: could we go back to using id? Markus @markus have a look at it.
Issue 61
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
Markus: a switch-like structure. Is it a part of MathML? Dennis: part of MathML.
Markus: does this switch include MathML for CSS?
@dennis find out if switch supports mathml-for-css?
@dennis what symbols are used to denote the types? point us to where switch is explained. Need to figure out relation to our content selection feature.
Issue 46
Dennis: real issue seems to be when alttext and altimg should be required.
Dennis suggest that role='math' be included, and stated that it should only be used when single number or identifier. This means that alttext and altimg can remain required.
Markus: at this point alttext and altimg are not stated to be required in ZedAI. Content selection has the content-supported feature which is optional.
Markus: would x sup 2 be allowed in simplified? Dennis: would think not. The problem is when generating alttext and altimg.
Markus: how do we enforce that people dont misuse role="math"?
@markus: add math role to vocab, add prose to MathML feature doc that explains its restricted use.
Next call
December 21st.
