Hello, I would say why not if it is compatible with my daily work time, I will try to grab more knowledge around this matter.
I think we (well I) need to have more information about the context of this specification. - Is there a "customer" requiring it and already have some "requirements"? - Or any ideas from a pure brainstorming on this topic are also welcome? I also would like to present the work I did with Maven (java building tool) and Docbook because I really think it is a nice toolchain (I guess most of you are not aware of this work). I don't know it the TC (if this is the next meeting you are talking about) is the right place for that but I can make the presentation short (or schedule it another date). However it depends when is the meeting in order to gather all the informationI need. Regards, Cédric, On Wed, Jul 22, 2009 at 6:08 PM, Scott Hudson < [email protected]> wrote: > Cédric, > > thank you so much for your comments. I'll bring this information up at our > next meeting. Perhaps you would also be interested in joining the meeting to > provide additional comments? Let me know and I'll send meeting info. > > As for the similarity of the models, we wanted to enable semantic > distinction in the elements, but provide a common framework for how lines > would be marked up. Additional elements could be added as you have > indicated, but we did not want to add so many specific elements to be too > restrictive.This is why the db.all.blocks pattern is also allowed between > lines and linegroups. > > Thanks and best regards, > > --Scott > > Scott Hudson > Senior XML Architect > > +1 (303) 542-2146 | Office > +1 (303) 332-1883 | Cell > [email protected] > ========================================== > Flatirons Solutions > http://www.flatironssolutions.com > > > > Mimil Mimil wrote: > >> Hello, >> >> I did some research and I found interesting document about screenplays (a >> dialogue base interaction too) and they use the following additional >> informations: >> >> - scene numbering >> - scene slugs: information about the action location (setting, location, >> time of the day) >> - scene breaks: information about the action rhythm >> - scene description: information about the action environment >> - dialogue: vocal direction, emotion >> >> Everything is explained at >> http://www.mediachops.com/producer_chops/1_Production_Cycle/PDFs/screenplay_formatting.pdf >> >> Maybe something to take into account for the publisher spec? >> >> Regards, >> Cédric, >> >> On Tue, Jul 21, 2009 at 8:18 AM, Dave Pawson <[email protected]<mailto: >> [email protected]>> wrote: >> >> On 07/20/2009 10:18 PM, Mimil Mimil wrote: >> >> Hello, >> >> I just have a little comment on 8.Publishing Subcommittee >> report ... Scott suggests everyone read it and provide comments. >> >> With an external view (no knowledge of publishing) I wondered >> what is the real motivation to have 3 distinct elements >> (dialogue, drama, poetry) because they seem to have the same >> goal "speeches" and also have the same xml definition in the >> spec >> ( >> http://docs.oasis-open.org/docbook/specs/publishers-1.0-spec-cd-01.pdf) >> If the definition is the same, isn't the role attribute >> sufficient within a single dialogue element? >> Or is it a choice made to simplify the stylesheet work as >> these elements really need a different printing layout? >> >> Best regards, >> Cédric, >> >> >> With some (not a lot) of experience in marking up both poetry and >> drama, I can state >> that they are quite different in some ways, particularly if >> certain aspects of the visual >> presentation of the source is required to be captured. >> >> >> >> >> regards >> >> -- Dave Pawson >> XSLT XSL-FO FAQ. >> http://www.dpawson.co.uk >> >> >>
