I always took footnotes for granted. You need them as you’re writing, you insert an indicator at the right place and it points the reader to an amplification, a citation, an off-hand comment, or something — but it’s out of the way, a distraction to the point you’re trying to make.
Some documents don’t need them, but some require them (e.g., scholarly documents, legal documents). In those documents, the footnotes contain such important information that, as Barry Bealer suggests in When footnotes are the content, “the meat [is] in the footnotes.”
The web doesn’t make it easy to represent footnotes. Footnotes on the Web argues that HTML is barely up to the task of presenting footnotes in any effective form.
But if you were to recreate the whole thing from scratch, without static paper as a model, how would you model footnotes?
In a document, a footnote is composed of two pieces of related information. One is the point that you’re trying to make, typically a new point. The other is some pre-existing reference material that presumably supports your point. If it is always the new material that points at the existing, supporting material, then we’re building an information taxonomy bottom up — with the unfortunate property that entering at higher levels will prevent us from seeing lower levels through explicitly-stated links.
To be fair, there are good reasons for connections to be bidirectional. Unidirectional links are forgivable for the paper model, with its inherently temporal life. But the WWW is more malleable, and bidirectional links don’t have to be published at the same time as the first end of the link. In this sense, HTML’s linking mechanism, the ‘<a href=”over_there”>’ construct is fundamentally broken. Google’s founders exploited just this characteristic of the web to build their company on a solution to a problem that needn’t have been.
And people who have lived through the markup revolution from the days of SGML and HyTime know that it shouldn’t have been.
But footnotes still only point bottom up. Fifteen to twenty years on, many of the deeper concepts of the markup revolution are still waiting to flower.
Category: Publishing & media (Page 32 of 53)
Clickability announced the immediate availability of the Clickability Media Solution. The Media Solution provides a centrally managed SaaS content repository that enables large media companies to share digital content across their entire organization and publish it to multiple devices and web channels. Companies of all sizes can leverage the multi-tenant content repository as a hub for innovative content sharing, syndication and distribution strategies. Additional benefits to companies large and small include reduced operational costs through greater efficiencies and the ability to build active social media communities. The solution is designed to maximize the value of every piece of content in a customer’s repository. Content can be tagged and annotated for search and reuse. Assets can be linked and shared across channels and publications. The repository allows companies to create targeted microsites or regional portals that rely on metadata to automatically populate with appropriate content and contextual links. Clickability also offers interactive features, which includes social networking, blogging, video serving, ticketing, personalized calendars, site customization and an on-demand ad server that ties ads to specific sections and pages of a site. http://www.clickability.com
MadCap Software announced its roadmap for supporting the Darwin Information Typing Architecture (DITA) standard. With MadCap, authors will have a complete authoring and publishing suite of tools for creating, managing, translating and publishing DITA content. The products will use MadCap’s XML editor, which provides an graphical user interface for creating featured documentation that hides the XML being generated below. In the first phase of its DITA initiative, MadCap Software will add DITA support to four products: MadCap Flare, MadCap Blaze, MadCap Analyzer for reporting, MadCap Lingo. With MadCap Flare and Blaze, authors will be able to import DITA projects and topics as raw XML content, and using the XML editor, change the style sheets to get the desired look and structure. Authors will then have the option to publish the output as DITA content; print formats, such as Microsoft Word, DOCX and XPS or Adobe FrameMaker, PDF and AIR; and a range of HTML and XHTML online formats MadCap Analyzer will work directly with DITA topics and projects to allow authors to analyze and report on the content. Similarly, MadCap Lingo will import data directly from DITA topics and projects, so that it can be translated. The translated material can be published as DITA content or exported to a Flare or Blaze project. In the second phase, MadCap will enable authors to natively create and edit DITA topics in Flare and Blaze, as well as MadCap X-Edit, MadCap’s software family for creating short documents, contributing content to other documents, and reviewing content. Like Flare and Blaze, X-Edit will also support the ability to import and publish DITA information. In the third phase, MadCap will add DITA support to its forthcoming MadCap Team Server. This will make it possible to manage and share DITA content across teams and projects, as well as schedule DITA publishing. http://www.madcapsoftware.com
By David Lipsey, Managing Director, Entertainment & Media, FTI
Can anyone deliver customized content to its customers – in print, on the Web in rich applications, in social networking or to wireless media? To make matters more challenging, what if your customers are two-to-five year olds? Well, Sesame Workshop recently had to address this test to keep its brand relevant to precocious preschoolers. In fact, this non-profit organization behind Sesame Street took the bold view that multi-channel publishing is the future of the Workshop, and recognized that online will become its primary channel of distribution down the line. At the upcoming Gilbane Boston Conference (link to information on session), I will moderate a panel of multi-channel publishing experts, including the VP charged with Sesame Workshop’s internet initiative. We will provide you with the latest in content delivery, opportunities to serve more users and more applications, and insights to show that yes, almost anyone can do it. Please join me, Joe Bachana from DPCI (an industry leader in his own right) and the ever-innovative O’Reilly Press for a didactic and enlightening discussion that will get you mulling over ideas for enhancing your brand experience for customers.
So a number of client projects recently have me looking for certain info and tools. If you have some thoughts about any of these, please do get in touch or post a comment here.
In no particular order:
- Does anyone have experience with the XSL-FO stylesheets that have been created for previewing content encoded with the NLM article DTD? In addition, has anyone extended the stylesheets to work with the book tag set?
- In a related note, has anyone tried the Word 2007 add-in for the NLM DTD? Experiences? Good, bad, or indifferent? I also wonder if anyone has tried extending it to reflect customizations to the DTD/schema?
- Finally, I am looking to talk to users who have created DITA content with Microsoft Word, either one of the commercial add-ins like Content Mapper or a custom add-in.
Publisher’s Weekly is reporting that a settlement might be at hand.
Nearly three years after publishers filed a lawsuit against Google over its controversial program to scan books from library shelves, a settlement could be near. Although rumors of a settlement have flared up and died down intermittently over the years, sources this week confirmed for Library Journal and Publishers Weekly that talk of a final agreement has indeed heated up, and one publishing insider with knowledge of the talks confirmed that a settlement announcement was “imminent.” Asked if the broad strokes of a final settlement with Google had indeed been reached, Association of American Publishers spokesperson Judith Platt suggested that the rumor mill was once again starting its run up to Frankfurt, which begins October 15. A Google spokesperson said the company does not comment on speculation.
If Google does stay in the scanning business, I wish someone would teach them how to scan physical copies of books to anything approach industry standard quality.
UPDATE (10/28/08): Wired News has a brief report on the settlement. The notion of a Book Rights Registry caught my eye. The Google Books website has a brief explanation of the settlement.
RSuite CMS now offers a CS3 Connector for InCopy users. The integration with Adobe’s CS3 enables InCopy users the ability to browse and open XML or InCopy documents in RSuite directly from the Adobe application. The RSuite CS3 Connector allows users to manage their content as XML within RSuite and to create a transformation to and from their own XML content model to the native XML file format of InCopy. This will help publishers who want to manage their content as XML throughout its life-cycle but also want to use the Adobe tools in their editorial and production process. Users can also store and develop workflows around InCopy and InDesign documents in RSuite. http://www.rsuitecms.com
MadCap Software announced the launch of MadCap Capture 3.0. Capture is MadCap’s screen capture and graphics editing software, which is designed specifically to address the needs of documentation professionals. With version 3.0, Capture adds several enhancements to provide image integration, quality, and control, including: Image text single-sourcing – Capture 3.0 expands on the integration with MadCap Flare, MadCap’s authoring software, which enables single-sourcing of content across the two applications. Now authors can enter a text description (screen tip or alternative text) for an image in a centralized location, so every time the image appears in a Flare project, the text automatically appears with it; System clipboard integration – Authors can now automatically save and insert screen captures into any application with direct system clipboard integration. Optimized size configuration for print and online publishing – Capture 3.0 allows authors to establish separate height and width settings for print and online publishing; Delayed capture – Capture 3.0 provides a time delay feature that lets you automatically capture an image after a certain number of seconds. This makes it possible to take screenshots showing elements such as drop-down menus and tool tips; Image blurring and magnification – In addition to being able to blur images around shapes, authors can now blur the area within shapes; Enhanced XPS support – Capture 3.0 provides the ability to save and load images in Microsoft XPS, providing a crisp image that does not become pixilated when someone zooms in. http://www.madcapsoftware.com/
Subscribe to the Gilbane Advisor
