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?


Mary, to follow up on JoAnn's comment, the DITA TC is already demonstrating near-conformant OASIS output style for PDF using DITA as source. DocBook and ODF also have output formatting for OASIS. DITA's alignment with web content strategies might argue somewhat for exploring a hosted OASIS review system around that architecture (the Chair suggests delicately).

The rub for any XML standard is providing appropriate authoring for participants. I believe that the ideal scenario is for OASIS to host a collaborative authoring/review environment that hides whatever XML standard is used under a WYSIWYG authoring/rendering interface. These can be done (and have been), but not without significant application work to fit the OASIS business rules and integration into Kavi for review tracking and the SVN back end for version control.

And since one of your original requirements was "no programming," this appears to remain only a suggestion. The DITA TC is willing to share our experiences with how we are currently producing DITA 1.2 for its anticipated Public Review.

By the way, the DITA TC has a hibernating "DITA for Standards" activity that could produce an OASIS XML recommendation in a few month's time if reactivated and driven with high priority.

--
Don Day,
Chair, OASIS DITA TC

Mary McRae wrote:
B05B8A69-E2D3-4552-BE42-15C9247CB9F7@oasis-open.org" type="cite">
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






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