OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

chairs message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [chairs] What can Standards Development / TC Administration doto help?


Frederick,

On 4/22/2010 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.
>
+1!
> What about authoring tools, or would editors be working in ed/vi/emacs 
> (not that all mind doing so)?
>
Assuming a format for OASIS standards was agreed upon, I think the major 
editors could be configured with templates or stylesheet mechanisms to 
produce the correct output in whatever format.

The key would be OASIS staff or better yet, automation, rejecting (not 
correcting) documents that deviated from the specified format due to 
creative efforts of its editors.

The usual excuses that editors can't follow directions, aren't 
professional editors (then why are they editors?), the rules are just 
too hard, etc., need to be disregarded. Other standards organizations 
don't accept "best efforts" or "good intentions" and neither should OASIS.

If we want a professional reputation for OASIS standards, and I assume 
we all do, then we need to produce professional quality work. The rules 
and tools should assist in meeting that goal.

Hope you are having a great day!

Patrick



> 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
>>>
>>
>
>

-- 
Patrick Durusau
patrick@durusau.net
Chair, V1 - US TAG to JTC 1/SC 34
Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]