OASIS Darwin Information Typing Architecture (DITA) TC

Hi...

I've not been involved with the adoption group (too much going on), but 
have been lurking on the list. I've got one question .. is this group's 
charter to promote adoption of DITA or the DITA-OT? I assume that the 
answer is DITA, but thought I'd make sure.

There is a fine line between the two since it's the existence of the OT 
that makes DITA so compelling. Without the OT, DITA would just be 
another well thought out data model that requires a lot of work to 
implement. The OT lets you get from nowhere to somewhere substantial in 
short order, but that somewhere isn't typically very close to something 
that you'd actually ship to customers. It's like building a house .. you 
can get the framing up fairly quickly and it "looks" like you're close 
to being finished, but of course, it's putting the skin on that takes 
all the time and money. The OT lets you quickly get to a nice prototype 
phase that is great for validation .. but then the "fun" really begins.

Groups that have skilled development staff or lots of money to burn may 
be able to take the OT and pound it into something that will serve their 
publishing needs. You're much more likely to find in-house staff that 
will be able to get nice HTML-based content out of the OT than you'll 
find those with the FO expertise to get acceptable PDFs.

Regardless, the key point (to me) is that in using DITA your content 
lives in a non-proprietary format. You're not locked into using an 
expensive authoring tool just because it's too expensive to switch to 
something better. However, that doesn't mean you're not going to use a 
proprietary authoring (and publishing) tool, you're just free to switch 
if something better comes along. Everyone needs an editor of some kind. 
There are free or very inexpensive options, and there are more costly 
options (FM at $1000 is sill less than XMetaL or Arbortext at around 
$1500) .. you should choose something that suits your needs. For 
publishing, the OT offers one solution, but if you don't want to "get 
your hands dirty" you can use a tool to generate the type of output you 
need. This goes for HTML-based output with tools like RoboHelp, 
WebWorks, and Flare (soon?), as well as PDF output from FrameMaker (and 
Flare?). If your authoring tool can provide one or more types of output, 
that may be a benefit. It all depends on your needs and workflow.

I think it's great to work towards making the OT easier to use and 
easier to customize .. and this will happen over time. As the OT (and 
the OT documentation) matures, that will start to reduce the need for 
proprietary publishing tools. But until that time, one of the important 
pieces to promoting the adoption of DITA is the availability of these 
tools. I think it would be great to see an unbiased comparison of these 
tools/options that really discusses their pros and cons (there is no 
perfect tool). This would go a long way to reducing the confusion about 
how to proceed with implementing DITA.

Cheers!

...scott

Scott Prentice
Leximation, Inc.
www.leximation.com
+1.415.485.1892



