ZedAI telcon 20091019
From zedwiki
Note: this meeting will be held at 2100h UTC. Find the meeting time in your geographical location.
Contents |
Present
Markus (scribe), Sam, Per, Kenny, Boris, Matt
Regrets
James, Josh, Dennis
Previous Telcon
Notes
- Tuesday 13:00 UTC: con about lists
- Friday 13:00 UTC: con about SVG
Action Items
New
- Boris - ask ViewPlus et al about the namespace-inject issue
- Kenny - ask Ole if he is ok with putting periodicals to rest
- Kenny - own the page continuator issue
Brought Along
- Markus Matt, James, to create a wiki formulating an out-of-line metadata proposal, based on todays discussion. Then circulate to interested parties (IFLA group, WIPO, board, etc)
- Markus implement role module
- Markus set up initial concall with Matt, for list revisit work
- Markus to feed in information from ViewPlus re integration of SVG [DONE]
- Boris: help deal with svg integration, help with object documentation and samples, address issue 9
- Kenny/Ole: inform whether the periodicals profile should be targeted for inclusion, or withdrawn
- Markus and Ole: produce sample periodicals docs as in ZedAI_periodicals_telcon_20090819
- Markus: describe our use of xlink:simpletype as an implicit default a la docbook5
- Dennis: solve Issue 60
- Dennis: solve Issue 61
- Dennis: solve Issue 46
- Josh: solve Issue 50
- Markus to add spec prose on cascading level for inline styles: "For the purposes of the CSS cascade, these values are considered author-level"
- James: make sure the spec no longer claims to reserve the z3986-profile and feature values; instead define above rdfa solution [DONE, reservation for PLS remains]
- Dennis/Josh contact QTI and ask about replacing the HTML with host language text content set.
Agenda/Minutes
Reminder: ZedAI_Iteration4_Report#Deliverables_for_the_next_iteration deliverables for the next iteration
Observation: rdfa in html note published by the w3c
Observation: docbook5 up for voting
The metadata (ONIX/MODS) iteration deliverable
Page under development here: ZedAI_Meta_Data_-_OutOfLine_Proposal
Summary/discussion:
Matt: the issue that we are dealing with is pleasing MODS and ONIX camps, as well as versioning. The idea is to use out-of-line meta data sets, that are linked from the document head (with an identification of record type and version). The head can link to several records, if need be.
Some information should remain inline:
- Producer information: unique identifier
- Producer information: who they are, and location
- Perhaps title information?
Drawbacks is the added overhead for retrieving the external document infoset (and the URL may be a webservice URL).
Boris: is there a slot for Global Identifier such as ISBN inline?
Markus: we still dont know what the inline unique idenfier will be in terms of schemes. Matt: we went over this in the meta group; difficult to require particular scheme for example in the context of individual users (that arent hooked up to ISBN etc). We could perhaps come up with a few recommendations in the spec.
SVG and Object
(Boris owns these issues, here's a summary:)
SVG related
The basic questions, asked with input from our friends at ViewPlus are:
- how should SVG be integrated?
- via CDR (in which case it would be a blessed object mimetype)
- via CDI (in which case it would be a feature)
- via CDR+CDI
- which version(s)/flavors of SVG to allow? Should this be definable per profile perhaps?
- do we want to require SVG fallbacks to be provided?
- In CDR, object has a built-in mechanism for this
- In CDI, the content selection feature can be used
Comments:
ViewPlus: recommends external files
Boris: do we need to inject some of our own namespace elements into SVG as we do with MathML @Boris ask ViewPlus
ViewPlus recommends using 1.0?
Object related
- Issue 9:
- should profiles be able to define which mimetypes are allowed as object references? Should the spec define a baseline set of types that profiles may extend?
- should profiles be able to define for which object mimetypes object fallbacks (above text) must be provided?
Markus: Boris and Markus will meet on friday (13:00 UTC) to start dealing with this. All welcome to join.
Periodicals profile
Kenny/Ole: decision on whether to revive or drop needs to be taken
Kenny: checked with VA. Dont do newspapers at this time, however magazines are done, using XHTML. VA can live without this profile being included in the initial release of the spec.
Kenny: perhaps we could add a couple of things to the feeds profile; page continuation indicator. {Note from Markus: could be role on reference}
Markus: remembering James saying early on that print papers are a thing of the past.
Kenny: @check with Ole if he is ok with putting this profile to rest for a while.
Kenny: @own page continuation indicator issue.
Matt: I can see magazines and journals being somewhat interesting though.
Tentative recommendation to not do the periodicals profile now.
Packaging/mimetype
New potential deliverable: packaging and mimetype definitions
Dependency on part B developments, part A should reuse Part B packaging to a certain extent
New time satisfaction
All seems to be pretty happy with this new time, keeping for now.
