ZedAI telcon 20090427

From zedwiki

Jump to: navigation, search

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

Contents

Scribe

Markus

Present

James, Per, Markus, Marisa, Sam, Josh, Boris, Kenny, Matt, Ole

Regrets

New action items

@James and Markus; come up with a plan for dealing with the limbo in spec prose -- possibly a switch in the spec with two alternate versions

@Dennis/Josh add the 2 examples that Boris mentioned (20090427 concall) to Wiki.

@Boris send image(s) for the examples mentioned to Dennis and Josh.

@Dennis/Josh contact QTI and ask about replacing the HTML with host language text content set.


Previous Action Items

  • Markus to send list of RelaxNG-compatible tools to e-mail list [done]
  • Everyone to read through XForms/QTI document for next call
  • 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
  • Markus to invite people for profile testing
  • Markus to ask the DAISY list about how newspapers/periodicals markup is currently being done.

Agenda

  • Todays main agenda item: XForms/QTI and the forms feature.
    • Proposed target: get an alpha feature written and included in schema asap, then start testing markup scenarios on real-world input.
    • Note: each feature has its own documentation (in resource directory).
  • AOB

Minutes

Short update on W3C and fallback plan

  • Fallback plan
    • discussions with W3C
    • final decisions in W3C space may not be taken until end of year.
    • ZedNext trunk; a new set of schemas being built using chameleon approach
    • allows us to move ahead with full speed while postponing final decision on namespaces to use
    • remaining faithful to core XHTML2 models
    • (new schema version also translates well to XSD!)


@James and Markus; come up with a plan for dealing with the limbo in spec prose -- possibly a switch in the spec with two alternate versions

XForms/QTI and the forms feature

Markus: lets try to have rapid iterations for the Forms spec

Dennis: suggest: first decide which direction we want to go in terms of XForms/QTI

Josh: XForms is similar to original forms, main difference is the model,

Dennis: compared to QTI, UI elements in XForms are independent of the text markup around it.

Josh: QTI designed for testing environment. Each QTI element is a discrete question and answer combination. Leads to integration problems; [line breaks off]

Markus: remember what we need here in AI context is a strong and strict declarative expression model. It can get transformed to another format at distribution time.

James: example 2 is very clear of questions, and how they are done in both. Looks like in XForms, these questions, the text would be the general markup model, and really just the form part in the XForms namespace, whereas with QTI we loose all of our text markup. This is one strong argument for XForms.

James: another reason for XForms is that it is quite strongly coupled to XHTML2; there *may* be benefits here.

QTI: designed to be a thing in and of itself. Not designed for incorporation into various hosts.

James: must the model live in the head? Imagine a 1000 page book with questions scattered.

Josh/Dennis: model can be thin, doesnt have much to do with authoring. See the model as a template for the submission. James: could be used to define space, datatypes.

Josh: stuff like this can be provided in the body as well.

Marisa: should be able to keep the model in a separate file. We looked at this during SMIL3 state work.

Boris: common argument that XForms is easier to work with, but QTI handles interaction like multichoice questions, and mark up which is the correct answer. Another example is to match items in column a to corresponding items in column b. Impression that QTI is more declarative, whereas XForms is more presentational.

Dennis: Yes, QTI is designed for tests.

@Dennis/Josh add the 2 examples that Boris mentioned to Wiki.

@Boris send image(s) for the examples mentioned to Dennis and Josh.

@Dennis/Josh contact QTI and ask about replacing the HTML with host language text elements.

James: just because something is posed as a questions, does it need to be marked as interactive? Thats the other variable.

Fallback: we can presume a generic content selection feature to provide a switch-like mechanism.

Retrieved from "http://www.daisy.org/zw/ZedAI_telcon_20090427"
Personal tools