DITA/docbook vs your own schema

[Yves Barbion]

Hi Rebecca

I don't think any content maps perfectly to DITA, which is logical. But
then again, you can specialize DITA to make it match your content. Some
will even say that DITA must be specialized.

Others have already given you some good arguments in favor of DITA or
DocBook. With DITA, you will also get:

   - Excellent free support from clever people in various DITA user groups:
   Yahoo dita-users, DITA Awareness Group on LinkedIn...
   - Books: http://www.ditawriter.com/dita-books/
   - Conferences
   - DITA-aware tools (editors, CMSs) but also DITA-aware technical writers

I've been involved in projects in which customers chose to develop their
own schema. It has taken them months to develop the schemas, integrate them
in the tools and set up the publication process. With DITA, you can be up
and running in just a couple of days (or weeks).

If you develop your own schema, you will also have to document it. You get
this for free with DITA:

http://docs.oasis-open.org/dita/v1.2/spec/DITA1.2-spec.html


This may help too (source:
http://www.scriptorium.com/2009/12/assessing-dita-as-a-foundation-for-xml-implementation/):

Implementing DITA versus implementing custom XML architecture

With a basic understanding of DITA, it’s time to tackle the $64,000
question: Should you use DITA for your content? First, you need to
determine whether XML in general makes sense for your content requirements.
If you decide that XML is appropriate, take a look at DITA. The following
table outlines a few possible scenarios.

*Scenario*

*Recommendation*

Content must conform to a specific standard, such as S1000D (manufacturing
and aerospace), SPL (Structured Product Labeling, pharmaceuticals), or
NewsML (newspaper articles).

Use the required standard.

DITA, out of the box, meets all requirements.

Use DITA.

A customer or business partner requires you to deliver DITA content.

Use DITA.

Content contains lengthy narratives that cannot be broken into reasonable
modular chunks.

DITA is probably not a good fit. Consider a different standard, perhaps
DocBook, or build your own.

Single sourcing is a requirement. No existing content. Can be flexible with
markup requirements in exchange for quicker implementation.

DITA is a good fit.

DITA is not an exact match; customization would be required.

Compare the cost of DITA customization to the cost of custom implementation.

Markup requirements are industry-specific, complex, and strict.

Look for an existing standard in your industry or build a custom structure.




Kind regards



-- 
Yves Barbion
www.scripto.nu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frameusers.com/pipermail/framers-frameusers.com/attachments/20130709/3c447a35/attachment.htm>