From zedwiki

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

Contents 1 Present 2 Regrets 3 Previous Telcon 4 Action Items 4.1 New 4.2 Brought Along 5 Agenda/Minutes 5.1 Impact of XHTML2 WG Cancellation 5.2 Revisit last weeks discussion on running headers and braille feature 5.3 Item-of-the-week: object (#57) 5.4 Item-of-the-coming-week 5.5 Periodicals profile: status update 5.6 AOB

Present

Markus (scribe), James, Matt, Boris, Marisa, Per, Ole

Regrets

Josh, Dennis, Kenny

Previous Telcon

ZedAI_telcon_20090629

Action Items

New

• Markus ask rdf/a task force for alternatives to CURIE syntax
• Markus propose a runninghead element for use in conjunction with section/h
• Markus: add reference/xlink/about to schemas, and raise all issues that arise on list
• Boris: help dissect XLink spec for good subset scope, and raise any issues re XLink 1.0 vs 1.1 (can we express additional constraints in ZedAI spec prose to "emulate" 1.1?)

Brought Along

• Marisa bring Boris's annotation role property suggestions to Request_A_Role
• Markus startup the Braille formatting feature on the SVN. On the feature team: Ole, a slice of Matt, someone from TPB, perhaps VA also.
• Markus contact TPB for participation in the braille feature work
• Kenny check with VA re participation in the braille feature work
• markus add all math issues clearly to tracker
• Dennis/Josh contact QTI and ask about replacing the HTML with host language text content set.
• Markus to add spec prose on cascading level for inline styles: "For the purposes of the CSS cascade, these values are considered author-level"
• Markus to create wiki page devoted to level issue

Agenda/Minutes

Impact of XHTML2 WG Cancellation

Needs replacement:

• Role attribute module

Markus: choice to simply define our own attribute named "role"

• CURIEs

There are other syntaxes to use within RDF space. @markus ask rdf/a task force for alternatives

We dont know where to go in terms of the SMIL3 DAISY Profile; Marisa and Daniel are looking into it.

James: in creating our own role attribute; the most important thing is that has a formalized way for extensibility.

James: could we adopt CURIEs into our standard?

Markus: possibly. But need to research alternatives as well.

Needs amendment:

• all RNG modules where we previously were planning to inherit functionality definitions/semantics. Another option is to point to XHTML11 in some cases (eg object).

Revisit last weeks discussion on running headers and braille feature

• whats the relation to the already existing source rendition feature ([1])?
• whats the relation to the more general theme of paginated media? Could the feature be generalized to target this level instead?
• seeking input from more organisations
• seeking approach to running header markup

Boris: how far would it get us if we added some sort of abbreviated title element?

Matt: yes, some way of specifying an abbreviated title, doesnt really matter if it an element or not.

Ole: I agree, some place to put an abbreviation, or an annotation. The main issue is how you handle the human-authored string.

Markus: do we have enough matter for an entire braille feature?

Ole: most other issues are handled by ToC etc.

Matt: running headers, and context breaks.

Ole: one other thing we should have is the equivalent of dtbook:showin.

Markus: yes, thats the content selection feature.

Markus: suggest cancelling braille feature, all agree

Solution for running headers

Ole: needs to be an element, so we can have markup.

Boris: must be easily distinguished so that it can be ignored.

Boris: will there ever be a case where a running head will change within a section (eg should it be allowed anywhere?)

Ole: ours never do.

Matt: could be useful to have it as an element that could appear whereever its needed, but its ugly.

@Markus propose a runninghead element for use in conjunction with section/h

Item-of-the-week: object (#57)

See also ZedAI_Linking_Proposal

Boris: would we allow everything thats in the XLink spec? Or just allow a subset (such as Simple Links)?

Markus: I dont see a problem in subsetting.

@Boris comment on the subsetting, and other problems.

All in favor of implementing this as a beta in schemas.

@Markus: add reference/xlink/about to schemas, and raise all issues that arise on list

Item-of-the-coming-week

Focus on consequences of reference, xlink, and @for

Periodicals profile: status update

Sample documents are being worked on, still.

AOB