Curated for content, computing, and digital experience professionals

Category: Publishing & media (Page 36 of 52)

JustSystems Announces DITA Maturity Model Co-Authored with IBM

JustSystems, Inc. announced the availability of the “DITA Maturity Model,” which was co-authored with IBM and defines a graduated, step-by-step methodology for implementing Darwin Information Typing Architecture (DITA). One of DITA’s features is its support for incremental adoption. Users can start with DITA using a subset of its capabilities, and then add investment over time as their content strategy evolves and expands to cover more requirements and content areas. However, this continuum of adoption has also resulted in confusion, as communities at different stages of adoption claim radically different numbers for cost of migration and return on investment.

The DITA Maturity Model addresses this confusion by dividing DITA adoption into six levels, each with its own required investment and associated return on investment. Users can assess their own capabilities and goals relative to the model and choose the initial adoption level appropriate for their needs and schedule. The six levels of DITA adoption include:

Level 1: Topics – The most minimum DITA adoption requires the migration of the current XML content sources;

Level 2: Scalable Reuse – The major activity at this level is to break down the content in topics that are stored as individual files and use DITA maps to collect and organize the content into reusable units for assembly into specific deliverables;

Level 3: Specialization and Customization – Now, users expand the information architecture to be a full content model, which explicitly defines the different types of content required to meet different author and audience needs and specify how to meet these needs using structured, typed content;

Level 4: Automation and Integration – Once content is specialized, users can leverage their investments in semantics with automation of key processes and begin tying content together even across different specializations or authoring disciplines;

Level 5: Semantic Bandwidth – As DITA diversifies to occupy more roles within an organization, a cross-application, cross-silo solution that shares DITA as a common semantic currency lets groups use the toolset most appropriate for their content authoring and management needs;

Level 6: Universal Semantic Ecosystem – As DITA provides for scalable semantic bandwidth across content silos and applications, a new kind of semantic ecosystem emerges: Semantics that can move with content across old boundaries, wrap unstructured content, and provide validated integration with semi-structured content and managed data sources. http://www.ibm.com, http://na.justsystems.com

ADAM Software Offers XPS-functionality

ADAM Software announced full breadth XPS-functionality. XPS stands for XML Paper Specification. ADAM’s provider model allows third party developers to co-engineer on emerging opportunities. As for XPS, ADAM software joined forces with the Belgian company NiXPS to build an XPS-engine for ADAM. The ‘NiXPS Library v2.0’ widens the scope in which ADAM can handle data. Thumbnails of XPS files are shown in ADAM, the previewing of XPS files starts here. Metadata can be read by ADAM when importing. ADAM handles a conversion of XPS files to Adobe PDF. http://www.adam.be, http://www.nixps.com

Welcome to XML Technologies and Content Strategies

As Frank noted in our main blog and in the related press release, this blog is part of our launch this week of a new practice focused on the technologies, strategies, and best practices associated with using XML in content management. With this focus on XML, the new practice is broad–XML is fundamental to so many aspects of content management. Yet the focus on XML also compels us to look at content management through a certain lens. This begins with the vendor offerings, where nearly every platform, product, and tool has to meet anywhere from a few to myriad XML-related requirements. As XML and its related standards have evolved and matured, evaluating this support has become a more complex and considered task. The more complex and feature-rich the offering, the more difficult the task of evaluating its support.

And indeed, the offerings are becoming more complex, especially among platform vendors like Microsoft, IBM, and Oracle. Looking at SharePoint means evaluating it as a content management platform, but also looking specifically at how it supports technologies like XML forms interfaces, XML data and content feeds, and integration with the XML schemas underlying Microsoft Word and Excel. It also means looking at SOA interfaces and XML integration of Web Parts,and considering how developers and data analysts might want to utilize XML schema and XSLT in SharePoint application development. Depending on your requirements and applications, there could be a great deal more functionality for you to evaluate and explore. And that is just one platform.

But understanding the vendor–and open source–offerings is only one piece of the XML content management puzzle. Just as important as choosing the right tools are the strategic issues in planning for and later deploying these offerings. Organizations often don’t spend enough time asking and answering the biggest and most important questions. What goals do they have for the technology? Cost savings? Revenue growth? Accelerated time to market? The ability to work globally? These general business requirements need to then be translated into more specific requirements, and only then do these requirements begin to point to specific technologies. If XML is part of the potential solution, organizations need to look at what standards might be a fit. If you produce product support content, perhaps DITA is a fit for you. If you are a publisher, you might look at XML-based metadata standards like XMP or PRISM.

