Cool Stuff: What's New, What's Cool

I'm still a fan of the functionality that Daisy has implemented. But after having played with it for a bit, it seems to be somewhat less than optimal with respect to error handling and documentation.[Read More]

If you need the collaborative aspects of a Wiki combined with DITA's modular topics and publishing capabilities, then DAISY might just be the system you need--and it's free. DAISY provides WYSIWYG editing for Wiki pages that can be combined to publish books, either in a PDF or as a single HTML page.

 

[Read More]

So what's wrong with using <b>, <i>, and <tt>, anyway? What's so useful about identifying things as menu items, , or filenames? Here's the list of reasons that surfaced at the recent 2008 DITA/CMS Conference. What are your thoughts? [Read More]

The 2008 DITA CMS Conference was informative, educational, and in many cases surprising.  My personal highlights include Daisy, DITAStorm, WebWorks ePublisher, and more...

[Read More]

Notes from the March meeting of the Silicon Valley DITA Interest Group, covering AirHelp and DITA naming conventions.[Read More]

The DITA topic hierarchy that goes into a production system invariably does not match the desired hierarchy of documents coming out of it. And in any mixed-document system where not all docs are in the DITA format, it is invariably the case that xrefs to external documents need to resolve to different locations when documents are published in different contexts. They may require absolute links in some contexts, but be able to use relative links in others--but the relative location may change, depending on context.

This post contains a proposal for production maps. The goal is to control link generation at production time, automatically insert xrefs at authoring time, and automate link management in Content Management Systems when document names and locations change.

Since it touches the DITA standard itself, and all aspects of the tools ecosystem that surrounds that standard, any attempt at implementation will require a significant amount of time. (In the process, the proposal will undoubtedly undergo significant modification, as well.) But at this point, I don't see any alternative that will successfully divorce the output hierarchy--and link resolution--from the input hierarchy.

[Read More]

After writing, Are Structured Docs Really Necessary?, I was asked:
>
> Having written up that interesting discussion, what is your gut feeling at this time?
> If you had to make an authoring recommendation to a group to make life easier
> going forward, what would it be?
>
Well, I found myself going back and forth, as you can tell. That post reflected two weeks of thoughts that kept surfacing after a particularly stimulating discussion. This post is an attempt to come up with an answer.[Read More]

Do we really need structured document formats? In one meeting, every reason we came up with that made them seem necessary, was answered by a convincing counter argument. "Reuse" would seem to be the most important reason. And maybe there are some compelling cases. But  maybe all-out reuse isn't needed. Maybe we really only need a very restricted form that solves those cases.

This post summarizes the arguments we considered. Do they demolish the case for structured documents and reuse in a highly fluid setting like the software industry? Are they wrong in some important respect? Or do they overlook some vitally important point that makes structured document formats irreplacable?

You be the judge. And please let us know. We really want to know.[Read More]

Surprisingly, BlogRoller does not seem to have an archive of past posts. The posts have permalinks, so bookmarks can still find them, and they can be found by searching, but there is no way to browse old posts, once they age out of the system. This index page will be used to rectify that situation until it changes or until I find a Wiki I really like, in which case I'll maintain the index there.[Read More]

My feature wish list for a system that would make it possible to easily interact with the open source community.[Read More]

In both Ruby and DITA, domain specific languages make elegance possible. More importantly, each is producing an ecosystem of domain specific languages (aka "power tools") that is making it possible to do ever more as time goes on.[Read More]

It's a wicked-nice calendar. There are a couple of wishlist items, but basically, this is it.[Read More]

Get the voting advice you need, when you need it, all in one place! The parts are all in place. We just need to bring them together.[Read More]

HTML's "id" attribute works better than named anchors for "Plain Old Semantic HTML" (POSH) web pages, especially for self-referential "purple links", which had their origins in Doug Engelbart's 1968 demo!
[Read More]

The need to rebuilding my Windows XP system turns into an adventure after running out of disk space and deleting one too many things to make room.[Read More]