[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [dita] Providing a DITA OT plug-in for specs available to other OASIS users
My opinion is that the DITA TC (1) should develop the standard and
avoid aligning itself with any particular implementation and (2) has plenty of
work to do on the standard and already has a track record for taking much
longer than thought at first to get out the next version and so shouldn't spend
time on tools. So for several reasons I prefer choice #3 (which might also be the
easiest given the OASIS process). paul From: Kristen Eberlein
[mailto:keberlein@sdl.com] Robert has
finished a first round of work on the plug-in (thanks, Robert!), and so
I’ve started a conversation with Robin Cover about how best to make the
plug-in available. Since it will need documentation providing information about
how to set up the plug-in up and configure a bookmap to hold the requisite
publication information, it does involve a TC work artifact, which would
be the new non-standards work-track item – a committee note. Here are what
our options appear to be: 1. Apply to the TC Admin for requisite
metadata, produce the document per whatever “template,” label
the document as a working draft, and give it to the TC Admin who will make
it available from http://docs.oasis-open.org/templates/ 2. Apply to the TC Admin for requisite
metadata, produce the document per whatever “template,” go through
the formal review process to approve the document as a TC work product. 3. Make the plug-in and documentation
available from another venue,
for example, Sourceforge or dita.xml.org. I think that
the TC will need to consider the pros and cons of each approach and decide how
it wants to move forward with this item. I’ll
send another e-mail to the list explaining the OASIS processes that the TC
would need to follow for options 1 or 2. Best regards, Kris |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]