As long as it's XML, we can each work in whatever tool we'd like, seems
to me.
JoAnn
JoAnn Hackos PhD
Co-chair DITA Adoption TC
Comtech Services, Inc.
Skype joannhackos
-----Original Message-----
From: Frederick Hirsch [mailto:]
Sent: Thursday, April 22, 2010 1:08 PM
To: ext Mary McRae
Cc: Frederick Hirsch; Bob Freund; Dave Ings;
Subject: Re: [chairs] What can Standards Development / TC Administration
do to help?
I see the benefit of automation of publication checking and tool
driven production of various output formats. This also might make
useful templates easier to work with.
What about authoring tools, or would editors be working in ed/vi/emacs
(not that all mind doing so)?
regards, Frederick
Frederick Hirsch
Nokia
On Apr 22, 2010, at 12:57 PM, ext Mary McRae wrote:
> Agreed. How would the chairs feel about mandating all specs be
> created in an OASIS XML format?
>
> m
>
> On Apr 22, 2010, at 12:40 PM, Bob Freund wrote:
>
>> How much of this review might be automated?
>> might be a lot if we had an xml publication format.
>>
>> On Apr 22, 2010, at 9:24 AM, Dave Ings wrote:
>>
>>> +1
>>>
>>> This would really cut down on the iterative churn that seems to
>>> frustrate the people involved in the publication process. Great
>>> idea!
>>>
>>> Regards, Dave Ings,
>>> Emerging Software Standards
>>> Email:
>>> Yahoo Messenger: dave_ings
>>>
>>> <graycol.gif>Hanssens Bart ---2010/04/22 09:02:30 AM---> Would you
>>> like us to review your specifications prior to TC ballots so you
>>> don't need to go back a
>>>
>>> From: Hanssens Bart <>
>>> To: Mary McRae <>,
"
>>> " <>
>>> Date: 2010/04/22 09:02 AM
>>> Subject: RE: [chairs] What can Standards Development / TC
>>> Administration do to help?
>>>
>>>
>>>
>>>
>>>
>>> > Would you like us to review your specifications prior to TC
>>> ballots so you don't need to go back and fix stuff afterwards?
>>>
>>> That would be very helpful indeed, especially for new TC's /
>>> people submitting specifications for the first time...
>>>
>>>
>>> Best regards
>>>
>>> Bart
>>
>
