<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>XML Technologies &amp; Content Strategies</title>
    <link rel="alternate" type="text/html" href="http://gilbane.com/xml/" />
    <link rel="self" type="application/atom+xml" href="http://gilbane.com/xml/atom.xml" />
    <id>tag:gilbane.com,2008-12-28:/xml//42</id>
    <updated>2010-03-03T21:15:45Z</updated>
    <subtitle>Gilbane Group&apos;s XML Technologies &amp; Best Practices Blog Lead Analyst, Bill Trippe</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 4.32-en</generator>

<entry>
    <title>New Gilbane Beacon on High-Volume Data Challenges</title>
    <link rel="alternate" type="text/html" href="http://gilbane.com/xml/2010/03/new-gilbane-beacon-on-high-volume-data-challenges.html" />
    <id>tag:gilbane.com,2010:/xml//42.10415</id>

    <published>2010-03-03T20:48:48Z</published>
    <updated>2010-03-03T21:15:45Z</updated>

    <summary><![CDATA[We've published a new&nbsp;paper on addressing large-scale integration, storage, and access of complex information. As Dale mentions in his&nbsp;entry over on our main blog,&nbsp;the paper frames the discussion in terms of challenges to Open Government initiatives. We note, though, that...]]></summary>
    <author>
        <name>Mary Laplante</name>
        <uri>http://gilbane.com/blog/mt-cp.cgi?__mode=view&amp;blog_id=42&amp;id=3</uri>
    </author>
    
        <category term="Government" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="HTML/XHTML" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="XML" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="beacon" label="Beacon" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="marklogic" label="Mark Logic" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="opengovernment" label="Open Government" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/xml/">
        <![CDATA[<p>We've published a new&nbsp;paper on addressing large-scale integration, storage, and access of complex information. As Dale mentions in <a href="http://gilbane.com/blog/2010/02/paper_on_open_government_data_initiatives_available.html">his&nbsp;entry over on our main blog</a>,&nbsp;the paper frames the discussion in terms of challenges to Open Government initiatives. We note, though, that the exploration of obstacles to effective, efficient processing of high volumes of data and content is relevant&nbsp;across many&nbsp;industries.</p><p>We're cross-posting here on the XML blog because the paper&nbsp;deals wtih XML content and the XML family of standards, including XQuery and XPath.</p><p>The Gilbane Beacon is available as a free <a href="http://gilbane.com/beacons.html">download from&nbsp;Gilbane</a> and from <a href="http://www.marklogic.com/resources/enabling-the-promise-of-open-government.html">Mark Logic</a>, sponsor of the paper.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Focusing on the &quot;Content&quot; in Content Management</title>
    <link rel="alternate" type="text/html" href="http://gilbane.com/xml/2010/01/focusing-on-the-content-in-content-management.html" />
    <id>tag:gilbane.com,2009:/xml//42.9587</id>

    <published>2010-01-04T14:31:20Z</published>
    <updated>2010-01-04T17:20:48Z</updated>

    <summary>The growth in web-centric communication has created a major focus on content management, web content management , component content management, and so on. This interest is driven primarily by increasing demand for rich, interactive, accessible information products delivered via the Web. The focus is not misplaced but may be missing part of the point. To be specific, in our focus on the &quot;management&quot; part of CM, we may be missing the first word in the phrase.... &quot;Content.&quot; </summary>
    <author>
        <name>Barry Schaeffer</name>
        <uri>http://gilbane.com/blog/mt-cp.cgi?__mode=view&amp;blog_id=42&amp;id=145</uri>
    </author>
    
        <category term="Information Architecture" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="contentmanagement" label="content management" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="sourcecontent" label="source content" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="XML" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/xml/">
        <![CDATA[<p>The growth in web-centric communication has created a major focus on content management, web content management , component content management, and so on. This interest is driven primarily by increasing demand for rich, interactive, accessible information products delivered via the Web. The focus is not misplaced but may be missing part of the point. To be specific, in our focus on the &quot;management&quot; part of CM, we may be missing the first word in the phrase.... &quot;Content.&quot;</p><p>It's true that the application of increasing amounts of computer and brain power to the processes associated with preparing and delivering the kind of information demanded by today's users can improve those products. But it does so within limits set by and at costs generated by the content &quot;raw material&quot; it gets from the content providers. In many cases, the content available to web product development processes is so structurally crude that it requries major clean-up and enhancement in order to adequately participate in the classification and delivery process. As the focus on elegant Web delivery increases, barring real changes in the condition of this raw content, the cost of enhancement is likely to grow proportionally, straining the involved organizations' ability to support it.</p><p>The answer may be in an increased focus on the processes and tools used to create the original content. We know that the original creator of most content knows the most about how it should be logically structured and most about the best way to classify it for search and retrieval. Trouble is, in most cases, we provide no means of capturing what the creator knows about his or her intellectual product. Moreover, because many creators have never been able to fully populate the metadata needed to classify and deliver their content, in past eras, professional catalogers were employed to complete this final step. In today's world, however, we have virtually eliminated the cataloger, assuming instead that the prodigious computer power available to us could develop the needed classification and structure from the content itself. That approach can and does work, but it will require better raw material if it is to achieve the level of effectiveness needed to keep the Web from becoming a virtual haystack in which finding the needle is more good luck than good measure. Native XML editors instead of today's visually oriented word processors, spreadsheets, graphics and other media forms with content-specific XML under them, increased use of native XML databases and a host of rich content-centric resources are part of this content evolution.</p><p>Most important, however, may be promulgation of the realization across society that creating content includes more than just making it look good on the screen, and that the creator shares in that responsibility. This won't be an easy or quick process, requiring more likely generations than years, but if we don't begin soon, we may end up with a Web 3 or 4 or 5.0 trying to deliver content that isn't even yet 1.0.</p>]]>
        
    </content>
</entry>

<entry>
    <title>In the end, good search may depend on good source.</title>
    <link rel="alternate" type="text/html" href="http://gilbane.com/xml/2010/01/in-the-end-good-search-may-depend-on-good-source.html" />
    <id>tag:gilbane.com,2010:/xml//42.9571</id>

    <published>2010-01-02T16:35:21Z</published>
    <updated>2010-01-03T14:09:39Z</updated>

    <summary>As the world of search becomes more and more sophisticated (and that process has been underway for decades,) we may be approaching the limits of software&apos;s ability to improve its ability to find what a searcher wants. If that is true, and I suspect that it is, we will finally be forced to follow the trail of crumbs up the content life cycle... to its source.</summary>
    <author>
        <name>Barry Schaeffer</name>
        <uri>http://gilbane.com/blog/mt-cp.cgi?__mode=view&amp;blog_id=42&amp;id=145</uri>
    </author>
    
        <category term="CMS - Content Management Systems" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Enterprise Search" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="XML" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="contentmanagement" label="content management" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="navigation" label="navigation" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="search" label="search" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/xml/">
        <![CDATA[<p>As the world of search becomes more and more sophisticated (and that process has been underway for decades,) we may be approaching the limits of software's ability to improve its ability to find what a searcher wants. If that is true, and I suspect that it is, we will finally be forced to follow the trail of crumbs up the content life cycle... to its source. Indeed, most of the challenges inherent in today's search strategy and products appears to grow from the fact that while we continually increase our demands for intelligence on the back end, we have done little if anything to address the chaos that exists on the front end. You name it, different word processing formats, spreadsheets, HTML tagged text, database delimited files, and so on are all dumped into what we think of as a coherent, easily searchable body of intellectual property. It isn't and isn't likely to become so any time soon unless we address the source. Having spent some time in the library automation world, I can remember the sometimes bitter controversies over having just two major foundations for cataloging source material (Dewey and LC; add a third if you include the NICEM A/V scheme.) Had we known back then that the process of finding intellectual property would devolve into the chaos we now confront, with every search engine and database product essentialy rolling its own approach to rational search, we would have considered ourselves blessed. In the end, it seems, we must begin to see the source material, its physcial formats, its logical organization and its inclusion of rational cataloging and taxonomy elements as the conceptual raw material for its own location. As long as the word processing world teaches that anyone creating anything can make it look like it should in a dozen different ways, ignoring any semblance of finding-aid inclusion, we probably won't have a truly workable ability to find what we want without reworking the content or wading through a haystack of misses to find our desired hits. Unfortunately, the solutions of yesteryear, including after-creation cataloging by a professional cataloger, probably won't work now either, for cost if no other reason. We will be forced to approach the creators of valuable content, asking them for a minimum of preparation for searching their product, and providing the necessary software tools to make that possible. We can't act too soon because, despite the growth of software elegance and raw computer power, this situation will likely get worse as the sheer volume of valuable content grows. Regards, Barry Read more: Enterprise Search Practice Blog:&nbsp; <a href="http://gilbane.com/search_blog/">http://gilbane.com/search_blog/</a></p>]]>
        
    </content>
</entry>

<entry>
    <title>What is Smart Content?</title>
    <link rel="alternate" type="text/html" href="http://gilbane.com/xml/2009/11/what-is-smart-content.html" />
    <id>tag:gilbane.com,2009:/xml//42.10186</id>

    <published>2009-11-24T20:18:33Z</published>
    <updated>2009-11-26T14:13:57Z</updated>

    <summary>When you add meaning to content you make it &quot;smart&quot; enough for computers to do some interesting things. At Gilbane we talk of &quot;Smart Content&quot;, &quot;Structured Content&quot;, and &quot;Unstructured Content&quot;. In this article I share some ideas about these types of content and what they enable and require in terms of processes and systems.</summary>
    <author>
        <name>Dale Waldt</name>
        <uri>http://gilbane.com/blog/mt-cp.cgi?__mode=view&amp;blog_id=42&amp;id=120</uri>
    </author>
    
        <category term="CMS - Content Management Systems" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Information Architecture" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="XML" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="smart_contentstructured_contentunstructured_contentsemantics" label="smart_content structured_content unstructured_content semantics" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/xml/">
        <![CDATA[<p>At Gilbane we talk of &quot;Smart Content,&quot; &quot;Structured Content,&quot; and &quot;Unstructured Content.&quot; We will be discussing these ideas in a seminar entitled &quot;<a href="http://gilbaneboston.com/workshops.html#workshopb">Managing Smart Content</a>&quot; at the <a href="http://gilbaneboston.com/index.html">Gilbane Conference</a> next week in Boston. Below I share some ideas about these types of content and what they enable and require in terms of processes and systems.</p><p>When you add meaning to content you make it &quot;smart&quot; enough for computers to do some interesting things. Organizing, searching, processing, and discovery are greatly improved, which also increases the value of the data. Structured content allows some, but fewer, processes to be automated or simplified, and unstructured content enables very little to be streamlined and requires the most ongoing human intervention.</p><p>Most content is not very smart. In fact, most content is unstructured and usually more difficult to process automatically. Think flat text files, HTML without all the end tags, etc. Unstructured content is more difficult for computers to interpret and understand than structured content due to incompleteness and ambiguity inherent in the content. Unstructured content usually requires humans to decipher the structure and the meaning, or even to apply formatting for display rendering.</p><p>The next level up toward smart content is structured content. This includes wellformed XML documents, content compliant to a schema, or even RDMS databases. Some of the intelligence is included in the content, such as boundaries of element (or field) being clearly demarcated, and element names that mean something to users and systems that consume the information. Automatic processing of structured content includes reorganizing, breaking into components, rendering for print or display, and other processes streamlined by the structured content data models in use.</p><p>Finally, smart content is structured content that also includes the semantic meaning of the information. The semantics can be in a variety of forms such as RDFa attributes applied to structured elements, or even semantically names elements. However it is done, the meaning is available to both humans and computers to process.</p>   <p><a onclick="window.open('http://gilbane.com/xml/assets_c/2009/11/SmartContentValue-159.html','popup','width=698,height=541,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false" href="http://gilbane.com/xml/assets_c/2009/11/SmartContentValue-159.html"><img width="460" height="356" style="margin: 0pt auto 20px; text-align: center; display: block;" class="mt-image-center" alt="SmartContentValue.jpg" src="http://gilbane.com/xml/assets_c/2009/11/SmartContentValue-thumb-460x356-159.jpg" /></a>Smart content enables highly reusable content components and powerful automated dynamic document assembly. Searching can be enhanced with the inclusion of metadata and buried semantics in the content providing more clues as to what the data is about, where it came from, and how it is related to other content.Smart content enables very robust, valuable content ecosystems.</p><p>Deciding which level of rigor is needed for a specific set of content requires understanding the business drivers intended to be met. The more structure and intelligence you add to content, the more complicated and expensive the system development and content creation and management processes may become. More intelligence requires more investment, but may be justified through benefits achieved.</p><p>I think it is useful if the XML and CMS communities use consistent terms when talking about the rigor of their data models and the benefits they hope to achieve with them. Hopefully, these three terms, smart content, structured content, and unstructured content ring true and can be used productively to differentiate content and application types.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Nuts and Bolts Tutorials at The Gilbane Conference</title>
    <link rel="alternate" type="text/html" href="http://gilbane.com/xml/2009/11/nuts-and-bolts-tutorials-at-the-gilbane-conference.html" />
    <id>tag:gilbane.com,2009:/xml//42.10183</id>

    <published>2009-11-23T14:38:36Z</published>
    <updated>2009-11-23T17:22:43Z</updated>

    <summary>In a half-day session preceding the Gilbane conference next week, the Gilbane consulting team will tackle some of the real world challenges inherent in this rapidly changing information world, providing both sign posts for issues likely to come up and &quot;in the trenches&quot; suggestions for how to deal with them.  The goal of the session, scheduled for the afternoon of December 1, is that the attendees leave with a better handle on how to proceed in the quest for better information products and the role &quot;smart content&quot; can and should play.  </summary>
    <author>
        <name>Barry Schaeffer</name>
        <uri>http://gilbane.com/blog/mt-cp.cgi?__mode=view&amp;blog_id=42&amp;id=145</uri>
    </author>
    
    <category term="semanticweb" label="Semantic Web" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="smartcontent" label="smart content" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="strategy" label="strategy" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="structuredcontent" label="structured content" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xbrl" label="XBRL" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="XML" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xmlcommunities" label="XML Communities" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/xml/">
        <![CDATA[<p>In a world that seems increasingly about technology itself, it has become tempting to assume that the questions and challenges of new and better information products is about the technology.&nbsp; While it is true that technology is the key enabler of the new information world we are building, it is also true that the decision making and judgment involved in how that technology is to be organized and deployed is of equal--and not decreasing--importance.&nbsp; Indeed, as the products move toward increasing sophistication and flexibility--<i>smart content </i>you might say--the importance of the human and organizational parts of the information life cycle become even more important.&nbsp;</p><p>It is a truism that you cannot deliver information products you can't create and manage, and with the circle of participants in that creation and management ever widening, we must be sensitive to the limits of the creators.&nbsp; Moreover, while just &quot;getting it up on the web&quot; used to be at least sufficient to justify deployment of information products, today's information consumer has a much more extensive and demanding list of features required before he will accept web-based information.&nbsp; The publisher who forgets&nbsp; or ignores that list is for trouble.</p><p>In <a href="http://gilbaneboston.com/workshops.html#workshopb">a half-day session preceding the Gilbane conference</a> next week, the Gilbance consulting team will tackle some of the real world challenges inherent in this rapidly changing information world, providing both sign posts for issues likely to come up and &quot;in the trenches&quot; suggestions for how to deal with them.&nbsp; The goal of the session, scheduled for the afternoon of December 1, is that the attendees leave with a better handle on how to proceed in the quest for better information products and the role &quot;smart content&quot; should play.&nbsp;</p><p>The presenters, in addition to their expertise&nbsp;in the technology and tools of information,&nbsp;bring a unique resource to their efforts: years of design, implementation and evaluation of real organizations facing real challenges.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Upcoming Workshop: Managing Smart Content: How to Deploy XML Technologies across Your Organization</title>
    <link rel="alternate" type="text/html" href="http://gilbane.com/xml/2009/11/upcoming-workshop-managing-smart-content-how-to-deploy-xml-technologies-across-your-organization.html" />
    <id>tag:gilbane.com,2009:/xml//42.10182</id>

    <published>2009-11-23T13:50:16Z</published>
    <updated>2009-11-23T14:10:13Z</updated>

    <summary><![CDATA[As part of next week's Gilbane Boston Conference, the XML practice will be delivering a pre-conference workshop, &quot;Managing Smart Content: How to Deploy XML Technologies across Your Organization.&quot; The instructors will be&nbsp;Geoff Bock, Dale Waldt, Bill Trippe, Barry Schaeffer and...]]></summary>
    <author>
        <name>Bill Trippe</name>
        <uri>http://gilbane.com/blog/mt-cp.cgi?__mode=view&amp;blog_id=42&amp;id=2</uri>
    </author>
    
        <category term="Authoring" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="DITA - Darwin Information Typing Architecture" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Publishing" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="XBRL" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="XML" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="XQuery" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="XSL-FO, CSS, &amp; Style Sheets" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="XSLT" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="dita" label="DITA" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="smartcontent" label="smart content" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="XML" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/xml/">
        <![CDATA[<p>As part of next week's Gilbane Boston Conference, the XML practice will be delivering a pre-conference workshop, &quot;<a href="http://gilbaneboston.com/workshops.html#workshopb">Managing Smart Content: How to Deploy XML Technologies across Your Organization</a>.&quot; The instructors will be&nbsp;Geoff Bock, Dale Waldt, Bill Trippe, Barry Schaeffer and Neal Hannon--a group of experts that represents decades of technical and management experience on XML initiatives.</p>
<p>A tip of the virtual hat to Senior Analyst Geoff Bock for organizing this.</p>]]>
        <![CDATA[<p>Smart content holds great promise. First with SGML and now with XML, we are marking up content with both formatting and semantic tags, and adding intelligence to electronic information. Using richly tagged XML documents that exploit predefined taxonomies, we are developing innovative applications for single source publishing, pharmaceutical labeling, and financial reporting. By managing content snippets in a granular yet coherent fashion, these applications are revolutionizing our capabilities to meet business needs and customers&rsquo; expectations.</p>
<p>What&rsquo;s working and why? What are the lessons learned from these innovative applications? Does the rapid growth of web-based collaborative environments, together with the wide array of smart content editors, provide the keys to developing other business solutions? There are many promising approaches to tagging content while doing work. Yet we still face an uphill battle to smarten up our content and develop useful applications.</p>
<p>In this workshop, we the five members of the Gilbane practice on XML technologies will share our experiences and provide you with practical strategies for the future. We will address a range of topics, including:</p>
<ul><li>The business drivers for smart content</li><li>Some innovative content management techniques that make authors and editors more productive</li><li>The migration paths from &lsquo;conventional&rsquo; documents to smart content</li><li>How to apply industry-specific taxonomies to tag content for meaning</li><li>The prospects for mash-ups to integrate content from disparate application communities</li></ul>
<p>We will discuss both the rapidly developing technologies available for creating, capturing, organizing, storing, and distributing smart content, as well as the organizational environment required to manage content as business processes. We will identify some of the IT challenges associated with managing information as smart content rather than as structured data, and map strategies to address them. We invite you to join the conversation about how best to exploit the power of XML as the foundation for managing smart content across your organization.</p>]]>
    </content>
</entry>

<entry>
    <title>Once Upon a Time...</title>
    <link rel="alternate" type="text/html" href="http://gilbane.com/xml/2009/11/once-upon-a-time.html" />
    <id>tag:gilbane.com,2009:/xml//42.10161</id>

    <published>2009-11-12T18:39:33Z</published>
    <updated>2009-11-13T15:03:05Z</updated>

    <summary><![CDATA[... there was SVG. People were excited about it. Adobe and others supported it. Pundits saw a whole new graphical web that would leverage SVG heavily. Heck, I even wrote a book about it.&nbsp; Then things got quiet for a...]]></summary>
    <author>
        <name>Bill Trippe</name>
        <uri>http://gilbane.com/blog/mt-cp.cgi?__mode=view&amp;blog_id=42&amp;id=2</uri>
    </author>
    
        <category term="Authoring" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="HTML/XHTML" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Publishing" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="XSL-FO, CSS, &amp; Style Sheets" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="google" label="Google" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="internetexplorer" label="Internet Explorer" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="microsoft" label="Microsoft" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="svg" label="SVG" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/xml/">
        <![CDATA[<p>... there was <a href="http://www.w3.org/Graphics/SVG/">SVG</a>. People <a href="http://www.xml.com/pub/a/2001/11/21/svgtools.html?page=last&amp;x-showcontent=off&amp;x-order=date">were excited</a> about it. Adobe and others <a href="http://www.zdnetasia.com/news/security/0,39044215,39154025,00.htm">supported it</a>. Pundits saw <a href="http://www.eweek.com/c/a/Web-Services-Web-20-and-SOA/Browsers-Get-Ready-for-Graphics-Boost/">a whole new graphical web</a> that would leverage SVG heavily. Heck, I even <a href="http://www.amazon.com/gp/product/0072225297?ie=UTF8&amp;tag=newmillenn-20&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=0072225297">wrote a book</a> about it.&nbsp;</p> <p>Then things got quiet for a long time...</p> <p>However, there are some signs that SVG might be experiencing a bit of a renaissance, if <a href="http://www.svgopen.org/2009/registration.php?section=conference_schedule">the quality of presentations at a recent conference</a> is a strong indication. It's notable that Google hosted the conference and even more notable that&nbsp;<a href="http://www.infoworld.com/d/applications/google-microsoft-support-svg-346">Google is trying to bigfoot Microsoft into supporting SVG in IE</a>, a move that would substantially boost SVG as an option for Web developers.</p> <p>So a question for those out there interested in SVG. Where are some big projects out there? Are there organizations creating large bases of illustrations and other graphical content with SVG? I would love to talk to you and learn about your projects. You can <a href="mailto:bill@gilbane.com?subject=SVG%20Projects">email me</a> or comment below.</p> <p>UPDATE: Brad Neuberg of Google, who is quoted in <a href="http://www.infoworld.com/d/applications/google-microsoft-support-svg-346">the InfoWorld article</a> linked above, sent along a link to a project at Google, <a href="http://code.google.com/p/svgweb/">SVG Web</a>, a JavaScript library that supports SVG on many browsers, including Internet Explorer, Firefox, and Safari. According to the tool's website, using the library plus native SVG support, you can instantly target ~95% of the existing installed web base.</p><p>UPDATE: Ruud Steltenpool, the organizer for <a href="http://www.svgopen.org/2009/">SVG Open 2009</a>, sent a link to <a href="http://svg.startpagina.nl/">an incredibly useful compendium of links</a> to SVG projects, tools, and other resources though he warns it is a little outdated.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Some Excellent Coverage of our Digital Publishing Report</title>
    <link rel="alternate" type="text/html" href="http://gilbane.com/xml/2009/09/some-excellent-coverage-of-our-digital-publishing-report.html" />
    <id>tag:gilbane.com,2009:/xml//42.9964</id>

    <published>2009-09-04T19:11:07Z</published>
    <updated>2009-09-04T19:20:52Z</updated>

    <summary>Over at TeleRead, David Rothman has a really fine writeup discussing our digital publishing report. He summarizes some of our key points about asset management and flexibility, but also raises some interesting related issues about DRM and the risks of...</summary>
    <author>
        <name>Bill Trippe</name>
        <uri>http://gilbane.com/blog/mt-cp.cgi?__mode=view&amp;blog_id=42&amp;id=2</uri>
    </author>
    
        <category term="Publishing" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="XML" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="damsystems" label="DAM systems" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="digitalpublishing" label="digital publishing" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="ebooks" label="eBooks" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/xml/">
        <![CDATA[<p>Over at <i>TeleRead</i>, David Rothman has <a href="http://www.teleread.org/2009/09/04/how-random-house-cengage-and-other-giants-are-using-tech-to-try-to-deal-with-change/">a really fine writeup</a> discussing <a href="http://gilbane.com/Research-Reports.html#beyond-ebook-report">our digital publishing report</a>. He summarizes some of our key points about asset management and flexibility, but also raises some interesting related issues about DRM and the risks of &quot;publishers as mixmasters.&quot;</p><p>My thanks to David for his thoughtful response.</p>]]>
        
    </content>
</entry>

<entry>
    <title>XML&apos;s Role in Digital Archives</title>
    <link rel="alternate" type="text/html" href="http://gilbane.com/xml/2009/08/xmls-role-in-digital-archives.html" />
    <id>tag:gilbane.com,2009:/xml//42.9955</id>

    <published>2009-08-27T21:26:55Z</published>
    <updated>2009-08-27T21:48:13Z</updated>

    <summary><![CDATA[I have a new post over at EMC's Community site, &quot;Preserving Electronic Public Records: Lessons from the Washington State Digital Archives.&quot; This is part of our ongoing series for EMC on the use of ECM and XML in the public...]]></summary>
    <author>
        <name>Bill Trippe</name>
        <uri>http://gilbane.com/blog/mt-cp.cgi?__mode=view&amp;blog_id=42&amp;id=2</uri>
    </author>
    
        <category term="ECM - Enterprise Content Management" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Government" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="XML" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="digitalarchives" label="digital archives" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="emcdocumentum" label="EMC Documentum" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/xml/">
        <![CDATA[<p>I have a new post over at EMC's Community site, &quot;<a href="https://community.emc.com/docs/DOC-4636">Preserving Electronic Public Records: Lessons from the Washington State Digital Archives</a>.&quot; This is part of <a href="https://community.emc.com/docs/DOC-4343">our ongoing series for EMC</a> on the use of ECM and XML in the public sector.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Do you Have an eBook Strategy Yet?</title>
    <link rel="alternate" type="text/html" href="http://gilbane.com/xml/2009/08/do-you-have-an-ebook-strategy-yet.html" />
    <id>tag:gilbane.com,2009:/xml//42.9949</id>

    <published>2009-08-24T19:53:30Z</published>
    <updated>2009-08-24T20:30:11Z</updated>

    <summary><![CDATA[We have been very pleased with the interest in our new report, Digital Platforms and Technologies for Publishers: Implementations Beyond &quot;eBook.&quot; We have had hundreds of downloads already, the vast majority of which are senior people in the publishing industry....]]></summary>
    <author>
        <name>Bill Trippe</name>
        <uri>http://gilbane.com/blog/mt-cp.cgi?__mode=view&amp;blog_id=42&amp;id=2</uri>
    </author>
    
        <category term="Publishing" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="XML" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="amazon" label="Amazon" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="ebooks" label="eBooks" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="electronicpublishing" label="electronic publishing" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="epub" label="epub" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="kindle" label="Kindle" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="sonyreader" label="Sony Reader" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="strategy" label="strategy" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/xml/">
        <![CDATA[<p>We have been very pleased with the interest in our new report, <a href="http://gilbane.com/Research-Reports.html#beyond-ebook-report"><i>Digital Platforms and Technologies for Publishers: Implementations Beyond &quot;eBook.&quot;</i></a> We have had hundreds of downloads already, the vast majority of which are senior people in the publishing industry. This tells us that the timing for the research is good and that interest is strong, and we are thinking about what to do next with this topic.</p>
<p>One idea we have thought about is helping publishers think through their eBook strategy. If our research (and other recent research) is correct, many larger publishers are jumping in with both feet, but some larger publishers, many medium-sized, and perhaps most smaller publishers are staying on the sidelines or testing the waters with pilots and low-cost and low-impact tests with third parties. Perhaps these efforts are part of developing a strategy? Perhaps some of you think the market is too nascent?</p>
<p>An eBook strategy would necessarily be multi-faceted, and would include input from sales, marketing, editorial, production, fulfillment, and others with a stake in the process. It would need to be informed by good market data, and with good understanding of what technology and channel partners can truly offer publishers. It would also need to be pragmatic, balancing the capabilities of your organization with a realistic assessment of the market opportunities you have.</p>
<p>We'd like to gauge interest in this kind of offering through the following simple poll. Just one question, and no requirement to log in or register. If you would like to talk in more detail about this idea, please <a href="mailto:bill@gilbane.com?subject=eBook%20Strategy">email me</a> with any questions.</p>

<script language="JavaScript" src="http://www.micropoll.com/akira/MicroPoll?id=197069"></script><noscript><div><a href="http://www.micropoll.com/akira/mpview/649141-197069">Click Here for Poll</a><a href="http://www.questionpro.com" title="online surveys">Online Survey</a><BR> | <a href="http://www.micropoll.com" title="Website Polls">Website Polls</a><BR> | <a href="http://www.contactpro.com" title="email marketing">Email Marketing</a><BR><BR> | <a href="http://www.ideascale.com/crowdsourcing-software.html" title="crowdsourcing software">Crowdsourcing Software</a><BR><a href="http://www.micropoll.com/akira/MicroPoll?mode=html&id=197069">View MicroPoll</A></div></noscript><!-- END MICROPOLL JAVASCRIPT CODE -->]]>
        
    </content>
</entry>

<entry>
    <title>CMIS Use Cases</title>
    <link rel="alternate" type="text/html" href="http://gilbane.com/xml/2009/08/cmis-use-cases.html" />
    <id>tag:gilbane.com,2009:/xml//42.9941</id>

    <published>2009-08-17T23:18:01Z</published>
    <updated>2009-08-17T23:24:02Z</updated>

    <summary>If you&apos;re like me and have been thinking about CMIS (Content Management Interoperability Services), but need some use cases to help you conceptualize it better, Laurence Hart has put together a very useful presentation. He welcomes comments.As usual, Robin Cover...</summary>
    <author>
        <name>Bill Trippe</name>
        <uri>http://gilbane.com/blog/mt-cp.cgi?__mode=view&amp;blog_id=42&amp;id=2</uri>
    </author>
    
        <category term="CMS - Content Management Systems" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="ECM - Enterprise Content Management" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Software Infrastructure" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="cmis" label="CMIS" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="contentmanagementinteroperabilityservices" label="Content Management Interoperability Services" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/xml/">
        <![CDATA[<p>If you're like me and have been thinking about CMIS (Content Management Interoperability Services), but need some use cases to help you conceptualize it better, Laurence Hart has put together <a href="http://wordofpie.com/2009/08/17/three-fundamental-cmis-use-cases/">a very useful presentation</a>. He welcomes comments.</p><p>As usual, Robin Cover has a great list of resources <a href="http://xml.coverpages.org/cmis.html">here</a>.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Mind the XBRL GAAP</title>
    <link rel="alternate" type="text/html" href="http://gilbane.com/xml/2009/08/mind-the-xbrl-gaap.html" />
    <id>tag:gilbane.com,2009:/xml//42.9928</id>

    <published>2009-08-11T18:25:37Z</published>
    <updated>2009-08-12T15:05:07Z</updated>

    <summary>Recently, XBRL US and the FASB released a new taxonomy reference linkbase to enable referencing to the FASB Codification. The FASB Codification is the electronic data base that contains all US GAAP authoritative literature and was designated as official US...</summary>
    <author>
        <name>Neal Hannon</name>
        <uri>http://gilbane.com/blog/mt-cp.cgi?__mode=view&amp;blog_id=42&amp;id=153</uri>
    </author>
    
        <category term="XBRL" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="XML" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="codification" label="Codification" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="edgar" label="EDGAR" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="fasb" label="FASB" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="sec" label="SEC" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xbrl" label="XBRL" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/xml/">
        <![CDATA[<p>Recently, XBRL US and the FASB released a new taxonomy reference linkbase to enable referencing to the FASB Codification. The FASB Codification is the electronic data base that contains all US GAAP authoritative literature and was designated as official US GAAP as of July 1, 2009.&nbsp; Minding the GAAP between the existing 2009 US GAAP taxonomy reference linkbase, which contains references to the old GAAP hierarchy (such as FAS 142r or FAS 162) and the new Codification system is an interesting trip indeed.</p>
<p>The good news is that the efforts of the XBRL US people working in co-operation with FASB and the SEC have resulted in direct links from the new XBRL reference database to the Codification.&nbsp; There are a couple problems, however.</p>
<p>The new reference linkbase is unofficial and will not be accepted by the SEC's EDGAR system. URI links point to the proper places in the COD for FASB publications but require a separate log in and give you access to the public (high level) view only.</p>
<p>Firms and organizations with professional access to the Codification will not find this a problem, but individual practitioners will have to subscribe (at $850 per year) to get any views beyond the bare bones.</p>
<p>SEC literature stops at the top of the page for ALL SEC GAAP citations. For example, any XBRL element that has a regulation SX reference will point to exactly the same place, the top of the document. Not very useful. The SEC should address this.</p>
<p>So it appears we have three levels of accounting material to deal with, 1) the high level public access literature, which is official US GAAP in the Codification; 2) the professional view additional detail and explanations, and 3) and the non-GAAP material the FASB left out of the COD that is in their hard copy literature but didn't make the COD/US GAAP cut. Ideally, all literature coming from the SEC or the FASB should be, in my opinion, easily accessible via the Internet.</p>
<p>
The present plans to fix the GAAP in the US GAAP XBRL taxonomy are to wait until the 2010 taxonomy is issued (Spring 2010).&nbsp; Although this would give the SEC plenty of time to tweak the EDGAR system into accepting the new linkbase, until then users of XBRL will have to accept workarounds to discover the authoritative literature link from an XBRL element tag and official US GAAP.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Give Financial Statements an MRI with XBRL</title>
    <link rel="alternate" type="text/html" href="http://gilbane.com/xml/2009/07/give-financial-statements-an-mri-with-xbrl.html" />
    <id>tag:gilbane.com,2009:/xml//42.9885</id>

    <published>2009-07-17T13:38:57Z</published>
    <updated>2009-07-18T10:50:08Z</updated>

    <summary><![CDATA[Recent news item:&nbsp; CLEVELAND (AP) &mdash; Indians outfielder Grady Sizemore is feeling better and will have an MRI on his strained left elbow on Monday. It has become very commonplace for doctors to order an MRI for patients experiencing pain....]]></summary>
    <author>
        <name>Neal Hannon</name>
        <uri>http://gilbane.com/blog/mt-cp.cgi?__mode=view&amp;blog_id=42&amp;id=153</uri>
    </author>
    
        <category term="XBRL" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="XML" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="secfilings" label="SEC filings" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xbrl" label="XBRL" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/xml/">
        <![CDATA[<p>Recent news item:&nbsp; CLEVELAND (AP) &mdash; Indians outfielder Grady Sizemore is feeling better and will have an MRI on his strained left elbow on Monday.</p> <p>It has become very commonplace for doctors to order an MRI for patients experiencing pain. According to Radiology Info.com, Magnetic resonance imaging (MRI) is a noninvasive medical test that helps physicians diagnose and treat medical conditions.&nbsp; The website goes on to say, &ldquo;MR imaging uses a powerful magnetic field, radio frequency pulses and a computer to produce detailed pictures of organs, soft tissues, bone and virtually all other internal body structures. The images can then be examined on a computer monitor, printed or copied to CD.&rdquo; (see <a href="http://www.radiologyinfo.org/en/info.cfm?pg=bodymr">http://www.radiologyinfo.org/en/info.cfm?pg=bodymr</a>)</p> <p>In a similar fashion, XBRL puts a company&rsquo;s financial statements under a transformation that exposes detailed pictures of the underlying accounting backing every line item.&nbsp; This information can then be analyzed and compared by computer software to help determine a company&rsquo;s financial health.</p> <p>For example, let&rsquo;s look at a sample line item from the Marathon Oil SEC filing covering the quarter ending September 30, 2008.&nbsp; The form 10-Q has a line on financial statement that reads:</p> <p>Loss on early extinguishment of debt 120&nbsp;(nine months ending September 30, 2007, in millions)</p> <p>When you give that line item the XBRL MRI treatment, computers can extract the XBRL label:</p> <p style="margin-left: 40px;">us-gaap:GainsLossesOnExtinguishmentOfDebt</p> <p>the definition of the item:</p> <p style="margin-left: 40px;">Amount represents the difference between the fair value of the payments made and the carrying amount of the debt at the time of its extinguishment.<br /> And the authoritative literature that backs up the accounting decisions:</p> <p>the reference:</p> <p style="margin-left: 40px;">Presentation Reference&nbsp;</p> <p style="margin-left: 40px;">Name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Accounting Principles Board Opinion (APB)<br /> Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 26<br /> Paragraph&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 20, 21<br /> Publisher&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AICPA</p> <p>Inquiring minds will take a close look at APB 26 for more detail.&nbsp; This examination should yield a much clearer understanding of the basis for reporting the number and therefore yield a better understanding of the financial statement.</p> <p>Note:&nbsp; Mr. Sizemore returned to full duty with the Cleveland Indians shortly after his MRI.</p>]]>
        
    </content>
</entry>

<entry>
    <title>When is a Book Not a Book?</title>
    <link rel="alternate" type="text/html" href="http://gilbane.com/xml/2009/07/when-is-a-book-not-a-book.html" />
    <id>tag:gilbane.com,2009:/xml//42.9884</id>

    <published>2009-07-16T19:00:44Z</published>
    <updated>2009-07-20T15:04:49Z</updated>

    <summary>I recently wrote a short Gilbane Spotlight article for an XML community site about the state of Iowa going paperless in regards to its Administrative Code publication. It got me to thinking, &quot;When is a book no longer a book?&quot;</summary>
    <author>
        <name>Dale Waldt</name>
        <uri>http://gilbane.com/blog/mt-cp.cgi?__mode=view&amp;blog_id=42&amp;id=120</uri>
    </author>
    
        <category term="Authoring" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="DITA - Darwin Information Typing Architecture" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="XML" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="contentbookpaperless" label="content book paperless" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/xml/">
        <![CDATA[<p>I recently wrote a short Gilbane Spotlight article for the <a href="https://community.emc.com/community/edn">EMC XML community site</a> about the state of Iowa going paperless (<a href="https://community.emc.com/docs/DOC-4308">article can be found here</a>) in regards to its Administrative Code publication. It got me to thinking, &quot;When is a book no longer a book?&quot; <br /><br />Originally the admin code was produced as a 10,000 page loose-leaf publication service containing all the regulations of the state. For the last 10 years it has also appeared on the Web as PDFs of pages, and more recently, independent data chunks in HTML. And now they have discontinued the commercial printing of the loose-leaf version and only rely on the electronic versions to inform the public. They still produce PDF pages that resemble the printed volumes that are intended for local printing of select sections by public users of the information. But the electronic HTML version is being enhanced to improve reusability of the content, present it in alternative forms and integrated with related materials, etc. Think mashups and improved search capabilities. The content is managed in an XML-based Single Source Publishing system that produces all output forms.<br /><br />I have migrated many, many printed publications to XML SSP platforms. Most follow the same evolutionary path regarding how the information is delivered to consumers. First they are printed. Then a second electronic copy is produced simultaneously with the print using separate production processes. Then the data is organized in a single database and reformatted to allow editing that can produce both print and electronic. Eventually the data gets enhanced and possibly broken into chunks to better enable reusing the content, but the print is still a viable output format. Later, the print is discontinued as the subscription list falls and the print product is no longer feasible. Or the electronic version is so much better, that people stop buying the print version.<br />So back to the original question, is it no longer a book? Is it when you stop printing pages? Or when you stop producing the content in page-oriented PDFs? Or does it have to do with how you manage and store the information?<br /><br />Other changes take place in how the information is edited, formatted, and stored that might influence the answer to the question. For instance, if the content is still managed as a series of flat files, like chapters, and assembled for print, it seems to me that it is still a book, especially if it still contains content that is very book oriented, like tables of contents and other front matter, indexes, and even page numbers. Eventually, the content may be reorganized as logical chunks stored in a database, extracted for one or more output formats and organized appropriately for each delivery version, as in SSP systems. Print artifacts like TOCs may be completely generated and not stored as persistent objects, or they can be created and managed as build lists or maps (like with DITA). As long as one version is still book-like, IMHO it is still a book. <br /><br />I would posit that once the printed versions are discontinued, and all electronic versions no longer contain print-specific artifacts, then maybe this is no longer a book, but simply content.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Busy Week in XML Content Management Market</title>
    <link rel="alternate" type="text/html" href="http://gilbane.com/xml/2009/07/busy-week-in-xml-content-management-market.html" />
    <id>tag:gilbane.com,2009:/xml//42.9864</id>

    <published>2009-07-01T18:32:56Z</published>
    <updated>2009-07-01T20:17:05Z</updated>

    <summary>Holiday weeks can be sleepy weeks in enterprise software news, but this week has seen one significant press release each day in the XML content management market, or component content management (CCM) market if you prefer.On Monday, SDL announced the...</summary>
    <author>
        <name>Bill Trippe</name>
        <uri>http://gilbane.com/blog/mt-cp.cgi?__mode=view&amp;blog_id=42&amp;id=2</uri>
    </author>
    
        <category term="DITA - Darwin Information Typing Architecture" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Publishing" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="XML" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="documentum" label="Documentum" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="doczone" label="DocZone" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="emc" label="EMC" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="quark" label="Quark" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="reallystrategies" label="Really Strategies" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="sdl" label="SDL" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="trisoft" label="Trisoft" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xyenterprise" label="XyEnterprise" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/xml/">
        <![CDATA[<p>Holiday weeks can be sleepy weeks in enterprise software news, but this week has seen one significant press release each day in the XML content management market, or component content management (CCM) market if you prefer.</p><ul><li>On Monday, <a href="http://www.sdltrisoft.com/en/landing-pages/acquisition/">SDL announced the acquisition of XyEnteprise</a>, and the creation of a new business unit based on XyEnterprise and Trisoft called SDL-XySoft.</li><li>On Tuesday, Really Strategies, the makers of the Marklogic-Server-based system RSuite, <a href="http://www.reallysi.com/pr_090630.htm">announced the acquisition of SaaS CCM provider DocZone</a>.</li><li>Today, Quark and EMC <a href="http://quark.com/pressdetail.aspx?nid=2422">announced an integration of Quark XML Author with Documentum</a>.</li></ul><p>First, the necessary disclosures and caveats. Of the six companies mentioned, we've worked with all of them, I believe, and I actually worked for XyEnterprise back in the 1980s and early 1990s. That said, each of these announcements is significant.</p><p>SDL, through both organic growth and acquistion, has grown into a substantial business that spans globalization technology, globalization services, CCM technology, and WCM technology. My colleagues Mary Laplante and Leonor Ciarlone know them much better as a company, but I believe it is safe to say that SDL is in a unique position spanning essentially four markets, but four markets that make a great deal of sense under a single umbrella. The product support content managed in a CCM technology is the best point of integration for globalization/translation tools. A CCM technology is also an excellent underpinning for a global company's web presence or web precenses (the latter more likely, especially when one considers the need for localized web sites). And services are an essential piece of this puzzle. It's the rare company that staffs heavily for localization, and even when they do, very few would staff full time to cover all of their language needs. Is SDL in a position to represent one-stop shopping for large companies with complex product content that needs to be localized into many languages? Again, my colleagues could answer that question more precisely, but it's not a crazy question to ask.</p><p>Mary has more on SDL XySoft <a href="http://gilbane.com/globalization/2009/07/sdl_scores_again_with_sdl_xysoft.html">over in the globalization blog</a>.</p><p>The acquisition also breathes new life into XyEnterprise, a company with highly functional, mature technology and excellent executive leadership. We take it as a very positive sign that XyEnterprise CEO Kevin Duffy will become the CEO of the newly combined business unit, reporting to Mark Lancaster, Chairman and CEO of SDL.</p><p>The Really Strategies acquistion of DocZone is on a smaller scale of course, but it is is significant in that these two companies represent two leading trends in the CCM marketplace--management of component content in native XML repositories (MarkLogic Server for RSuite and Documentum Content Store for one version of DocZone) and Software as a Service (SaaS). Count me among those who have been skeptical at times about SaaS for CCM, but DocZone, under Dan Dube's leadership, has made it work. Really Strategies, in the mean time, has developed an impressive CCM offering on top of Mark Logic Server, and they have quietly built up a strong customer list.&nbsp; We think the combined companies complement each other, and the new management team is excellent, with Barry Bealer as CEO, co-founder Lisa Bos as CTO, Ann Michael in charge of services, and Dan Dube as VP Sales and Marketing.</p><p>Which brings us to Quark and EMC. Both companies have been developing more CCM capabilities. EMC acquired X-Hive, and a lot of XML expertise along with it. They have since added more XML expertise on both the product management and engineering side. As they have integrated X-Hive into the Documentum platform, they have logically looked to build out more capabilities and applications for vertical markets. The integration with Quark XML Author makes perfect sense for them, giving their customers and prospects a ready mechanism for XML authoring in a familiar editorial tool.</p><p>For Quark's part, the move is a logical and very positive next step. They had <a href="http://quark.com/pressdetail.aspx?nid=63&amp;lang=us">previously announced this kind of integration with IBM Content Manager</a>, which has a strong presence in the manufacturing space. With EMC, Quark now has a strong partner in the pharma space. Documentum has long dominated pharma, and Quark XML Author, under Michael Boses and previous owner In.Vision, had built up a long list of pharma customers. Boses and his team know the pharma data structures inside and out, and it will be interesting to see the details of how Quark XML Author will integrate with Documentum and its storage mechanisms. (I am sure both EMC and Quark see the potential as more than just the pharma market--government is also a good target here--but the pharma angle will be fruitful I am sure.)</p><p>So, what news is on tap for tomorrow?</p>]]>
        
    </content>
</entry>

</feed>
