ZedAI telcon 20090223
From zedwiki
Note: The 23 February 2009 meeting will be held at 1400h UTC. Find the meeting time in your geographical location.
Contents |
Scribe
Marisa
Present
Markus, James, Marisa, Leona, Sam, Boris, Per, Dennis, Josh, Kate, Matt, Kenny
Regrets
Stephen
Completed Action Items
- Marisa: find Dicks and Jacks presentation on SMIL+XForms
- Warning, PDF link: http://homepages.cwi.nl/~jack/presentations/smilstate-for-rwab.pdf
- Markus to contact Oxygen for possible free licenses.
- We have 5 licenses; contact Markus off list
- Kenny to post information about the leads to the list.
New Action Items
- @Markus: collect all open issues in the SVN issue tracker; the list will review each one
- @Kenny, Marisa: Go through CMOS list and compare against Journals page
- @Markus make conference room arrangements
Previous Action Items
- Dennis: produce XForms+XHTML2 workbook examples, put on Wiki
- XHTML2 WG going to integrate XFORMS 1.1 at the schema level
- Dennis to post information about QTI to the list.
- Dennis preparing wiki pages with workbook examples and QTI information.
- Stephen to assist in documenting the elements in the Zed AI profile suite.
- Markus fix ZedAI main page, start a ZedAI Overview page (postponed, Markus is working on spec prose first.)
- Sam - gathering sample documents.
- Kenny - gathering sample documents.
- Markus to invite people for profile testing.
- Markus to ask the DAISY list about how newspapers/periodicals markup is currently being done.
- Gregory to research mechanisms for local extension of taxonomies
Agenda
Iteration Deadline
Reality check on:
- iteration deadline
- Markus proposes to delay this iteration (current deadline is end Feb) to give us more time to finish the Periodicals profile and to have a good XHTML schema to refer to.
- This iteration will include:
- First draft of Periodicals and Advanced Book Profiles
- Second draft of Simple Book Profiles
- First draft of specification documents
- New due date: March 13
- date for first feature complete internal draft
- There will be an Iteration 2 for finalizing internal drafts. Probably end April/early May.
First public draft due date: end of October.
George and Markus to have a call with NISO to discuss the timeline.
Metadata status update
- Background: ZedAI_Meta_Data_-_AI_Working_Draft and ZedAI_Meta_Data_-_Status_Report
Discussion
Matt: use Mod standard for bibliographic metadata; in contact with mods group. Mod standard due in the summertime. Do we wait and write our own version in RDF in the meantime, or help out on their committee (and with what resources)? The group will need to make decisions about what to do with metadata that falls outside the standard bibliographic metadata (e.g. section numbers). Our profiles can reference several existing RDF schemas for their metadata. MODS (bibliographic) will be global to all profiles. We will need something additional for production information.
XInclude report review, continued (add CDR)
Continuation from last weeks discussion: ZedAI_telcon_20090216#XInclude and XInclude_Analysis
- XInclude covers the collective editing use case (and should therefore be allowed in the standard), but it does not help with the size/performance problems.
- Alternative solutions:
- use the epub approach (for distribution): mandate several valid complete documents. For authoring, ignore the problem.
- drawbacks: the content doc is not longer a tree (and is that a problem? It was with DTBook, but must not be in ZedDist)
- invent our own fragment inclusion mechanism with the option of not loading all parts by default
- drawbacks: is a very low level interception on our part, and will never work with off-the-shelf processors. Further, ZedSpec implementors would have to do a lot of low level work just to get hold of the entire document instance. Cost may be higher than benefit.
- new: Use the W3C CDR approach for application-level controllable segmentation
- Stephen: XML TWIG seems to be addressing this problem.
- use the epub approach (for distribution): mandate several valid complete documents. For authoring, ignore the problem.
Discussion
- XInclude can be completely on or completely off.
- It is not helpful if using DOM; other APIs are ok.
- It can still be helpful for the authoring process.
- What alternatives?
- EPUB restriction: each book can be only 300k.
- Compound document by reference (use mime type to discover xml fragments)
James says the problem is how to split up a single entity into manageable chunks and still have it represented as a single entity. This is a mountain of distribution format work that we shouldn't have to tackle now. This is also a universal problem. No one has solved it yet.
Boris says that the advantage of XInclude is that it will be supported in off-the-shelf XML applications.
James found Java and .NET libraries that support it.
Endorsing XInclude: incorporate xml base and decide how much to talk about it in the spec.
Profiles Status: book profiles
- AdvancedBook now has TOC sections, section TOCs, box[@role] and annotations
Remaining issues:
- annotations, what of them (see list discussion)
- open issues in frontmatter
- poem and drama modules?
- metadata
- ... and issues at the svn tracker: http://code.google.com/p/zednext/issues/list
Profiles Status: periodicals
Discussion
Kenny: CMOS has lots of information about Journals. Decided against including Journals in the Periodicals profile and restricting . A Journals profile can happen after the spec is done. It will be a superset of the Periodicals profile. There is a wiki page with all the concepts for newspapers and magazines. Another wiki page lists the CMOS concepts for journals.
Oxygen
- The good folks at Oxygen XML have granted us some free licenses. Markus will distribute.
- Leonas issues: resolved?
LAX F2F March 2009
Physical attendants, notify Markus asap
Authoring_&_Interchange_Working_Group#LAX_F2F_March_2009
Attending so far: Kenny, Marisa, Sam, Markus, Dennis
