ZedAI Iteration3 Report

From zedwiki

Jump to: navigation, search

Contents

Summary

This is the report from ZedAI WG Iteration 3.

The iteration time span was 18 April 2008 - 26 May 2009. Iteration deliverables were defined in the Iteration 2 report.


Deliverables Report

The main deliverable of this iteration was a a first public working draft of the Z39.86 Authoring and Interchange Framework. This has been completed, and is available at http://www.daisy.org/z3986/2010/

The published version of the specification, profiles, features and framework is of an early access nature, and contains several incomplete areas, and several yet unresolved issues. The WG tracks all lower level issues at the GoogleCode issue tracker. The following additional items should be taken notice of regarding the first public working draft:

Periodicals profile not yet delivered
A profile for Periodicals (newspapers, magazines) was planned to be provided in a first version in iteration 3, but this has been postponed to Iteration 4.
Non-functional prototype of the Content Selection feature
Published as version 0.0, the Content Selection feature is not yet usable, but provided anyway as a placeholder, and as a way to seek input from the community on how to complete it.
XHTML2 Fallback plan
See Risk analysis below

Sample Documents

The Google Code repository hosts a collection of sample documents referencing the profiles-in-development. These sample are like their profiles under development, and no guarantees are made that they are fully valid to the conformance requirements as dictated by the specification.

Risk analysis

As noted in the previous iteration risk analysis, the future and timeline of XHTML2 and XHTML Modularization 2.0 remains uncertain. For this reason, the current version of the schemas use a "chameleon" approach: core elements and modules are in the Z39.86-2010 namespace, but can be switched back to XHTML2 compliance at any time.

Resolved Items from Iteration 2 Issue Log

Inclusion model for MODS (document-level)
The current inclusion model is to use MODS XML. The use of RDFa was investigated, but was found unfitting. The WG may return to this issue in a later iteration.
MODS inline using RDF/a
Since MODS is not RDF/a compatible at this time, the answer is no. This may change in a later iteration.
Autogeneration of XSD
Autogeneration of XSD now works, with the exception of the MathML feature. The W3C MathML WG will eventually produce an XSD of MathML3, so this is a temporary problem. Currently, a placeholder "dummy" XSD MathML schema is provided as an interim solution.
RDDL or XHTML+RDF/a
RDDL has now been abandoned in favor of a Resource Directory Vocabulary defined in RDFa. This vocabulary will be extended considerably in coming iterations.

Iteration 3 Issue Log (to be solved in iteration 4)

The WG henceforth tracks all issues at the GoogleCode issue tracker.

Deliverables for the next iteration

Iteration 4 time span: 29 May 2009 - 23 September 2009

Main deliverable: a second public working draft of the Z39.86 Authoring and Interchange Framework

Overarching

Core Document Model in schema
Define the Core document model using normative schema, and revise the corresponding spec section accordingly.
Further work on spec and primer documents
The spec and primer documents are taken to second public draft stage. At the end of iteration 4, they will still not be complete.
Tracker issues
Solve as many as possible of the lower level GoogleCode issue tracker issues, with prio level medium and high.
Extensions to Resource Directory Vocabulary
The RD vocab should be extended to be able to express
  • the target for normative prose: documents constraints, processing agents behavioral constraints
  • the equivalent of RDDL natures.
  • transformation relationships (to and from the profile or feature being described).
Schema documentation - further documentation of elements and attributes
Much documentation of elements and attributes remain.
Schema documentation - inline examples
Add the ability to provide small markup examples to the Schema Documentation
Second go at defining features
Fix remaining issues re feature "exposed elements" etc, as per TODOs in spec
Schematron, NVDL
Introduce the schematron tests formally, introduce NVDL where necessary

Profiles and features, new versions

Periodicals profile, first draft (target version 0.1)
A first draft of a periodicals profile (superset of newsfeeds profile) is created.
Book profile, fourth draft (target version 0.4)
A fourth draft is produced, based on input from testing
Newsfeeds profile, third draft (target version 0.3)
A third draft is produced, based on input from testing
Generic Document profile, third draft (target version 0.3)
A third draft is produced, based on input from testing
Sample production for Book, Newsfeeds, Periodicals and Generic Document Profiles
More public domain samples are produced.
Interactivity feature, second draft (target version 0.2)
A second draft of the interactivity feature is provided, based on input from testing.
Math feature, second draft (target version 0.2)
A second draft of the Math feature is provided, based on input from testing.
SSML feature, second draft (target version 0.2)
A second draft of the SSML feature is provided, based on input from testing.
Ruby feature, fourth draft (target version 0.4)
A fourth draft of the Ruby feature is provided, based on input from testing.
Content Selection feature, first draft (target version 0.1)
A first draft of the Content Selection feature (which was provided in an uncomplete version 0.0 in the previous iteration) is provided
Source Rendition feature, third draft (target version 0.3)
A fourth draft of the Source Rendition feature is provided, based on input from testing.

If time allows

RDF ontology for elements in our namespace
Investigate the utility of an RDF ontology that describes inheritance relationships of our element and attribute pool. This could be used in schema documentation, as well as referenced from Resource Directories for processing agents to discover fallbacks at the element level.
Profile Composition Guidelines
A first draft of an informative profile composition guidelines document is produced
Early drafts of poetry and drama modules
Research on computer code markup feature (possibly based on DocBook5)
Personal tools