ZedAI telcon 20081110
From zedwiki
Contents |
Present
Markus, Matt, Per, Stephen, Ole, Marisa, Sam, Kenny, Gregory.
Regrets: Boris.
Action Item Summarry
Completed Action Items
- @markus check with those not present today on next iteration tasks
- @Kenny to set up a concall with Markus, Kenny and Gregory Rusmeda about the possibilities for Gregory to join the group. Completion ASAP.
New Action Items
- @Markus Create a list where all the participants of this group could talk.
Action Items carried over
- @markus fix ZedAI main page, start a ZedAI Overview page
- @Markus to follow up the contact with the xhtml2 WG.
- @Kenny - Is NewsML modular? How is their schema built? Need more info on the wiki.(kenny and Gregory to post more information about NewsML g2 on the wiki)
- @Markus/Per - discuss pros/cons of the XHTML2 modularization framework (started at ZedAI W3C Modularization and XHTML2.
Minutes
Markus: Welcome Gregory.
Gregory: I am an invited expirt to the w3c. I am a member of the Protocols and Formats working group in the w3c, where I am actively working on aria web development. I am also a member of the xhtml2 working group in the w3c. I was a member of the html5 working group in the w3c too. Outside the w3c, I am a member of the Open Accessibility working group. In this group, I am the vice chair and the webmaster too. This working group is under the Linux Foundation umbrella. The latest specification of this working group is iaccessible 2. I am also very active in the expirt handlers interest group. I have read the roles document on the daisy zed next wiki. We should get the daisy specific roles into the xhtml vocab document. The vocab document is a living document. This document will stay and will be added to in the future. One of the advantages of using xhtml2 is that rdfa markup could be harnessed for our purposes.
markus: What interests you about this wg?
Gregory: I always wanted to be a part of Daisy. I also wrote substantial portions of the xhtml access module and ran it through pf. The promise of xhtml2 is out of one source deliver to a large and diverse user demographic. This ties into the work of this group as xhtml is the host language of the work of this wg. Given that accessibility is a reality for me, I am especially interested in the activities of this group. I was also a member for two years of the wai coordination group in the w3c.
Markus: Welcome stephen and Ole.
Markus: One of the major risks that we have identified is timing. Both Kenny and I have been trying to get an understanding of the timelines of xhtml2. We don't want to be in a situation where we build on top of w3c specs that are far from being Technical Recommendations.
Gregory: I Have put an agenda item to go over the timelines of xhtml 2 in the next teleconference of the xhtml 2 wg. We should have a better idea of the timeframe shortly.
Markus: A little overview for everyone: We have till March/April next year to publish a draft of this spec. Last week we finished the first iteration (iteration 0). This iteration was more of the foundational work required for the rest of the work. It included verification of xhtml2 as a host language and we also injected the daisy page break element into the xhtml2 vocabulary. We also demonstrated that it is possible to subset the xhtml2 content model without going into the xhtml2 schemas itself. In the past, We had the dtbook grammar that proved useful in some contexts and not useful in other contexts. It has become messy over the years. You can nest anything inside anything ... Our Profiles-based approach will solve this problem. Things are looking good. Several documents are available on the Daisy Zed Next wiki. In this iteration, we will come up with one concrete profile: the roles will be taken care of for this profile and also an rddl document will be created to act as a resource directory. This profile is called the Leisure profile. Pierre is the head of this work. There is another track in this iteration. This includes Kenny, Stephen and Ole. This is the periodicals profile (magazines and newspapers). Stephen has put on the wiki the description of RNIB dtds. Kenny will lead the work in this track.
stephen: These dtds are designed for our in-house magazines.
Markus: What dtd does RNIB use when you are publishing a non-RNIB magazine.
Stephen: We have not tested our dtds with a lot of non-RNIB magazines. Some of the capabilities required for newer magazines may not be available through our dtds.
Gregory: Has the analysis that this wg has undertaken thus far for Newsml been for 1.x or g2?
Kenny: The analysis was for NewsML 1.x and not for g2.
Markus: A task of this iteration is also to research if we should use modules from NewsML or create our own modules.
Gregory: 1.x is a wrapper around xhtml but g2 is more than a wrapper. I will send through links pointing to the new features in g2. g2 is the effort to modularise NewsML. g2 is much more robust and is a modularised vocabulary.
Markus: Could those modules be integrated with xhtml2?
Gregory: Yes. A part of the g2 process was to use the state of the art technology in xml and metadata from the w3c.
markus: There is a subgroup that Kenny is leading which will investigate what approach should be followed in creating a profile for periodicals. Only sample documents are to be created in this iteration though. The next iteration would take into account the actual definition of the profile.
Markus: Do you believe gregory would be beneficial to this sub group kenny?
Kenny: Affirmitive.
Markus: So there these are the two tracks. We are also hoping to introduce role as a universal construct that can be used to map to behaviours and relations to other semantic elements in other vocabularies. Borris and Marissa are the two people predominantly looking at that. One week before Christmas we will come up with concrete deliverables. A lightweight leisure profile will be created including the resource directory. This profile will be functional.
Stephen: I would like to have a look at the work of the leisure book profile sub group. We would like to understand how the work of this sub group fits in with the work that RNIB has already done.
markus: Steven, Should we be looking at the RNIB book dtd?
Stephen: Many aspects of our dtd might not be relevant to the purposes of this group.
markus: We would like to build upon the work that people have already put in and thats where RNIB's dtds will come in handy.
markus: Stephen and Ole, are you in agreement that you should spend the majority of your time on periodicals in this iteration.
Stephen: I don't specialise in periodicals but am more than happy to contribute as desired.
Ole: I am happy too.
Markus: Ole, perhaps you could become our nitf expirt?
Ole: May be!
Markus: To summarise, the activities of the two sub groups are: Periodicals sub group: sample documents are required for the periodicals profile. g2 to be investigated further. Leisure Book sub group: leisure book profile to be created including role definitions and resource directory. (covering the requirements from those organisations that cannot afford to have their people trained in complex markup. There however are no definitive answers on what a leisure book really is.)
Matt: Leisure book sits inside the text book category, but does not require high fidelity required for full-fledged text books.
Markus: It is not clear right now whether the leisure book will be a subset of the complex book profile or whether there will be a deivergence. The work on the leisure book profile in this iteration will not be a waste of time even if we don't decide to go the way of a separate leisure book profile. The work will feed into the complex book profile.
Markus: When someone gives you a book a decision will need to be made on what profile is to be used depending on the level of semantic information required in the profile.
Per: I believe this will be a good exercise. A leisure profile will give us just such an experience.
Matt: In terms of building the content model, starting with a smaller scope as the leisure profile could be very beneficial.
markus: I will send Mrissa and Borris an email on my thoughts on rdf and role.
Markus: Gregory, I will add you to the email list and introduce you to george.
