ZedAI telcon 20090126
From zedwiki
Note: The 26 January 2009 meeting will be held at 1400h UTC. Find the meeting time in your geographical location.
Contents |
Scribe
Kenny
Regrets
Markus, Stephen, Boris
Previous Action Items
- Markus/Per: metadata review, draft approach for realizing as module
- Markus fix ZedAI main page, start a ZedAI Overview page (postponed, Markus is working on spec prose first.)
- Sam - gathering sample documents.
- Kenny - gathering sample documents.
- Markus to contact Oxygen for possible free licenses.
- Markus to invite people for profile testing.
- Markus to ask the DAISY list about how newspapers/periodicals markup is currently being done.
- Gregory to research mechanisms for local extension of taxonomies
Action items closed in this Telecon
- James to begin research on XInclude and/or other strategies for splitting document over multiple files (James has posted information about XInclude to the list)
- Kenny to investigate Chicago Manual of Style equivalent for periodicals (No CMOS equivalent found. Alternative leads found; information about these leads will be posted to the list before the next telecon)
New Action Items
- Dennis to post information about QTI to the list.
- kenny to post information about the leads to the list.
- Stephen to assist in documenting the elements in the Zed AI profile suite.
Agenda
Discussion: advanced/text book profile scope
Question: is the scope as outlined at ZedAI_Profiles_Overview a reasonable starting point for an advanced/text book profile?
The approach would be to create the modules that would realize such a profile, assemble the profile, and then review (including a review to determine if separation between simple/advanced book profiles is worthwhile).
(We also have the pending issue of finding out if there is a way to make associations to external grammars (MathML, SVG, DocBook5) dynamic within the profile, as opposed to statically linked. This need not be discussed at this time, we can go for static in the short term.)
Discussion: out of spine content (sidebars et al)
Question: what design shall we choose for an out-of-spine-content module?
Please review Out of spine content module for an initial orientation.
Periodicals profile
@markus create the base schema for the periodicals profile, adding the section head module as defined in iteration one. Add to SVN.
Kenny: next steps?
Job vacancy: grammar documentation
Per has now created the mechanism to include prose descriptions of elements and attributes in the generated schema documentation. We are looking for individuals who would be willing to help with authoring prose descriptions. This will be done under a longer period of time, with increasing intensity as the grammars stabilize. In some cases, this work will include moving selected portions over from Structure Guidelines, in other cases authoring-from-scratch. Native english speakers preferred (including those who speak australian).
(Obvious note: the job is limited to documenting elements/attributes in the DAISY namespace. For other namespaces, we just provide URLs to external documentation.)
Discussion: Chicago Manual of Style
A new page is up describing the components of a publication, as given by the Chicago Manual of Style. We need to review it and decide what we want to include in our taxonomy, what is redundant, and what does not apply. The review does not need to take place on the call, but the document will be introduced if time allows.
Minutes
General
Kenny: I should have an update on the Periodicals Profile by next week. I have found a few leads on friday pertaining to the digitisation of newspapers. I will post information about these leads to the list.
Marisa: I added something to the agenda: Chicago manual of style.
James:I have posted material about x-include to the list. I got a response from Per. At some stage this will become an agenda item on the list.
kenny: I have had a chat with Kate and Leona about the sample documents. Sam, kate and I will work over the next few weeks to get the sample documents ready.
Sam: I will send kenny an email to touch base on the sample documents.
Discussion on agenda items
James: In Reference to Markus's pointer on the agenda page, is this enough for the advance book profile? Anyone have any thoughts on this?
kate: I think its a good starting point.
James: Per, you have been collecting items on the advance book profile, what do you think?
Per: I think its a great start. I came up with the exercise markup e.g. List items such as exercise 1a, 1b.
james: In terms of the exercises markup, I was thinking of items such as "fill in the blanks".
Per: You could use the normal section and h element combination for exercise 1a, 1b and so forth. We have this problem in Norway. We would like to avoid hard coding the exercise title.
James: The Advance book profile looks to me like a text book profile. Structures present in the Advance Book Profile are classic text book structures.
Marisa: Is there any desire to make the exercises that we intend to create markup for, interactive?
Per: I would like to see that.
Marisa: I am thinking about things that we would need to put in to make exercises interactive.
James: You need to define what needs to be interactive. It would then be implemented in the distribution format.
James: generally fill in the blanks are underscore characters.
dennis: I am aware of a technology called QTI. It stands for question and test interoperability specification. I recall QTI light: a solution that has a client side and a server side. I would be pleased to look at this for our purposes.
james: I like the idea of calling our Advanced book profile a text book profile.
Marisa: What other forms of highly structured books are converted to daisy? e.g. medical encyclopaedias?
James: We do a lot of legal books.
dennis: We get a lot of requests for government tax forms, insurance forms. A whole lot less text and a whole lot more interactivity. We get requests to convert this into daisy.
Marisa: xforms sounds like a good module for our Advance Book profile.
james: Everyone agrees that what we have for the advance/text book profile is a good start.
james: What is the difference between xforms and QTI?
Dennis: QTI is very focussed on different types of questions, validating the answers and sending them back to the server.
james: Do we need to choose between xforms and QTI? Or can they go hand in hand. (dennis will post information about QTI to the list)
James: Next area of discussion is out of spine content.
kenny: aria already has a few roles for out of spine content.
marisa: There's a lot that we need to do in terms of defining equivalencies between different namespaces|specs e.g. aria, chicago manual of style ...
marisa: I have posted a link on the agenda page which contains a whole lot of information about roles.
kenny: Will we do role="complementary" or <complementary>
james: we might define an element called box and then specialise it through roles.
Kenny: aria's focus is on the world wide web. our scope is broader.
james: Does everyone agree that we should have a generic element like box (perhaps we can rename it differently), and specialise it through the role attribute module?
(Everyone agreed)
dennis: you might like footnote to appear differently from a side bar. Is this catered for in our standard? some kinds of elements might be referenced differently from other elements e.g. footnotes.
James: Are notes and noterefs a part of the simple book profile?
per: yes.
James: we should be able to do such referencing through idrefs etc.
james: Lets get a periodicals profile update from kenny.
James: Kenny, can you liaise with Markus on the leads you have found?
James: Next agenda item - A technical writer required for prose.
Kenny: What is the time commitment required for this role?
Per: I don't think a lot of time is required for this. The documentation should be to the point. no talking book related issues. more to specify what an element is used for. not talking about new structure guidelines.
Kenny: I will volunteer for this. I have just finished the daisy online markup language ontology so I should be able to fit this in. It sounds very similar to what I did for the Daisy Online documentation.
James: On to the last agenda item. Marisa, do you have an update for us?
Marisa: we wanted to align our elements and roles to things from other grammars ie. waiARIA, chicago manual of style, docbook. Chicago manual of style has more prose. I have made a huge table that has a CMOS style and associated equivalencies. CMOS's view is that linear flow of a printed book should apply to an electronic book. There is a whole section on journals. You might be very interested in that Kenny.
matt: Perhaps there will be an owl rdf for the work of the metadata working group. I will send out an email to the group about the work of the metadata wg that will include information about the OWL implementation, and RDFA (which might be available in the future).
