ZedAI telcon 20090831

From zedwiki

Jump to: navigation, search

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


Contents

Present

Markus (scribe),

Regrets

Kenny, Marisa

Previous Telcon

ZedAI_telcon_20090817

Action Items

New

Brought Along

  • Markus and Ole: produce sample periodicals docs as in ZedAI_periodicals_telcon_20090819
  • Boris: define how to use RDFa to associate an annotation with an annotator (now that rdfa:about is no longer used) - perhaps just use @role? {See below}
  • Markus: describe our use of xlink:simpletype as an implicit default a la docbook5
  • Markus: update samples to define the z3986 CURIE prefix
  • James: make sure the spec no longer claims to reserve the z3986-profile and feature values; instead define above rdfa solution
  • James/Markus: samples and primer etc changes in the spec, relating to linking proposal and link rel="z3986-profile" etc
  • Markus: define the property to use on reference for issue 57 (reference role="object"?)
  • Markus: close all issues that are fixed by linking proposal
  • Boris: add issue to tracker re inversing pointing relationship between expansion and abbr
  • Per/Markus: have Content Selection draft available for review by next concall {DELAYED}
  • Dennis: solve Issue 60
  • Dennis: solve Issue 61
  • Josh: solve Issue 50
  • Josh: solve Issue 53
  • 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

Postponed beyond this iteration

  • Matt (hopefully) propose whether we need specialized content models for bibliographies and indices (as opposed to section @role="bibliography")
  • Markus ask rdf/a task force for alternatives to CURIE syntax / research best way to compose our own Role module
  • Dennis: solve Issue 46
  • Markus: deal with term@termdef to be in harmony with @for (see http://code.google.com/p/zednext/issues/detail?id=42)
  • Markus propose a runninghead element for use in conjunction with section/h

Agenda/Minutes

(Reminder: see ZedAI_telcon_20090803#Priorities_for_this_release)


Major remaining items this iteration

Content Selection Feature

Per - status?

Per: we have started extending the RD, nearing a 0.1 alpha.

Per: we are aiming to have the feature be implemented in XSLT 2.0.

Current function sets currently:

  • TARGET specifies target for content (consumer groups and concrete formats) (remember @showin?)
  • FEATURE SUPPORT: function as a fallback for unsupported features
  • PARAMETER TEST: test document variable against transformation runtime parameter

@per and markus: thursday

(Nearest target: get a 0.1 alpha out to this group for review).


XForms Feature

I've corrected issue #53 (http://code.google.com/p/zednext/issues/detail?id=53) 
and committed the changes.  I'm pretty sure I've done it correctly (changed the 
define of xforms.UI.Inline.class to zero or more z3986.Text.class), but you may 
want to doublecheck it.

As an additional note, after thinking more about it, I don't think we should expand 
the contents of <xforms:label> to include specific elements, such as paragraphs and 
lists.  While it would be handy in a few situations (namely the tax form example in 
the genericdocument tests), it seems as though it goes past the original intent of xforms.  
I'm more than happy to debate it, particularly as it's more of a gut feeling than any 
reasoned argument at this point.

@markus check out that Issue 53 commit is correct

MathML Feature

Dennis: status of Issue 60?

Dennis: status of Issue 61?


Josh: MathML has a new release coming out next week, partially waiting on that.

Periodicals Profile

See latest subwg notes at ZedAI_periodicals_telcon_20090819; discussion around what the most appropriate evolution strategy of this profile would be. Decision to start anew (Markus and Ole) with sample markup documents.

Note - NLM Journal Archiving and Interchange Tag Suite is now on NISO standard track. We need to investigate the nature of this grammar, and what the possibilities for co-op are. (George has had a first call with them.)

Markus: from now on do periodicals on this call. @Markus: research NLM further

Linking Proposal

Issue 68

Some other issues with the linking proposal still in action item list, but here is one we may be able to close: Issue 68.

Decision: @Markus revert to support Boris's suggestion.

Boris on annotation@role

I think using @role is the right thing to do; we certainly don't want to keep using @rel, 
since without the @about, @rel would be actively misleading RDFa-aware processors.
As a concrete example, with the linking change and the @role atrribute, annotations would look like this: 
<p id="a">Paragraph of original text;&lt/p>
<annotation for="#a" role="d:editorAnno">Note from editor about that paragraph</annotation> 
Note that we may be putting a lot onto @role, since we had also already identified a list of roles 
for annotations that describe the function of the annotation; see http://www.digitaltalkingbook.com/zw/Request_A_Role which 
lists the following roles:  structure description, content description, introductory note, commentary, clarification, 
correction, and (tentatively)  attribution.
We would be adding the source of the annotation to this as well, possibly resulting in multi-valued roles like this:
role="d:editorAnno d:correction"
or for a "prodnote" description of a table's structure:
role="d:republisherAnno d:structureDescription"

Decision: @Markus make sure this approach is implemented.

Spec

James/Markus - status?

  • Exposed Elements in Feature
  • Core Markup Model
  • Changing the way profiles are declared (properties instead of reserved words): let rest for a while more.

@James: send call suggestions to Markus for Spec work date.

New Target date for this iteration release

It makes no sense to Markus to release before we have a first draft of the Periodicals Profile (in other words; having a release which is profile and feature complete although some of these are still in early versions). Agree/Disagree?:

Target release date: 22nd September

Personal tools