DITA/docbook vs your own schema

[Scott Prentice]

All good info.

More reasons to use DITA or DocBook is the availability of off-the-shelf 
authoring, publishing, and file management (CMS) tools. Also, personnel 
support (authoring and development) .. it is much easier to find people 
to work on one of the "standards" than your custom model.

Cheers,

...scott

On 7/8/13 3:50 PM, Alan Houser wrote:
> I gotta generally agree with Matt. Occasionally I run into an 
> information modeling project that I can knock off in an afternoon, but 
> that's pretty rare. Remember that you will not only need to model 
> "block" content (topics, headings, paragraphs, lists, etc.), but also 
> tables, cross-references, images, etc. The latter set can be a bit 
> tricky. Plus, oh, your metadata.
>
> With DITA or DocBook, you also get a publishing framework. Also 
> usually non-trivial to create from scratch, especially if you are 
> publishing to multiple output formats, using filtering, content 
> re-use, etc.
>
> I'll mention with some regret that FrameMaker's DocBook support is 
> pretty poor. I've never figured out why...the "typical" use cases for 
> both (books, PDF) line up very well. It may be a chicken-and-egg 
> issue...I suspect more people would use DocBook if FrameMaker provided 
> better DocBook support.
>
> -Alan
>
> On 7/8/13 6:31 PM, Matt Sullivan wrote:
>> A list of what you'll save using DITA or DocBook rather than creating 
>> your own schema:
>>
>>  1. Time
>>  2. Money
>>
>>
>> (Hey, someone had to say it...)
>>
>>
>> -Matt
>>
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frameusers.com/pipermail/framers-frameusers.com/attachments/20130708/acd4802f/attachment.htm>