+1
*Requiring* XML would be a potential barrier for more text-oriented
specs and their editors;
Having specs in XML would no doubt offer a clear advantage, but
let’s concentrate on having the core templates first – and then seeing how they
can be applied to different editing environments…
Regards,
Peter
From: Kelvin Lawrence
[mailto:klawrenc@us.ibm.com]
Sent: Thu, 22 April 2010 12:39
To: Mary McRae
Cc: Bob Freund; chairs@lists.oasis-open.org; Frederick Hirsch; Dave Ings
Subject: Re: [chairs] What can Standards Development / TC Administration
do to help?
As
much as I am an XML advocate, requiring the use of an XML editor or a text
editor like Vi to author documents is a major non starter for me. I want to be
able to use my word processor to edit WYSIWIG style. One of the things I have
always found hard at W3C is that specs are authored in XML and then processed
by style sheets to produce the specs. While it is a great use of the
technology, it is not the easiest way for an editor to work especially as will
be the case in many TCs an editor not skilled in the art of working in native
XML but very comfortable using a word processor type app.
Cheers
Kelvin
From:
|
Mary
McRae <mary.mcrae@oasis-open.org>
|
To:
|
Frederick
Hirsch <frederick.hirsch@nokia.com>
|
Cc:
|
Bob
Freund <Bob.Freund@hitachisoftware.com>, Dave Ings
<ings@ca.ibm.com>, "chairs@lists.oasis-open.org"
<chairs@lists.oasis-open.org>
|
Date:
|
04/22/2010
02:30 PM
|
Subject:
|
Re:
[chairs] What can Standards Development / TC Administration do to help?
|
There's a few free XML editors out there, or
maybe a handful of companies would like to make their products available for
use by TC members.
Mary
On Apr 22, 2010, at 3:08 PM, Frederick Hirsch wrote:
> 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: ings@ca.ibm.com
>>>> 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 <Bart.Hanssens@fedict.be>
>>>> To:
Mary McRae <mary.mcrae@oasis-open.org>,
"chairs@lists.oasis-open.org" <chairs@lists.oasis-open.org>
>>>> 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
>>>
>>
>