From zedwiki

Note: this meeting will be held at 2100h UTC. Find the meeting time in your geographical location.

Contents 1 Present 2 Regrets 3 IRC Channel 4 Previous Telcon 5 Action Items 5.1 New 5.2 Brought Along 5.2.1 Braille-centric 5.2.2 MathML-centric 5.2.3 Other 6 Agenda/Minutes 6.1 Action Item review/update 6.2 Abstract Definitions prose progress report (short) 6.3 SchemaDoc 2.0 6.4 This weeks Braille issues 6.4.1 Num element, status update 6.4.2 Proper Names 6.4.3 T-V distinctions 6.4.4 Continuation Issues 6.5 Next call

Present

Markus (scribe), James, Christian, Per, Matt, Josh, Boris

Regrets

IRC Channel

IRC Address: irc.a11y.org

Channel: #zedai

Previous Telcon

ZedAI_telcon_20100301

Action Items

New

• Matt add documentation to num module and numeral section in core.n3; longdesc as well (should stress clearly; not used for mathematics)
• Markus add issue num vs mathml to tracker [DONE, see http://code.google.com/p/zednext/issues/detail?id=133]
• Markus add person-name property to core vocab, populate the name element with this, close issue. [DONE]
• Markus add v-form t-form properties to vocab
• Christian check whether always single words or also groups of words (for v-form and t-form).[DONE, see http://code.google.com/p/zednext/issues/detail?id=116#c3]
• Christian start wiki page that discusses and gives examples of the continuation IDREF attribute in the context of 132, 124, 115.

Brought Along

Braille-centric

• 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.
• markus: on meta+properties for braille/formatting annotations: summarize to list
• markus: check with Joel re homonyms in BiD

MathML-centric

• markus: implement MathML changes that we've agreed on so far, and add an issue for the list of the encoding attribute.
• 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
• ChristianE, remind ChristianW to send suggestion about Mathml vs num distinction.

Other

• markus make sure we have an issue in the tracker to populate vocab with properties for names
• Matt: change the semantics of code to be more generic (not only computer programming, also covering things like morse).
• matt: review inline markup in bibliography, glossary, index {ONGOING}
• 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/Markus - ask ViewPlus et al about the SVG namespace-inject issue [ONGOING @markus]

Agenda/Minutes

Action Item review/update

See #Brought_Along above.

Abstract Definitions prose progress report (short)

Authoring ongoing at ZedAI_ADM, will be ported to docbook once done.

SchemaDoc 2.0

Status, review comments from group?

Boris:

 A few comments on the schemadoc - I agree that in general it looks great!

 Looking at "The Block variant of the object element" page, for example:

 Content model has, in this order:
 - a list of optional attributes 
 - a list of optional RDFa attributes 
 - a single required attribute
 - a single optional attribute (@srctype)

 I second Markus's suggestion to have a "required attributes" label parallel to the "optional attributes" labels.  Currently the required attributes seem too easily overlooked.

 I am puzzled why  @srctype is listed by itself rather than with the other optional attributes.

 Below, in the long description, <orderedlist> element being passed through to HTML, causing invalid HTML and odd display.

Markus: @srctype is because its co-dependent. There are several such cases, co-occurrence constraints attribute-attribute(s), or attribute-element(s.)

This weeks Braille issues

Num element, status update

Wiki page: ZedAI_Numeral_Element

Issues: 118, 119, 120

Num module and initial set of properties added : r629. Documentation and MathML disambiguation remain.

Documentation tasks include:

• documentation of module
• documentation of core vocab properties (in core.n3)
• a longdesc that gives examples of use with properties (isbn, phone, ordinal, etc)

@ Matt add documentation to num module and numeral section in core.n3; longdesc as well (should stress clearly; not used for mathematics)

@ markus add issue num vs mathml to tracker

Proper Names

Wiki page: ZedAI_Proper_Name_Proposal

Issue: 121

@markus add person-name property to core vocab, populate the name element with this, close issue.

T-V distinctions

Wiki page: ZedAI_T–V_distinctions_Proposal

Issue: 116

@markus add v-form t-form properties to vocab

@Christian check whether always single words or also groups of words.

Continuation Issues

We probably wont have the time to solve this one on the call, but as a starter:

The below issues are related in that they in one way or another relate to the notion of connecting non-contiguous content chunks or points with each other.

These issues should be solved using a uniform mechanism.

• 115: inlines that cross section boundaries

• 124: paragraph continuations

• 132: articles: page continuation

Markus: Re 124, if the "dtbook culture" solution, which is to embed inside the p should be used, then we need to extend the current paragraph content model to allow more block elements. Problem becomes, where do you draw the line?

Matt: would equally apply to a list item

Markus: splitting with explicit continuator might be "cleaner", but question becomes what people are willing to live with

Boris: would it solve a few of these problems to have a "continues" IDREF attribute? Rather just saying "continuation" with a class

Christian: continuationOf would also solve 115

@Christian start wiki page that discusses and gives examples of the continuation IDREF attribute in the context of 132, 124, 115.

Next call

Note: daylight savings time kicks in next weekend here in North America pushing the time up to 5:00PM.

 Most of the US will be moving its clocks forward on Sunday March 14 2010.  
 This is two weeks earlier than Europe.
 Most European clocks will move 1 hour relative to UTC on Sunday March 28  
 2010.

 Between March 14 and March 28, the time difference between US and Europe  
 will be 1 hour less than it currently is.

Suggestions for new times (even beyond the 14-28 period):

• mondays 14:00 UTC
• mondays 15:00 UTC
• mondays 20:00 UTC

Starting with next mondays call we are doing 13:00 UTC