http://tc.eserver.org/authors/O'Keefe,_Sarah_S A bibliography of works by O'Keefe, Sarah S in the field of technical communication. en-us Copyright (c) 2005-08 by the EServer. All rights reserved. tclib-editorial@eserver.org (TC Library Editorial Board) webmaster@eserver.org (Geoffrey Sauer) http://tc.eserver.org/images/newlogo.gif http://tc.eserver.org/dir/O'Keefe,_Sarah_S http://tc.eserver.org/35767.html http://tc.eserver.org/35767.html What is Flash? It's a vector-based format for moving images. Adobe technology via Macromedia Proprietary FLA for Flash development files. SWF for compressed files. http://tc.eserver.org/35316.html http://tc.eserver.org/35316.html The mission of STC is to “advance the arts and sciences of technical communication.” How does this help you, the member? I have been a freelancer/business owner for the vast majority of my career (so far). Let me say a few things about STC’s value proposition for mercenaries like me. http://tc.eserver.org/35218.html http://tc.eserver.org/35218.html Formatting automation removes cost from the process of creating and delivering content. For technical documents that change often and are perhaps delivered in multiple languages, it removes a lot of cost. Essentially, we can produce documents inexpensively and give more people access to them as a direct result of lower cost, or we can climb on our typographic high horse and whine about word spacing. I’m with the noisome fanboys. http://tc.eserver.org/34710.html http://tc.eserver.org/34710.html The authoring tool does matter. Writers are focusing on the wrong set of issues (leading, kerning, print formatting), none of which is actually relevant for the output. http://tc.eserver.org/34695.html http://tc.eserver.org/34695.html In the absence of safety concerns, I think that accuracy must win. Thus, as the information curator, you have a responsibility to correct inaccurate information. If the inaccuracy is truly dangerous, you may need to edit the post directly. Make sure that you disclosure what you've done with brackets. http://tc.eserver.org/34627.html http://tc.eserver.org/34627.html As you may have heard, STC is in a financial crisis. According to the board of directors meeting minutes from May 5, 2009, STC must retain membership "for the next year or STC will be out of business in two years." I believe that STC needs to make some significant changes in the following areas. http://tc.eserver.org/34135.html http://tc.eserver.org/34135.html O’Keefe gives detailed information on two technology standards that may be used in multilingual workflows: XSL and XLIFF. http://tc.eserver.org/33746.html http://tc.eserver.org/33746.html A blog about publishing and technical communications. http://tc.eserver.org/33649.html http://tc.eserver.org/33649.html Have you been waiting for the right time to switch to XML publishing? O’Keefe illustrates that with the advent of Web 2.0, the time is now. http://tc.eserver.org/33400.html http://tc.eserver.org/33400.html Compares Gutenberg's invention of the movable type to the creation of XML. But where movable type changed the “economics of a mechanical process,” XML changed the “economics of content authoring, formatting, and customization.” http://tc.eserver.org/32797.html http://tc.eserver.org/32797.html Many people see DITA architecture as a shortcut to avoiding content modeling. O'Keefe warns readers against this mistake. http://tc.eserver.org/32227.html http://tc.eserver.org/32227.html In the past few years, we have implemented both DITA-based and custom XML solutions for our customers. Given the right set of circumstances, DITA provides an excellent foundation for structured content. But I seem to be in significant disagreement with DITA advocates about how often the "right set of circumstances" is present. http://tc.eserver.org/32179.html http://tc.eserver.org/32179.html The move toward XML-based authoring in technical publications is a classic paradigm shift. It requires content creators to change their writing process and learn new concepts. http://tc.eserver.org/31742.html http://tc.eserver.org/31742.html Most people are risk-averse, and profound changes such as the move to structured authoring require new skills and workflows. To ensure a successful transition, XML implementers need to assess their team members, identify allies, and build their implementation strategy around the staff members who embrace change. http://tc.eserver.org/31579.html http://tc.eserver.org/31579.html The rise of Web 2.0 technology provides a platform for user-generated content. Publishing is no longer restricted to a few technical writers—any user can now contribute information. But the information coming from users tends to be highly specific, whereas technical documentation is comprehensive but less specific. The two types of information can coexist and improve the overall user experience. User-generated content also offers an opportunity for technical writers to participate as “curators”—by evaluating and organizing the information provided by end users. http://tc.eserver.org/31580.html http://tc.eserver.org/31580.html Sorry, guys, but what you're describing is "single sourcing" and it's been around for a while. And I don't think redefining "dynamic publishing" is going to work, either, because that term already means something. http://tc.eserver.org/31583.html http://tc.eserver.org/31583.html Free and cheap tools (blogging software, cheap digital cameras) have made "many-to-many" communication possible. This is sometimes called the "rise of the creative class." People are shifting from being consumers to creators. http://tc.eserver.org/31584.html http://tc.eserver.org/31584.html In this podcast, Sarah O’Keefe talks about XSL, Flash, and live blogging. XSL (extensible stylesheet language) is a programming language that transforms XML content into a specific format, such as HTML. She explains what you can do with XSL, why it’s unique, and how the output is created. http://tc.eserver.org/30784.html http://tc.eserver.org/30784.html How do you convert your application-neutral, vendor-neutral, unformatted XML content into paginated content (such as PDF) or HTML? O'Keefe introduces one solution: the Extensible Stylesheet Language, a programming language for processing XML. http://tc.eserver.org/30122.html http://tc.eserver.org/30122.html XML-based publishing challenges authors to convert from the familiar desktop-publishing routine to new tools. This article explains what you should consider when deciding whether to implement XML. http://tc.eserver.org/28263.html http://tc.eserver.org/28263.html Content reuse enables technical communicators to create multiple deliverables from a single set of source documents. A key component of reuse is identifying which information belongs in which deliverable. Some customization is feasible with build tags (RoboHelp), conditional text (FrameMaker), topic reuse (FrameMaker and AuthorIT), and similar features. http://tc.eserver.org/28185.html http://tc.eserver.org/28185.html Implementing structured authoring with XML allows organizations to create better content. The addition of hierarchy and metadata to content improves reuse and content management. These benefits, however, must be weighed against the time and money required to implement a structured authoring approach. The business case is compelling for larger writing organizations; they will be the first to adopt structured authoring. Over time, improvements in available tools will reduce the cost of implementing structured authoring and make it affordable for smaller organizations. http://tc.eserver.org/28186.html http://tc.eserver.org/28186.html In a structured authoring environment, authors create documents by assembling elements and text in an order permitted by the structure definition document. You might think of structured authoring as being similar to template-based authoring with a strict template. Authors do not assign formatting; the formatting is automatically assigned based on the structure of the document. Formatting may differ for different output media. http://tc.eserver.org/28177.html http://tc.eserver.org/28177.html Not every content-creation group will benefit from structured authoring and XML. Sometimes, the expense of implementation outweighs the benefits realized, especially in smaller groups with less total page count. http://tc.eserver.org/27647.html http://tc.eserver.org/27647.html To create a specific deliverable, you collect all of the relevant topics and wrap information around them. A printed book, for instance, contains topics grouped into chapters along with front and back matter. http://tc.eserver.org/20726.html http://tc.eserver.org/20726.html WebWorks Publisher from Quadralay lets you develop online help from FrameMaker files without dealing with the inefficiencies associated with help authoring tools (HATs). No longer do you have to convert the FrameMaker files to RTF for use in a HAT—and consequently lose all the formatting, which you must rebuild. You also do not have to maintain two sets of files. http://tc.eserver.org/19468.html http://tc.eserver.org/19468.html Implementing structured authoring with XML allows organizations to create better content. The addition of hierarchy and metadata to content improves reuse and content management. These benefits, however, must be weighed against the time and money required to implement a structured authoring approach. The business case is compelling for larger writing organizations; they will be the first to adopt structured authoring. Over time, improvements in available tools will reduce the cost of implementing structured authoring and make it affordable for smaller organizations.