ZedAI telcon 20091005
From zedwiki
Note: this meeting will be held at 1300h UTC. Find the meeting time in your geographical location.
Contents |
Present
Markus (scribe), Josh, James, Boris, Matt
Regrets
Per, Kenny
Previous Telcon
Action Items
New
- 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
- 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
Brought Along
- Markus check out that Issue 53 commit is correct : [DONE, yes it was]
- 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
- Markus: define the property to use on reference for issue 57 (reference role="object"?) [DONE - "image-placeholder" in core vocab]
- Markus: close all issues that are fixed by linking proposal [DONE]
- Boris: add issue to tracker re inversing pointing relationship between expansion and abbr [DONE, @markus fix in module, DONE]
- Per/Markus: have Content Selection draft available for review by next concall [DONE]
- Dennis: solve Issue 60
- Dennis: solve Issue 61
- 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"
Postponed beyond this iteration
- Matt (hopefully) propose whether we need specialized content models for bibliographies and indices (as opposed to section @role="bibliography") See ZedAI_Linking_Proposal
- 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) [DONE]
- Markus propose a runninghead element for use in conjunction with section/h
- Markus: update samples to define the z3986 CURIE prefix [DONE]
- 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]
- James/Markus: samples and primer etc changes in the spec, relating to linking proposal and link rel="z3986-profile" etc [DONE]
- Dennis/Josh contact QTI and ask about replacing the HTML with host language text content set.
Agenda/Minutes
Discussion: ZedAI_Iteration4_Report including deliverables for the next iteration
MathML
- MathML3 is now in Last Call, good news! Dennis's items remain, but are minor.
On the ONIX and MODS iteration deliverable
James: on use cases and usage scenarios. Many different ways of transactions, whats the use case of actually having metadata in the document itself? Many of these issues seem like data mapping issues. It would be helpful to clearly articulate how metadata within an AI file would be used and processed to know how to represent it.
Matt: this is the AI format, not a distribution format. Are we looking at the right stage where ONIX comes in to play?
James: does the metadata have to be an in-band communication with the document? In fact, if I am doing interlibrary loan, Ive already searched some institutions catalog to find the book. Why do I need anything more than the book identifier, and I can look up the rest from there.
Matt: think ONIX metadata is often used as a separate entity.
Matt: perhaps we could see metadata as associated with the ZedAI instead of as inlined.
James: one suggestion: required to have a UID, and one or more links with URIs that point to metadata resources; URIs can be local but separate files, online file URIs, or a webservice.
Matt: the only difficulty is transforming between different metadata standards.
Markus: look at the DOI proposal in Issue 49.
James: outcome of WIPO work could be a web service, as a way to alleviate transforms
Matt: Whatever we do needs to integrate well with the Global Library group, who are looking at MODS.
James: notes again that none of these issues relate to authoring, dont think it belongs here. An out-of-line solution is preferable.
Markus: agrees, both in terms of pushing this problems to the proper solution instance, and in terms of introducing some flexibility. Simple Dublin Core may be all thats viable for example in the Newsfeeds profile (these documents never make it into catalogs anyway, they are often no more than transient aggregations).
Conclusion: Matt, James, and Markus to create a wiki formulating an out-of-line metadata proposal The out-of-line-metadata posse.
Role Deliverable
@markus implement
note that we have the same risk here as for RDF/a in terms of CURIEs
Lists revisit
@markus, set up an initial concall with Matt
SVG and Object
@Markus to feed in information from ViewPlus re integration of SVG
@Boris: help deal with svg integration, help with object documentation and samples, address issue 9
New day/time for telcon
Proposal: options are
* stay with Monday 13:00 UTC * Mondays 21:00 UTC * Thursdays 21:00 UTC
