Workday Goes DITA with Bluestream XDocs
Bluestream Database Software, a provider of XML storage and content management technologies, announced recently that publisher Workday has finished their implementation of online documentation and application help system leveraging DITA processes and Bluestream’s XDocs XML CMS.
“Workday’s choice of DITA as our documentation schema was the deciding factor in our selection of XDocs” said Stan Swete,VP, Products & Technology, Workday. “Their support of the DITA Open Toolkit processes made our content publishable right out the box. And their configurable transformation pipelines have allowed us to deliver our DITA-based documentation and help content with a Workday look and feel.”
|
SPONSORSHIP |
XDocs is a standards-compliant single-sourcing solution that lets users create, manage and store large volumes of both XML and non-XML content. By working with the XStreamDB Native XML database, XDocs is, the company asserts, an “out-of-the-box DITA-ready” content management system.
Not familiar with DITA? IBM puts it like this, “The Darwin Information Typing Architecture (DITA) is an XML-based, end-to-end architecture for authoring, producing, and delivering technical information. This architecture consists of a set of design principles for creating “information-typed” modules at a topic level and for using that content in delivery modes such as online help and product support portals on the Web. This document is a roadmap for DITA: what it is and how it applies to technical documentation.”
Mark Fletcher, Workday’s Information Architect, said, “Aside from the DITA support, what impresses me about XDocs is the power of the underlying native XML database. We’re taking full advantage of features such as an XPath-sensitive full text search and XQuery-computed resources. Our writers are also seeing productivity benefits through the content reusability that DITA and XDocs provide, and from the WebDAV interface, which allows them to interact with the CMS directly through our XML editing tool.
With the implementation of the Bluestream’s XDocs XML CMS, Workday will benefit from cost savings and will be able to further enhance users’ online experience.
“We are very pleased to be working with such a technology progressive company” commented Jim Tivy, CTO Bluestream. “Workday’s decision to adopt DITA as their content standard puts them among today’s bleeding edge technology organizations.”
Read more breaking news:
- When Technology Fails, Behaviors Get Analyzed
- A Drupal Web CMS Webinar: Everything You Need to Know
- Sitecore Web CMS Recommended to SMBs
- Adobe Max 2008 Winners Announced
- Web Publishing Roll Up: Staying Afloat Online, Barely
- Webinars: Open Source ECM, Web CMS
- Bitrix Goes Social in a Simple Way
- Alfresco Packages CMIS Developer Toolbox
- WordPress 2.7: From Blog Platform to Web CMS
- Alfresco Announces Surf Camp Boston
Comments
Scott--
The "C" in "CMS" stands for content... :) That said, I agree, I've spent a chunk of time looking at enterprise CMS products, and I can't begin to imagine a competitive product that doens't integrate version control.
However, a quick skim of their product suggests that, remarkably, they left that out... Embarassing, really. Really reduces XDocs to the level of a toy...
Add a Comment
Get a New Job!
(View All
|
Feed
| Post a Job)
- Lead UI/User Experience Designer at edufire
- Senior Web Developer at Trapeze
- ActionScript Engineer (ActionScript Assassin) at Meebo
- Software Chameleon at BorderStylo
- Web UI Developer at GETCO
- Copywriter at Navajo Company Inc.
- Principal Technical Architect at TandemSEVEN
- EMC/Documentum content management Architect at Urpan Technologies, Inc.


Newsletter:
Email a Friend
Digg It


Does Bluestream’s XDocs XML CMS now have version control? In the past, they've touted this tool as a CMS. Without simple things like version control, I'd question whether BlueStream should label their product a CMS. After all, the "C" in CMS stands for control. If you don't even have version control, how can you call a product a CMS?
I'd like to see an article on CMSWire about what makes a CMS a CMS. Now that would be really useful.
Cheers,
Scott Abel
Posted by: Scott Abel on February 8, 2007 6:17 AMTheContentWrangler.com