[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [Fwd: Re: [docbook] DocBook Technical Committee Meeting Minutes:15 July 2009]
Feedback on the publishers spec.
--Scott
-------- Original Message --------
Subject: Re: [docbook] DocBook Technical Committee Meeting Minutes: 15
July 2009
Date: Fri, 31 Jul 2009 16:12:32 -0600
From: Mimil Mimil <mimilowns@gmail.com>
To: Hudson, Scott <Scott.Hudson@flatironssolutions.com>
References: <01b101ca0583$bf087e60$6400a8c0@pazu>
<af7433920907231404q764f65ebnc52597019883f918@mail.gmail.com>
<4A68DA5D.4080800@flatironssolutions.com>
<af7433920907231458w16a40cf7q72fef21516bd0173@mail.gmail.com>
<4A68DFB9.3070005@flatironssolutions.com>
<af7433920907231519p1d0409cayed869480e387f386@mail.gmail.com>
<4A68E5E1.90702@flatironssolutions.com>
<4A68E6B6.9090908@flatironssolutions.com>
<af7433920907271209r2376708vc6561824dbaa0b2f@mail.gmail.com>
<4A6DFB67.3080501@flatironssolutions.com>
Hello Scott,
sorry for the long delay but I haven't been able to free much spare time
this week. I hope this little presentation document will give you some
inputs for the publisher spec.
- I haven't duplicated the information given in
http://www.mediachops.com/producer_chops/1_Production_Cycle/PDFs/screenplay_formatting.pdf
- I now agree on the need of different root elements (drama, poetry ...)
I am also making the maven/docbook presentation (I guess for tomorrow),
as for now I have completed wiki pages
(http://wiki.docbook.org/topic/Maven), tested it (simple maven
integration) and have release working maven artifacts. The presentation
will talk about maven, the simple integration and the advanced
integration using a dedicated maven plugin I am developer in.
See you later,
Cédric,
On Mon, Jul 27, 2009 at 9:09 PM, Scott Hudson
<scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>> wrote:
Sorry to hear that. We'll try to address your questions via the
OASIS comment facility and email then.
Best regards,
--Scott
Scott Hudson
Senior XML Architect
+1 (303) 542-2146 | Office
+1 (303) 332-1883 | Cell
Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>
==========================================
Flatirons Solutions
http://www.flatironssolutions.com
Mimil Mimil wrote:
Hello,
I guess I am screwed on using my company for OASIS meeting, I
will have to fallback on making emails.
See you later,
Cédric,
On Fri, Jul 24, 2009 at 12:39 AM, Scott Hudson
<scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>>> wrote:
Here's the dial-in info for France:
0800-917733
pcode: 16948621
/Here’s a couple of tips when setting up international conference
calls: /
/1. //If your conference participants are calling outside the US
and Canada
<https://projects.flatironssolutions.com/eRoomReq/Files/Flatirons/Admin/0_21de0/International%20Conferencing%20Instructions%20%28WebEx%29.doc>,
they must dial the toll or toll-free number
<https://projects.flatironssolutions.com/eRoomReq/Files/Flatirons/Admin/0_246d6/Conf%20Call_International%20toll%20and%20toll%20free%20numbers%20%28WebEx%29.xls>
assigned to the country they are calling from. They must wait for
the “Welcome to WebEx” prompt before dialing the participant code
to be connected to the conference call./
/2. //If your participants cannot connect to the conference for
any reason, they can call the toll international technical
support
line to get immediate help in connecting to the call. That number
is +1-408-435-7088 (+ is where they might need to dial the US
country code, ‘00’)./
/3. //If your participants wish to dial a toll-free tech support
line, they can call the International Toll Free tech support
number assigned to their country. You can find those numbers
online at http://support.webex.com/support/phone-numbers.html/
/4. //If you wish to report technical issues to WebEx or get tech
support help, call 1-866-229-3239/
/5. //You can also get help and view training materials and
tutorials online at
http://support.webex.com/support/support-services.html/
Best regards,
--Scott
Scott Hudson Senior XML Architect
+1 (303) 542-2146 | Office
+1 (303) 332-1883 | Cell
Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>>
==========================================
Flatirons Solutions
http://www.flatironssolutions.com
Scott Hudson wrote:
http://www.timeanddate.com/worldclock/converted.html?month=8&day=4&year=2009&hour=14&min=0&sec=0&p1=224&p2=195
<http://www.timeanddate.com/worldclock/converted.html?month=8&day=4&year=2009&hour=14&min=0&sec=0&p1=224&p2=195>
<http://www.timeanddate.com/worldclock/converted.html?month=8&day=4&year=2009&hour=14&min=0&sec=0&p1=224&p2=195
<http://www.timeanddate.com/worldclock/converted.html?month=8&day=4&year=2009&hour=14&min=0&sec=0&p1=224&p2=195>>
Looks like 11pm for you. Let me know what time would work
better for you.
Best regards,
--Scott
Scott Hudson Senior XML Architect
+1 (303) 542-2146 | Office
+1 (303) 332-1883 | Cell
Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>>
==========================================
Flatirons Solutions
http://www.flatironssolutions.com
Mimil Mimil wrote:
I just need to convince my manager and find the oasis
contact inside my company, I will do that tomorrow.
could you use
http://www.timeanddate.com/worldclock/converter.html with
France location for me?
Regards,
Cédric,
On Fri, Jul 24, 2009 at 12:10 AM, Scott Hudson
<scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>>>> wrote:
Actually, Mary was just concerned that you be an OASIS
member. If
that's the case, we'd still love to have you at our
next meeting!
Tuesday, 04 August 2009, 12:00pm to 01:00pm PT
Dial US/Canada toll-free number: 1-866-699-3239
Participant Code: 16948621
I'm trying to locate the int'l dialing number, so will
send that
soon. This time may be difficult for you, as that may
be midnight?
Let me know a better time, and I'll try to reschedule
with the
committee...
Best regards,
--Scott
Scott Hudson Senior XML Architect
+1 (303) 542-2146 | Office
+1 (303) 332-1883 | Cell
Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>>>
==========================================
Flatirons Solutions
http://www.flatironssolutions.com
Mimil Mimil wrote:
if it can help my company seems to be a
"contributor" (France
Telecom)
and I also work on OpenFormula specification
for an
opensource
implementation that is also used by OpenOffice and
maybe Sun too.
If acting as France Telecom (was not my choice at
first to
simplify) I just need to ask if I can speak
for them.
Cédric,
On Thu, Jul 23, 2009 at 11:47 PM, Scott Hudson
<scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>>>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>>>>> wrote:
Unfortunately, Mary McRae just informed me that
you must be an
OASIS member to participate in committee
meetings. Still,
we would
welcome any further comments you may have!
This specification was started as an attempt to
broaden the
scope
and acceptance of DocBook outside of the
traditional
software and
hardware documentation.
Best regards,
--Scott
Scott Hudson Senior XML Architect
+1 (303) 542-2146 | Office
+1 (303) 332-1883 | Cell
Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>>>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>>>>
==========================================
Flatirons Solutions
http://www.flatironssolutions.com
Mimil Mimil wrote:
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
<scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>>>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>>>>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>>>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>
<mailto:scott.hudson@flatironssolutions.com
<mailto:scott.hudson@flatironssolutions.com>>>>>> 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
Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>>>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>>>>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>>>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>
<mailto:Scott.Hudson@flatironssolutions.com
<mailto:Scott.Hudson@flatironssolutions.com>>>>>
==========================================
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
<davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>
<mailto:davep@dpawson.co.uk <mailto:davep@dpawson.co.uk>>
<mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>
<mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>>> <mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>
<mailto:davep@dpawson.co.uk <mailto:davep@dpawson.co.uk>>
<mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>
<mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>>>>
<mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>
<mailto:davep@dpawson.co.uk <mailto:davep@dpawson.co.uk>>
<mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>
<mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>>> <mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>
<mailto:davep@dpawson.co.uk <mailto:davep@dpawson.co.uk>>
<mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>
<mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>>>>>
<mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>
<mailto:davep@dpawson.co.uk <mailto:davep@dpawson.co.uk>>
<mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>
<mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>>>
<mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>
<mailto:davep@dpawson.co.uk <mailto:davep@dpawson.co.uk>>
<mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>
<mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>>>> <mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>
<mailto:davep@dpawson.co.uk <mailto:davep@dpawson.co.uk>>
<mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>
<mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>>>
<mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>
<mailto:davep@dpawson.co.uk <mailto:davep@dpawson.co.uk>>
<mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>
<mailto:davep@dpawson.co.uk
<mailto:davep@dpawson.co.uk>>>>>>> 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
--
Scott Hudson
Senior XML Architect
+1 (303) 542-2146 | Office
+1 (720) 663-7268 | Gvoice
Scott.Hudson@flatironssolutions.com
http://www.flatironssolutions.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]