ZedAI telcon 20100301
From zedwiki
Note: this meeting will be held at 2100h UTC. Find the meeting time in your geographical location.
Contents |
Present
Markus (scribe), Dennis, Josh, ChristianE, Boris, Matt, Per, Sam and James
Regrets
Kenny
IRC Channel
IRC Address: irc.a11y.org
Channel: #zedai
Previous Telcon
Action Items
New
- markus: implement MathML changes that we've agreed on so far, and add an issue for the list of the encoding attribute.
- ChristianE, remind ChristianW to send suggestion about Mathml vs num distinction.
- Matt: change the semantics of code to be more generic (not only computer programming, also covering things like morse).
- Matt: push num properties to vocab. Markus: tell Matt how to do rng enum contributions in n3.
Brought Along
Braille-centric
- ChristianE :
review proposed solutions to 110 and 111 in the issue tracker.[DONE: Both proposed solutions are fine and solve our use cases] -
Markus assign owners to Braille issues in tracker.[DONE] - ChristianW: come up with a proposal for a clear definition of scope distribution between MathML and <num>; use emailing list so Dennis et al can react.
- Matt: update the num element wiki page with a proposal for a new set of "pragmatic" properties for role on num
-
ChristianW get a Google account, give Markus google account address (adding CW as project member).{DONE} - markus: on meta+properties for braille/formatting annotations: summarize to list
- markus: check with Joel re homonyms in BiD
MathML-centric
- Dennis: suggest reasonable set of "ZedAI recognized" values for @encoding on mathml:annotation-xml. Note that other values beyond these would be allowed from a document validity perspective, but tools would not be required to support anything beyond the given set. (Note that the list could be empty, ie tools are compliant without supporting any value). Note also that values for mathml:annotation are also possibly of interest
- Dennis: is there a predefined value for mathml-in-css to use in @encoding?
- Dennis: determine whether we should allow Strict Content, Pragmatic Content, or both inside annotation-xml.
Other
- markus make sure we have an issue in the tracker to populate vocab with properties for names
- matt: review inline markup in bibliography, glossary, index {ONGOING}
- kenny: send summary of use case for continuation indicator to list.
- markus add issue to tracker: may be necessary with publisher address in inline reqd metadata.
- markus check how math/@id and else/@xml:id works in RelaxNG and XSD.
- markus investigate pros/cons of going back to using id?
- 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)
Agenda/Minutes
SchemaDoc 2.0 now live
Question to Per: anything you want reviewers to focus on?
Per: not very different from earlier versions, cleaned up, less of those long lists etc.
Still not complete, lost of space for improvements. What is needed now is actually for people to have a look at it.
Per: please check three things:
- check that the schemadoc actually presents "the truth" in relation to the schema
- Markus: schemadoc will formally be informative
- changed the content model presentation of elements, is it better or worse than the previous?
- the attributes presentation is no longer a list, now part of the elements content model. Is this better or worse than previous version?
Per: I will continue working on this for a while more.
Action Item review/update
See #Brought_Along above.
MathML action items
Dennis: no there is no predefined value for @encoding re mathml-for-css. MathML 2/3 has only three predefined values: x, y, z.
Dennis: probably a good time to bring this up with the MathML WG (mathml-for-css).
Dennis: we should allow both Strict Content and Pragmatic Content in annotation-xml. Remember that Strict is exactly the same as OpenMath. Pragmatic is a superset of OpenMath.
Dennis: values for encoding attribute: the ones that MathML3 specifies: mathml, mathml-content, mathml-presentation (from MathML2).
Markus: could presentation MathML be used as a fallback for presentation MathML? Dennis: Yes, using the semantic element.
Dennis: we should come up with values for @encoding regarding Braille representations. Maybe a good place to begin is some kind of naming scheme using accepted abbreviations.
Dennis: note that the actual alternative content is actually permitted to be external to the document.
Christian: so this is not about different Braille representations of the MathML? Dennis: you could have several encodings simultaneously.
@markus: implement MathML changes that we've agreed on so far, and add an issue for the list of the encoding attribute.
Num element
@ChristianE, remind ChristianW to send suggestion about Mathml vs num distinction.
Matt has added a new set of properties to the wiki page.
Markus: next steps?
Matt: we may need to go further; a possible route here is to have multiple elements instead. Or there may be logical groupings.
Matt: regarding alpha and morse code, perhaps we should move these to the code element instead. Markus: sounds like a good idea.
@Matt: change the semantics of code to be more generic (not only computer programming, also covering things like morse).
@Matt: push num properties to vocab. Markus tell Matt how to do this in n3.
Next call
Monday 8th.