Finally, XML doesn’t exist in a content management vacuum, removed from the larger technology infrastructure that organizations have put in place. The platforms and tools must integrate well with technologies inside and outside the firewall; this is especially true as more software development is happening in the cloud and organizations are more readily embracing Software as a Service. One thing we have learned over the years is that XML is fundamental to two critical aspects of content management—for the encoding and management of the content itself (including the related metadata) and for the integration of the many component and related technologies that comprise and are related to content management. Lauren Wood wrote about this in 2002, David Guenette and I revisited it a year later, and the theme recurs in numerous Gilbane writings. The ubiquitous nature of XML makes the need for strategies and best practices more acute, and also points to the need to bring together the various stakeholders–notably the business people who have the content management requirements and the technologists who can help make the technology adoptions successful. Projects have the best chance of succeeding when these stakeholders are brought together to reach consensus first on business and technical requirements, and, later, to reach consensus on technology and approach.

As Frank noted, this is “New/Old” news for all of us involved with the new practice. I first discussed SGML with Frank in 1987 when I was at Mitre and responsible for a project to bring new technology to bear on creating specifications for government projects. Frank had recently launched his technology practice, Publishing Technology Management. Leonor was a client at Factory Mutual when I worked for Xyvision (now XyEnterprise) in the early 1990s. And I probably first met Mary at a GCA (now IDEAlliance) event during my Xyvision days and when she worked for a competitor, Datalogics. We are, in the polite vernacular of the day, seasoned professionals.

So welcome to the new blog. Watch this space for more details as we announce some of the offerings and initiatives. I plan to blog actively here, so please add the RSS feed if you prefer to digest your material that way. If you have ideas or suggestions, don’t hesitate to post here or contact me or any of the other analysts directly. We look forward to the interaction!

MadCap Software Debuts MadCap Lingo & MadCap Analyzer

MadCap Software announced MadCap Lingo, an XML-based, integrated translation memory system and authoring tool, aimed at eliminating the need for file transfers in order to complete translation. Document components, such as tables of content, topics, index keywords, concepts, glossaries, and variables all remain intact throughout the translation and localization process, so there is never a need to recreate them. MadCap Lingo also is integrated with MadCap Flare and MadCap Blaze, and it is Unicode enabled to help documentation professionals deliver a consistent user experience in print, online, and in any language. MadCap Lingo is being announced in conjunction with the new MadCap Analyzer, software that proactively recommends documentation content and design improvements. MadCap Lingo works with MadCap Flare, the company’s native-XML authoring product, and MadCap Blaze, the native-XML tool for publishing long print documents, which will be generally available in early 2008. A user creates a MadCap Lingo project to access the source content in a Flare or Blaze project via a shared file structure. Working through Lingo’s interface, the user accesses and translates the content. Because the content never actually leaves the structure of the original Flare or Blaze project, all the content and formatting is preserved in the translated version. Once a project is translated, it is opened in either Flare or Blaze, which generates the output and facilitates publishing. At the front end of the process, Flare and Blaze can import a range of document types to create the source content. Following translation, the products provide single-source delivery to multiple formats online and off, including the Internet, intranets, CDs, and print. MadCap Lingo is available and is priced at $2,199 per license, but is available at an introductory price of $899 for a limited time. MadCap Lingo also is available on a subscription basis for $649 per year. Fees for support start at $449 per year. http://www.madcapsoftware.com/

SiberSafe Hosted XML CMS Service Now Available On-Demand

SiberLogic announced SiberSafe On-Demand, a monthly subscription approach to XML content management for technical documentation teams who are looking for significant efficiency gains in producing long-lived, complex, evolving content. SiberSafe On-Demand delivers full SiberSafe functionality as an ASP service in a secure data center. Each team has full access/administrative rights to their server for system administration and configuration. SiberSafe On-Demand also includes daily content backups and SiberLogic’s technical support service. SiberSafe On-Demand “out of the box” configuration offers your choice of DTD – DITA, DocBook, or MIL-STD 2361 – with sample templates and stylesheets. Also included are SiberSafe Communicator (our XML authoring tool) and our integrated publishing tool. Alternatively, you can continue to use your own editor, such as XMetaL, Epic, or FrameMaker, or your own publishing tools. SiberSafe On-Demand costs only $799 per month for the first pair of users (one author and one reviewer) and as little as $275 per user monthly for 10+ users. There are no additional upfront costs. Anyone who signs up for SiberSafe On-Demand before the end of January 2008 will receive access for one additional author free of charge for the first year. http://www.siberlogic.com/

In.vision and Trisoft Announce Partnership to Boost Technical Publishing