Mark Poston wrote:
 > At the moment it is easier for a non technical user to work with
 > proprietary tools rather than having to customise the DITA-OT.
 >
 > As you suggest, the DITA OT is not something that you can easily pick
 > up, install and customise to create an output that is branded as you
 > need. You need to know a lot of XML-related technologies to make it
 > happen or employ consultants.
 >
 > When you take into consideration the time that learning the DOT and
 > then implementing it will take, the $1000 for FrameMaker (or whatever
 > tool you might decide to use) is a more cost effective solution, that
 > is much easy for an end user to customise with a lot less training.
 >
 > When I first developed the FrameMaker adapter for the DITA OT part of
 > the rationale behind this was to allow existing FrameMaker users to
 > keep it as their publishing tool, even if they had switched to a
 > different authoring tool. I think this still applies.
 >
 > Kind regards
 >
 > Mark Poston
 > Senior Consultant & Technical Architect
 > Mekon Ltd.
 > Tel. +44 (0)20 8722 8461
 > Skype: mark_mekon.com
 > Twitter: mekonltd & xpubs
 >
 > On 24 Mar 2009, at 16:33, Sowmya Kannan wrote:
 >
 >> Doesn't a license of Framemaker cost nearly $1000?
 >> Perhaps it is a question of setting the right expectation about the
 >> capabilities of the DITA OT. The DITA OT literature gives the
 >> impression that multiple output formats can be generated out of the
 >> box. There is no mention of the level of effort required to generate
 >> custom branded HTML output or print quality PDF output.
 >>
 >> The first look at the generated PDF output can be be really jarring!
 >>
 >> I feel like we should focus on documenting the following:
 >> For each output format:
 >> - what does DITA OT produce out of the box
 >> - what are the customization options
 >> - what are the technical details to implement a customization
 >> - what is the level of effort and cost associated with customization
 >> - are there commercial DITA OT plugins that can be purchased to
 >> accomplish customization, instead of hiring a consultant each time
 >>
 >> Perhaps the DITA OT needs a model like Red Hat Linux or MySQL, where
 >> the open source / free version is always available, but customers
 >> have to pay a nominal price for extras. For small-mid size companies,
 >> that may be a more palatable option than paying thousands of dollars
 >> for a proprietary product or extensive consulting work.
 >>
 >> My 2 cents.
 >>
 >> Thanks
 >> Sowmya
 >>
 >>
 >> Briana Wherry wrote:
 >>>
 >>>
 >>> Saw an interesting email chain this morning on the STC Single Source
 >>> SIG. An individual is looking for guidance. It sounds like she knows
 >>> that DITA is the right thing to do, but then it seems doesn’t really
 >>> understand how to achieve it with tools. I was most interested in
 >>> one of the replies which did a succinct job of pointing out exactly
 >>> how convoluted it is to achieve the few simple scenarios she wants
 >>> (html and pdf) and also potentially quite costly.
 >>>
 >>> I believe this is one of the most common scenarios we will find for
 >>> the tech author audience and the answer that Scott gave is good. It
 >>> does highlight, however, that this is not a simple thing to achieve
 >>> by any stretch.
 >>> I believe where we can make the biggest impression is to put a more
 >>> positive swing on this kind of answer, and as we discussed last
 >>> week, providing some sort of checklist against which to evaluate
 >>> tools as well as identifying what tools are out there. (preaching to
 >>> the choir, I know)
 >>>
 >>> I have added the email text for reference. (I am assuming this is
 >>> OK, as long as we don’t distribute further)
 >>>
 >>> Cheers, Briana
 >>>
 >>>
 >>> Hi Vickie...
 >>>
 >>> If you're to be authoring content in DITA you'll need an editor that
 >>> supports DITA. Some popular options are .. Oxygen, FrameMaker (with
 >>> DITA-FMx), XMetaL, Arbortext, XXE (and others ..
 >>> http://www.ditanews.com/tools/desktop_editors/). One of the nice
 >>> things about DITA is that you don't really need to decide on a
 >>> single authoring tool .. as long as it round-trips valid DITA it
 >>> won't matter. You can have people using XMetaL and others using
 >>> FrameMaker, and all of the files will integrate nicely with your
 >>> publishing process. As far as I know Author-IT will export DITA, but
 >>> I wouldn't consider it a DITA authoring tool because it can't open
 >>> DITA files (without a complicated import process).
 >>>
 >>> You can generate online output through the DITA Open Toolkit, and
 >>> after a bit of tweaking and effort, you'll probably have something
 >>> that works reasonably well. If you want something a bit more WYSIWYG
 >>> for building your HTML-based output, you might consider RoboHelp
 >>> (which now imports DITA files, but is not a DITA authoring tool) or
 >>> Quadralay's ePublisher.
 >>> Flare is poised to have DITA support, but as far as I know it's not
 >>> there yet.
 >>>
 >>> For PDF output, you can use the Open Toolkit, but in order to get
 >>> anything reasonably useful will require hiring an FO developer and
 >>> probably spending a substantial amount of time and money. FrameMaker
 >>> gives you nice looking PDF output right out of the box, and
 >>> modifying a FM template is infinitely easier than FO development.
 >>> Even if you don't use FM as your DITA authoring tool, you might
 >>> consider using it for PDF output.
 >>>
 >>> Cheers,
 >>>
 >>> ...scott
 >>>
 >>> Scott Prentice
 >>> Leximation, Inc.
 >>> www.leximation.com
 >>>
 >>>
 >>> Vickie Hearne wrote:
 >>> > Hello all:
 >>> >
 >>> > I'm working with a software company to help them migrate their
 >>> unstructured content from their wiki into a more structured (dita)
 >>> format.
 >>> >
 >>> > We need electronic output (a help system or another nested,
 >>> layered structure that can be delivered via the web), and the
 >>> occasional .pdf manuals for training, etc. While not graphic
 >>> intensive (screen shots mostly), we would like to include a video
 >>> with the task component.
 >>> >
 >>> > I'm reluctant to take them down the Robo path. Even though I have
 >>> a lot of experience with the product, potentially, there could be
 >>> multiple contributors, and, Robo is not the most intuitive for the
 >>> occasional author. I also would the the single-source tool to be
 >>> leveraged for other non-product content, like RFP response, contract
 >>> prep, sows, etc.
 >>> >
 >>> > Any insight suggestions (and warnings!) would be greatly appreciated.
 >>> >
 >>> > Thanks,
 >>> >
 >>> > -v
 >>> >
 >>> > PS: I've used Author-IT in the past, and am comfortable with the
 >>> ease of the UI. Anyone working with the 5.0 version? Thanks again.
 >>>
 >
 >
 > ---------------------------------------------------------------------
 > To unsubscribe from this mail list, you must leave the OASIS TC that
 > generates this mail. Follow this link to all your TCs in OASIS at:
 > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
 >

Hi Scott,
The mission of the Adoption TC is to promote DITA adoption, including
the OT usability issues. Our discussion today focused on the issues of
the OT that has been in the email exchange. If people cannot understand
the OT and are misled by the instructions for its use, then they stop
there. We discussed the practicality of informing people that there are
tools available. We don't want to get into the same trouble that the
Help SC did by discussing tools in an official OASIS document, but we
believe there would be other ways to publish the information that people
would find valuable.

Thanks for your input,
JoAnn

JoAnn Hackos PhD
President
Comtech Services, Inc.
joann.hackos@comtech-serv.com
Skype joannhackos




                                                

					
                                                    

        
                                                
				
                                                

                                                    
                                                
                                                
                                            

Hi JoAnn...

I think that it's unfortunate that the discussion of tools in official 
Oasis documents is not allowed. DITA (and most any XML standard), can't 
exist without tools (specifically authoring tools, but also publishing 
tools), and to be unable to discuss how DITA interacts with specific 
tools just complicates issues that real users are trying to grasp. It 
seems like there should be some way to discuss these interactions in a 
way that doesn't conflict with the goals of Oasis. When this discussion 
is presented by tool vendors it may be seen as being biased, but if it 
could be done by a group that attempts to be unbiased, it would be much 
more beneficial to end users.

Cheers,

...scott



JoAnn Hackos wrote:
> Hi Scott,
> The mission of the Adoption TC is to promote DITA adoption, including
> the OT usability issues. Our discussion today focused on the issues of
> the OT that has been in the email exchange. If people cannot understand
> the OT and are misled by the instructions for its use, then they stop
> there. We discussed the practicality of informing people that there are
> tools available. We don't want to get into the same trouble that the
> Help SC did by discussing tools in an official OASIS document, but we
> believe there would be other ways to publish the information that people
> would find valuable.
>
> Thanks for your input,
> JoAnn
>
> JoAnn Hackos PhD
> President
> Comtech Services, Inc.
> joann.hackos@comtech-serv.com
> Skype joannhackos
>
>
>   

I am sending this message to try to dispel some unfortunate rumors  
that are floating around. OASIS has made no statements one way or the  
other about the legalities or appropriateness of the guide. OASIS has  
not ruled that this document cannot be published if approved by the  
DITA Technical Committee. I have asked to speak with the subcommittee,  
but they are as of yet unclear as to when their next meeting will be.

There has also been some mention of issues relating to process. The  
process is very clear. Subcommittees are unable to make any binding  
decisions. They cannot approve documents; they can only recommend to  
the parent committee. It is for this very reason that it's important  
for subcommittee members to maintain their voting rights at the TC  
level. It's also extremely important for the subcommittees and main TC  
to stay in touch with each other; if there is general disagreement  
about work currently being undertaken at the subcommittee level,  
concerns should be addressed before significant effort is spent on  
development.

Any member can bring an item to the Chair for inclusion on the agenda.  
A Voting Member can make a motion to bring the approval of a document  
for vote. As long as there is a 2nd (also by a Voting Member),  
discussion can occur, and at some point the Chair must close the  
discussion and bring the motion to a vote, unless the original motion  
is withdrawn by the proposer. Again, anyone with voting rights can  
then vote in the affirmative or negative. Approval as a Committee  
Draft requires a full majority - that is, +50% of all voting members  
(not just those in attendance).

If anyone has any questions or concerns please feel free to contact me  
directly.

Regards,

Mary


Mary P McRae
Director, Technical Committee Administration
OASIS: Advancing open standards for the information society
email: mary.mcrae@oasis-open.org
web: www.oasis-open.org
twitter: fiberartisan
phone: 1.603.232.9090




>

I am sending this message to try to dispel some unfortunate rumors  
that are floating around. OASIS has made no statements one way or the  
other about the legalities or appropriateness of the guide. OASIS has  
not ruled that this document cannot be published if approved by the  
DITA Technical Committee. I have asked to speak with the subcommittee,  
but they are as of yet unclear as to when their next meeting will be.

There has also been some mention of issues relating to process. The  
process is very clear. Subcommittees are unable to make any binding  
decisions. They cannot approve documents; they can only recommend to  
the parent committee. It is for this very reason that it's important  
for subcommittee members to maintain their voting rights at the TC  
level. It's also extremely important for the subcommittees and main TC  
to stay in touch with each other; if there is general disagreement  
about work currently being undertaken at the subcommittee level,  
concerns should be addressed before significant effort is spent on  
development.

Any member can bring an item to the Chair for inclusion on the agenda.  
A Voting Member can make a motion to bring the approval of a document  
for vote. As long as there is a 2nd (also by a Voting Member),  
discussion can occur, and at some point the Chair must close the  
discussion and bring the motion to a vote, unless the original motion  
is withdrawn by the proposer. Again, anyone with voting rights can  
then vote in the affirmative or negative. Approval as a Committee  
Draft requires a full majority - that is, +50% of all voting members  
(not just those in attendance).

If anyone has any questions or concerns please feel free to contact me  
directly.

Regards,

Mary


Mary P McRae
Director, Technical Committee Administration
OASIS: Advancing open standards for the information society
email: mary.mcrae@oasis-open.org
web: www.oasis-open.org
twitter: fiberartisan
phone: 1.603.232.9090




>

I am sending this message to try to dispel some unfortunate rumors  
that are floating around. OASIS has made no statements one way or the  
other about the legalities or appropriateness of the guide. OASIS has  
not ruled that this document cannot be published if approved by the  
DITA Technical Committee. I have asked to speak with the subcommittee,  
but they are as of yet unclear as to when their next meeting will be.

There has also been some mention of issues relating to process. The  
process is very clear. Subcommittees are unable to make any binding  
decisions. They cannot approve documents; they can only recommend to  
the parent committee. It is for this very reason that it's important  
for subcommittee members to maintain their voting rights at the TC  
level. It's also extremely important for the subcommittees and main TC  
to stay in touch with each other; if there is general disagreement  
about work currently being undertaken at the subcommittee level,  
concerns should be addressed before significant effort is spent on  
development.

Any member can bring an item to the Chair for inclusion on the agenda.  
A Voting Member can make a motion to bring the approval of a document  
for vote. As long as there is a 2nd (also by a Voting Member),  
discussion can occur, and at some point the Chair must close the  
discussion and bring the motion to a vote, unless the original motion  
is withdrawn by the proposer. Again, anyone with voting rights can  
then vote in the affirmative or negative. Approval as a Committee  
Draft requires a full majority - that is, +50% of all voting members  
(not just those in attendance).

If anyone has any questions or concerns please feel free to contact me  
directly.

Regards,

Mary


Mary P McRae
Director, Technical Committee Administration
OASIS: Advancing open standards for the information society
email: mary.mcrae@oasis-open.org
web: www.oasis-open.org
twitter: fiberartisan
phone: 1.603.232.9090




>

Agreed. When considering documentation approaches, the OT is what makes 
DITA attractive - publish to multiple output formats etc.
The need for a well documented, flexible OT becomes even more crucial in 
a situation where organizations have Docbook publishing systems in 
place. The question that we hear from senior management is we already 
have a tools chain in place, what new tools do we need to develop to 
support DITA, and what is the LOE?

So there are multiple bridges to be crossed on the way to DITA Adoption.

Sowmya



Scott Prentice wrote:
> Hi...
>
> I've not been involved with the adoption group (too much going on), 
> but have been lurking on the list. I've got one question .. is this 
> group's charter to promote adoption of DITA or the DITA-OT? I assume 
> that the answer is DITA, but thought I'd make sure.
>
> There is a fine line between the two since it's the existence of the 
> OT that makes DITA so compelling. Without the OT, DITA would just be 
> another well thought out data model that requires a lot of work to 
> implement. The OT lets you get from nowhere to somewhere substantial 
> in short order, but that somewhere isn't typically very close to 
> something that you'd actually ship to customers. It's like building a 
> house .. you can get the framing up fairly quickly and it "looks" like 
> you're close to being finished, but of course, it's putting the skin 
> on that takes all the time and money. The OT lets you quickly get to a 
> nice prototype phase that is great for validation .. but then the 
> "fun" really begins.
>
> Groups that have skilled development staff or lots of money to burn 
> may be able to take the OT and pound it into something that will serve 
> their publishing needs. You're much more likely to find in-house staff 
> that will be able to get nice HTML-based content out of the OT than 
> you'll find those with the FO expertise to get acceptable PDFs.
>
> Regardless, the key point (to me) is that in using DITA your content 
> lives in a non-proprietary format. You're not locked into using an 
> expensive authoring tool just because it's too expensive to switch to 
> something better. However, that doesn't mean you're not going to use a 
> proprietary authoring (and publishing) tool, you're just free to 
> switch if something better comes along. Everyone needs an editor of 
> some kind. There are free or very inexpensive options, and there are 
> more costly options (FM at $1000 is sill less than XMetaL or Arbortext 
> at around $1500) .. you should choose something that suits your needs. 
> For publishing, the OT offers one solution, but if you don't want to 
> "get your hands dirty" you can use a tool to generate the type of 
> output you need. This goes for HTML-based output with tools like 
> RoboHelp, WebWorks, and Flare (soon?), as well as PDF output from 
> FrameMaker (and Flare?). If your authoring tool can provide one or 
> more types of output, that may be a benefit. It all depends on your 
> needs and workflow.
>
> I think it's great to work towards making the OT easier to use and 
> easier to customize .. and this will happen over time. As the OT (and 
> the OT documentation) matures, that will start to reduce the need for 
> proprietary publishing tools. But until that time, one of the 
> important pieces to promoting the adoption of DITA is the availability 
> of these tools. I think it would be great to see an unbiased 
> comparison of these tools/options that really discusses their pros and 
> cons (there is no perfect tool). This would go a long way to reducing 
> the confusion about how to proceed with implementing DITA.
>
> Cheers!
>
> ...scott
>
> Scott Prentice
> Leximation, Inc.
> www.leximation.com
> +1.415.485.1892
>
>
>
> Mark Poston wrote:
> > At the moment it is easier for a non technical user to work with
> > proprietary tools rather than having to customise the DITA-OT.
> >
> > As you suggest, the DITA OT is not something that you can easily pick
> > up, install and customise to create an output that is branded as you
> > need. You need to know a lot of XML-related technologies to make it
> > happen or employ consultants.
> >
> > When you take into consideration the time that learning the DOT and
> > then implementing it will take, the $1000 for FrameMaker (or whatever
> > tool you might decide to use) is a more cost effective solution, that
> > is much easy for an end user to customise with a lot less training.
> >
> > When I first developed the FrameMaker adapter for the DITA OT part of
> > the rationale behind this was to allow existing FrameMaker users to
> > keep it as their publishing tool, even if they had switched to a
> > different authoring tool. I think this still applies.
> >
> > Kind regards
> >
> > Mark Poston
> > Senior Consultant & Technical Architect
> > Mekon Ltd.
> > Tel. +44 (0)20 8722 8461
> > Skype: mark_mekon.com
> > Twitter: mekonltd & xpubs
> >
> > On 24 Mar 2009, at 16:33, Sowmya Kannan wrote:
> >
> >> Doesn't a license of Framemaker cost nearly $1000?
> >> Perhaps it is a question of setting the right expectation about the
> >> capabilities of the DITA OT. The DITA OT literature gives the
> >> impression that multiple output formats can be generated out of the
> >> box. There is no mention of the level of effort required to generate
> >> custom branded HTML output or print quality PDF output.
> >>
> >> The first look at the generated PDF output can be be really jarring!
> >>
> >> I feel like we should focus on documenting the following:
> >> For each output format:
> >> - what does DITA OT produce out of the box
> >> - what are the customization options
> >> - what are the technical details to implement a customization
> >> - what is the level of effort and cost associated with customization
> >> - are there commercial DITA OT plugins that can be purchased to
> >> accomplish customization, instead of hiring a consultant each time
> >>
> >> Perhaps the DITA OT needs a model like Red Hat Linux or MySQL, where
> >> the open source / free version is always available, but customers
> >> have to pay a nominal price for extras. For small-mid size companies,
> >> that may be a more palatable option than paying thousands of dollars
> >> for a proprietary product or extensive consulting work.
> >>
> >> My 2 cents.
> >>
> >> Thanks
> >> Sowmya
> >>
> >>
> >> Briana Wherry wrote:
> >>>
> >>>
> >>> Saw an interesting email chain this morning on the STC Single Source
> >>> SIG. An individual is looking for guidance. It sounds like she knows
> >>> that DITA is the right thing to do, but then it seems doesn’t really
> >>> understand how to achieve it with tools. I was most interested in
> >>> one of the replies which did a succinct job of pointing out exactly
> >>> how convoluted it is to achieve the few simple scenarios she wants
> >>> (html and pdf) and also potentially quite costly.
> >>>
> >>> I believe this is one of the most common scenarios we will find for
> >>> the tech author audience and the answer that Scott gave is good. It
> >>> does highlight, however, that this is not a simple thing to achieve
> >>> by any stretch.
> >>> I believe where we can make the biggest impression is to put a more
> >>> positive swing on this kind of answer, and as we discussed last
> >>> week, providing some sort of checklist against which to evaluate
> >>> tools as well as identifying what tools are out there. (preaching to
> >>> the choir, I know)
> >>>
> >>> I have added the email text for reference. (I am assuming this is
> >>> OK, as long as we don’t distribute further)
> >>>
> >>> Cheers, Briana
> >>>
> >>>
> >>> Hi Vickie...
> >>>
> >>> If you're to be authoring content in DITA you'll need an editor that
> >>> supports DITA. Some popular options are .. Oxygen, FrameMaker (with
> >>> DITA-FMx), XMetaL, Arbortext, XXE (and others ..
> >>> http://www.ditanews.com/tools/desktop_editors/). One of the nice
> >>> things about DITA is that you don't really need to decide on a
> >>> single authoring tool .. as long as it round-trips valid DITA it
> >>> won't matter. You can have people using XMetaL and others using
> >>> FrameMaker, and all of the files will integrate nicely with your
> >>> publishing process. As far as I know Author-IT will export DITA, but
> >>> I wouldn't consider it a DITA authoring tool because it can't open
> >>> DITA files (without a complicated import process).
> >>>
> >>> You can generate online output through the DITA Open Toolkit, and
> >>> after a bit of tweaking and effort, you'll probably have something
> >>> that works reasonably well. If you want something a bit more WYSIWYG
> >>> for building your HTML-based output, you might consider RoboHelp
> >>> (which now imports DITA files, but is not a DITA authoring tool) or
> >>> Quadralay's ePublisher.
> >>> Flare is poised to have DITA support, but as far as I know it's not
> >>> there yet.
> >>>
> >>> For PDF output, you can use the Open Toolkit, but in order to get
> >>> anything reasonably useful will require hiring an FO developer and
> >>> probably spending a substantial amount of time and money. FrameMaker
> >>> gives you nice looking PDF output right out of the box, and
> >>> modifying a FM template is infinitely easier than FO development.
> >>> Even if you don't use FM as your DITA authoring tool, you might
> >>> consider using it for PDF output.
> >>>
> >>> Cheers,
> >>>
> >>> ...scott
> >>>
> >>> Scott Prentice
> >>> Leximation, Inc.
> >>> www.leximation.com
> >>>
> >>>
> >>> Vickie Hearne wrote:
> >>> > Hello all:
> >>> >
> >>> > I'm working with a software company to help them migrate their
> >>> unstructured content from their wiki into a more structured (dita)
> >>> format.
> >>> >
> >>> > We need electronic output (a help system or another nested,
> >>> layered structure that can be delivered via the web), and the
> >>> occasional .pdf manuals for training, etc. While not graphic
> >>> intensive (screen shots mostly), we would like to include a video
> >>> with the task component.
> >>> >
> >>> > I'm reluctant to take them down the Robo path. Even though I have
> >>> a lot of experience with the product, potentially, there could be
> >>> multiple contributors, and, Robo is not the most intuitive for the
> >>> occasional author. I also would the the single-source tool to be
> >>> leveraged for other non-product content, like RFP response, contract
> >>> prep, sows, etc.
> >>> >
> >>> > Any insight suggestions (and warnings!) would be greatly 
> appreciated.
> >>> >
> >>> > Thanks,
> >>> >
> >>> > -v
> >>> >
> >>> > PS: I've used Author-IT in the past, and am comfortable with the
> >>> ease of the UI. Anyone working with the 5.0 version? Thanks again.
> >>>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this mail list, you must leave the OASIS TC that
> > generates this mail. Follow this link to all your TCs in OASIS at:
> > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

Exactly. The discussion of appropriate tools for a given scenario and 
workflow is central to the adoption of DITA. if the "adoption" committee 
can't provide information of this type, who can?

...scott


Sowmya Kannan wrote:
> Agreed. When considering documentation approaches, the OT is what 
> makes DITA attractive - publish to multiple output formats etc.
> The need for a well documented, flexible OT becomes even more crucial 
> in a situation where organizations have Docbook publishing systems in 
> place. The question that we hear from senior management is we already 
> have a tools chain in place, what new tools do we need to develop to 
> support DITA, and what is the LOE?
>
> So there are multiple bridges to be crossed on the way to DITA Adoption.
>
> Sowmya
>
>

Hi,
First, I'm sorry I was unable to attend today's meeting - sounds like it was
an exciting one...
I'd like to agree with Scott on several of his points, but also stress
another point.
That is: the DITA-OT is a "toolkit" - it's not just a tool that is an
alternative to proprietary tools, but it is a framework for stringing
together a toolset to produce any kind of output. Yes, it comes "out of the
box" with ways to get quick prototype output, and you can customize those
"out of the box" transforms, but the toolkit architecture is such that you
can plug-in any type of functionality you want, some of which makes use of
3rd party open-source tools (e.g. the xslt processors, FOP, etc.) or
proprietary tools (e.g. RenderX, Antenna House, etc.)
An example of this: we are currently developing a plug-in to the DITA-OT
that allows you to run Webworks as a separate transtype. (We have several
customers who have asked for this.) Why? Since many individuals and s/w
vendors are integrating the DITA-OT as a common framework, we want to make
it easy to run the Webworks tool under the same unified system. 
Another example: we are also developing a plug-in to run XMLmind to produce
RTF output via FO. Why? To provide proprietary but affordable alternative to
get good quality RTF files other than the dita2rtf transform (which is
largely unsupported) but still stay within the same DITA-OT framework that
is being used to produce other outputs.
Hope this helps...
Joe