ZedAI telcon 20081208

From zedwiki

Jump to: navigation, search

Note: The 8 December 2008 meeting will be held ONE HOUR LATER than usual, beginning at 1400h UTC. Find the meeting time in your geographical location.


Contents

Scribe

James

Present

Gregory, James, Marisa, Kenny, Markus, Matt, Stephen, Per

Regrets: Ole

Action Items

Completed

  • MG investigate using NVDL to reference NewsML XSD fragment
  • MdM remove cardinality and datatype stuff from taxonomy draft
  • all read and comment on pers email on frontmatter
  • MG Iteration report discussion of fallback if XHTML2 gets delayed. Accept delay as a solution?
  • Per: continue frontmatter content model discussion on list (ref: RNIB Book DTD)

Still pending

  • GJR send email on XHTML1.x as possible fallback strategy
  • Markus fix ZedAI main page, start a ZedAI Overview page (postponed, Markus is working on spec prose first.)

New

  • Gregory to research mechanisms for local extension of taxonomies
  • Per & Markus to express book profile as schema
  • Boris and Marisa need to add book structures from Chicago Manual of Style and RNIB into taxonomy to support @role
  • Markus needs to add a link on the Wiki to the RNIB DTD information
  • James to begin research on XInclude and/or other strategies for splitting document over multiple files

Agenda/Minutes

There are two weeks left of this iteration.

Simple Book Profile

Frontmatter, current proposal summary [JP, PS]

  • Markus: Large number of elements would be daunting; can use use section/@role instead. But other elements have specialized content, so maybe use elements there
  • Advantage of using section/@role:
    • Extensible at profile level, organization level
      • Gregory to research mechanisms for local extension of taxonomies
    • Helps keep grammar simple
  • Suggested content model:
    • Zero or more section (x:h optional) with @role (for dedication, preface, etc.)
    • d:titlepage
    • d:copyrightpage
    • zero or more d:toc (for table of contents, figures, etc.)
  • Per & Markus can now express this as schema
  • Boris and Marisa need to add book structures from Chicago Manual of Style and RNIB into taxonomy to support @role
    • Markus needs to add a link on the Wiki to the RNIB DTD information

d:cover

  • Decision to add d:cover, element for book cover information
    • Top-level child of book, before frontmatter
    • Use pagebreak to distinguish inside/outside covers

Other items

  • Name for d:bridgehead will be d:bridgehead (for now)
  • @cite being worked on in the XHTML2 WG (Gregory has forwarded information to list)
  • When we have a frontmatter model in place, what remains to do for this iteration in the simplebook profile?
    • Need to be sure we have good distinctions between inline and block contexts/elements in schema
    • Need to support documents split among multiple files; not for this iteration, but need to work soon
      • James to begin research on XInclude and/or other strategies for doing this

Periodicals subWG

Periodicals subwg, status update

  • Four approaches to include NewsML constructs considered:
    • Create our own elements based on NewsML -- good if used for other kinds of content
    • Use @property or @role to map to NewsML -- consistent with use in book profile front matter
    • Use elements directly from NewsML -- good if only used for newspapers
    • Use DC vocabulary -- dropped; inappropriate here
  • Using distinct elements vs. attribute decorations: impact on authoring tools needs to be considered
  • Kenny: Needs to produce sample instance documents

Role/RDF subWG

Scope

Discussion in group on how to keep from becoming too complex (a danger with RDF). Suggestion to limit the use (for this iteration at least) of RDF Taxonomies to:

  • Static associations between QNames and OWL Classes
    • A solution to problem of repeating @role value
    • Use same OWL class as for CURIE name, tagged with QName (or QName mapped to OWL class?)
  • Dynamic associations: OWL Classes to CURIE names (eg classic @role usage)
    • Processing systems can hard-code CURIEs; don't need to resolve
    • Definitely want to do this

Out of scope for this iteration:

  • Behavioral descriptions; not for this iteration, but keep in mind for distribution
  • Fallbacks; nothing explicit in this iteration, although two items above can imply fallback; keep in mind for distribution

Spec prose for iteration deliverable

Short update from Markus, who is putting together a spec skeleton

  • Markus working locally; will post on SVN this week
  • Markus suggests using docbook to author spec

F2F?

Discussion on the possibility of holding an F2F in the spring.

  • Tentative decision: Towards end of last iteration (end-March?)
  • Coordinate with CSUN
  • Ideal place would be Princeton (James, Marisa and Gregory in the vicinity)
Personal tools