In.vision Research and Trisoft have announced a partnership to integrate their products to meet the needs of content management and publishing for a variety of industries including telecom, high-tech, software, mechanical equipment and automotive. The In.vision and Trisoft partnership will use In.vision’s Xpress Author for Microsoft Word add-in to allow non-technical writers to create XML content in Word. When the non-technical writer saves the document into the Trisoft InfoShare Content Management System, technical writers will be able to incorporate the content into their documents with ease, and continue with the various review, translation, and publishing processes that InfoShare provides. http://www.tri-soft.com, http://www.invisionresearch.com

eZ Systems Launches Mac OS X Server and iPhone Support for eZ Publish

eZ Systems announced support for eZ Publish running on Mac OS X Server v10.5 Leopard. In addition, eZ showed eZ Flow, a new extension for eZ Publish designed for media companies who need to build complex page layouts and pre-plan publication schedules to ensure a constant flow of rich content. Among other features, eZ Flow supports delivery of content to Apple iPhones. With support for the Mac OS X Server (which recently attained UNIX 03 certification), eZ Publish enhances the platform by providing an Open Source Enterprise Content Management System that enables organizations to create websites, intranets and extranets. Because content presentation is based on a template system, eZ Publish (and eZ Flow) can serve tailored content to mobile devices by using a template tuned for the devices’ display. For example, a template customized for Apple iPhones tunes the display of content to the iPhone display size and iPhone-specific user interface elements. http://ez.no/ezpublish

EBook Readers, Unite!

With the advent of Kindle, from Amazon, a second dedicated ebook reader device has made the news, not counting the press and high hypes of the many preceding, deceasing ebook device contenders. There is a lot to like about Kindle on the face of it: like the Sony reader, Kindle uses the very effective E-Ink display, and few argue that the display lacks sufficient print page fidelity. But, so what? If you want good black type on white, readable only when illuminated by lamp or sun, the book itself has proved a pretty good format.

But, of course, Kindle promises much more, including all the old bromides about ebooketry like storing many titles, interactive index capabilities, bookmarking, etc., but there are some new tricks in Kindle that may indeed spark new interest. The best one is that through cellphone data network connectivity, the user may order new titles anywhere and anytime the cell network works (which, admittedly, is a whole lot more where and when than Wi-Fi, unless one happens never to leave the office or home network, or lives in a Starbucks). Hats off to Amazon for this innovation. Other features include some sort of Web browsing, an online ebook ordering system that should be second nature to Amazon, and, kinda, MP3 playability. But many of the newest features Kindle offers are more disappointment than delivery, and these shortfalls have everything to do with one of the biggest conceptual problems of dedicated ebook readers in the real world: The additional device conundrum.

While readability is a key requirement for an ebook device (and the lack of which helps explains why PDAs have proved to be a poor ebook market factor), the human species has neither physically evolved more hands, nor has human culture fashioned more pockets. Like 99% of people, I have enough trouble making sure that I have my keys with me when they might be needed, and when you throw in the now essential cellphone, it can seem like half of each day is spent performing the mime of pocket swatting. (Thank god I long ago gave up smoking, and now no longer have to also pat myself down to see about matches or the pack.) People sherpa the minimum, and the idea of having a cell phone, and a PDA, and an MP3 player, and a laptop, and an ebook reader doesn’t require a lot of imagining to be seen as unattractive. And that’s before you figure than anyone hitting their forties also has to carry reading glasses, not to mention for some of any age inhalers or secure ID cards, and for many, breath mints, handkerchiefs, gloves or mittens, and the wallet or two. I’m sure that this is all good training if you’re going to be a combat grunt, but for daily living our current list of the things we carry is a burden.

That’s what drives me crazy about Kindle. It has a built-in cell phone, but there’s no option to use it for anything else other than ordering a book. It has the ICs and jacks for playing MP3 files, but no playlist management, nor—absurdly enough, considering that Amazon is set up to sell things like music—any iTunes-like music downloading. The critical assessment of the Web browsing capability of Kindle is not fully formed, but there’s already plenty of complaint about the Kindle’s shortcomings there. Even one of the strong features of Kindle—E-ink—comes with its own drawback; while promotional copy claims that it is just like reading a page, that also means that you can’t read without a light, so better add a booklight to your pack, even as you’re carrying an electrically powered “book.” And with Kindle’s fundamental lack of support of PDF files—without question the single most widespread format for ebooks—you have to wonder, “What were they thinking?!”

Yes, I’d love to have an ebook device with seamless book ordering. But gosh darn it, it better handle phone calls and calendars, text entry and music playlists, and a good enough Web browser before I’d consider it. Throw in a breath mints storage bin, and I’m sold.

« Older posts Newer posts »

© 2024 The Gilbane Advisor

Theme by Anders NorenUp ↑