Mondosoft announced the availability of a Web Service Search Kit that facilitates the deployment of search through web services. The Web Service Search Kit makes it easy to create a unified search index across multiple data sources, programming languages and software applications. Because it allows for local customization of search results and search options no matter where content is stored, it is useful for departmental, branch or user-specific adjustments of search results. The Kit can be accessed by and deployed with any language that supports XML and SOAP. Two samples are included with Mondosoft’s Web Service Search Kit. The Research Service for Microsoft Office 2003 sample allows access to content sources from different places and of various types directly from a search field in MS Office applications. In addition, a Windows application sample is included to demonstrate how the Kit is used and how web services can operate in Microsoft environments. The Web Service Search Kit is available free of charge for download to Mondosoft customers and partners and easily installs on top of existing MondoSearch implementations. www.mondosoft.com
Year: 2005 (Page 92 of 95)
Quark, Inc. introduced QuarkXPress Markup Language (QXML), an XML schema of the W3C Document Object Model (DOM) that will make it easier for developers to create custom XTensions software for QuarkXPress. The QXML schema fully describes the QuarkXPress file format in XML and enables QuarkXPress 6.5 XTensions software to be developed using a variety of development platforms and languages, including Java, .Net, and many scripting languages. QXML presents a QuarkXPress project as an XML tree and any modifications to the XML files change the project in real time. With QXML, developers can dynamically access and update the content, structure and style of a QuarkXPress project using a DOM interface. XTensions modules can be more versatile because they can use a project’s complete content, including all formatting, style sheets, hyphenation, and justification specifications. Additionally, developers can run query expressions using XPath queries. The initial version of QXML allows developers to read data from a QuarkXPress project. In the next version, developers will be able to both read from and write to QuarkXPress projects. The QXML developer kit is available immediately to certified QuarkXPress XTensions developers. www.quark.com
Autonomy Corporation plc announced an OEM agreement with EidosMedia, who has embedded Autonomy’s technology into its knowledge management and cross media publishing environment Methode. Autonomy’s advanced pattern-recognition software adds the ability to automate and accelerate processes on structured and unstructured data to EidosMedia solutions. Automatic profiling and alerting allow the delivery of content to the right recipients without the need for any manual input. Information can be imported and retrieved from a variety of sources and in numerous different formats. Additionally, the software enables EidosMedia to provide their customers with automatic hyperlinks to relevant content from internal and external sources. www.eidosmedia.com, www.autonomy.com
CMS Watch released their semi-annual update of “The CMS Report”. The key findings of the report include: Mid-market vendors now offer comprehensive Web content management packages that are typically easier to implement than those from enterprise-tier players; A new class of mid-market “challengers” can provide XML-based solutions, often for less than US$40,000 in licensing; Major USA-based CMS vendors have seen only limited success selling Web content management tools in Europe, where national and regional suppliers have snapped up most large accounts; Although feature sets are converging across CMS vendors, underlying technical architectures continue to diverge in important ways; Different vendors also follow highly distinct user-interface models, and; There are no predominant Web content management suppliers in the marketplace, which means prospective buyers face a confusing set of alternatives – nevertheless, a little diligence can yield good choices. The 7th Edition of The CMS Report provides updated analysis and 4-10 page comparative product surveys of 31 Web content management offerings as well as short descriptions of more than 15 other packages across 7 product categories. New vendors added in this edition include IBM, SiteCore A/S, and Refresh Software. Other vendors covered include Microsoft, Documentum, Interwoven, FileNet, Vignette, Stellent, Day, OpenText, Percussion, Serena, RedDot, Ektron, Tridion, FatWire, Mediasurface, PaperThin, and Atomz. The report is available for purchase online from CMS Watch http://www.cmswatch.com.
DataPower announced the availability of firmware release v3.1 for its DataPower XA35 XML Accelerator. The latest version of the product expands the benefits of hardware acceleration to applications that make use of XML schema, XML parsing, XSLT 2. 0 and XPath 2.0. Firmware release v3.1 release allows the XA35 to accelerate not just the XML messages themselves but also the XML schemas associated with the messages. A brand new XML Schema engine improves the performance of XML parsing and schema validation. V3.1 also includes Java object support for J2EE-based XML applications and support for transforming XML into binary messages (via DataGlue option). Also included are multiple enhancements for the user interface including the Control Panel for overall management, wizard-like interface to facilitate XML accelerator creation, logging drill-down, and enhanced troubleshooting tools. The XA35 XML Accelerator is a member of DataPower’s XML-aware networking product family, which includes the XS40 XML Security Gateway, the XI50 XML Integration Appliance and the XG4 XML Chipset for OEMs. DataPower’s firmware release v3.1 for the DataPower XA35 XML Accelerator is available immediately. www.datapower.com
Bill Trippe’s post on January 04, 2005, “ECM and Business Process Management,” and the discussion emerging from Bill Zoellick’s post on January 08, 2005, “Sarbanes-Oxley: Too Narrow?” (especially comment by Glen Secor) make me think about the issue of DRM transactional infrastructure. Glen Secor’s comment, especially, while framing the compliance issue more usefully in regard to effective implementation strategies, also helps highlight the significant challenge ahead for DRM (or, in Glen’s usage, ERM, for enterprise rights/[business]rules management).
When the scope of integration becomes as wide as Glen argues it must, it seems to me that the DRM infrastructure requires ubiquity. After all, what we’re talking about is governing content not just between and among departments within an enterprise, but also among partners, suppliers, regulators, and a dozen other categories of participant that aren’t necessarily easily anticipated. The good news is that the DRM approach to security, compliance, and business process integration of content is theoretically flexible and applicable—arguably the best single strategy to show up to date. The bad news may be that theory will move to practice only when a sufficient DRM transactional infrastructure emerges.
But what is a sufficient DRM infrastructure? At best it would be one or a number of trusted environments that provide ubiquitous business rule transaction management common to all participants, so that enterprises could concentrate on defining and associating the business rules needed with all types of content. Since DRM platforms must not only accept and manage rules associated with content, but handle financial transactions and regulatory demands (among other things), and since the advantages of electronic commerce brings with it fast-changing relationships and conditions, the best solution is to use a DRM system in which all others can and will participate.
There are reasons for hope, albeit, perhaps, not in regard to a quick-to-emerge DRM ubiquitous infrastructure. XML-based common meta-data structures provide portability and platform independence to a large degree, and there have been some early efforts toward defining DRM meta-data with XML (ContentGuard’s XrML being the best known, but hardly the only effort). In short, the general industry trend toward abstracting meta-data above platforms means that DRM in the enterprise already has some applicable structure. However, apart from some limited examples—Authentica and Adobe come to mind—there’s still not much in the way of DRM “editorial interfaces” (i.e., rules definition and association) for content management. Fortunately, there’s little barrier to the creation and improvement of such interfaces, and preferably within CM platforms themselves.
But the question remains: is widespread compliance, security, and business processes associated with content likely without a general infrastructure such as the “Trusted Environment” on the Intertrust model? There are plenty of small- and mid-sized companies that won’t be able to afford particular DRM solutions that are not generally addressable. There is a great amount of work left to do to bring DRM into the enterprise, and while some pieces of the puzzle are in place or on their way, I wonder if the lack of working generalized trust environments remains the missing necessary piece for all sorts of “content governance” implementations.
Bill Trippe’s post on January 04, 2005, “ECM and Business Process Management,” and the discussion emerging from Bill Zoellick’s post on January 08, 2005, “Sarbanes-Oxley: Too Narrow?” (especially comment by Glen Secor) make me think about the issue of DRM transactional infrastructure. Glen Secor’s comment, especially, while framing the compliance issue more usefully in regard to effective implementation strategies, also helps highlight the significant challenge ahead for DRM (or, in Glen’s usage, ERM, for enterprise rights/[business]rules management).
When the scope of integration becomes as wide as Glen argues it must, it seems to me that the DRM infrastructure requires ubiquity. After all, what we’re talking about is governing content not just between and among departments within an enterprise, but also among partners, suppliers, regulators, and a dozen other categories of participant that aren’t necessarily easily anticipated. The good news is that the DRM approach to security, compliance, and business process integration of content is theoretically flexible and applicable—arguably the best single strategy to show up to date. The bad news may be that theory will move to practice only when a sufficient DRM transactional infrastructure emerges.
But what is a sufficient DRM infrastructure? At best it would be one or a number of trusted environments that provide ubiquitous business rule transaction management common to all participants, so that enterprises could concentrate on defining and associating the business rules needed with all types of content. Since DRM platforms must not only accept and manage rules associated with content, but handle financial transactions and regulatory demands (among other things), and since the advantages of electronic commerce brings with it fast-changing relationships and conditions, the best solution is to use a DRM system in which all others can and will participate.
There are reasons for hope, albeit, perhaps, not in regard to a quick-to-emerge DRM ubiquitous infrastructure. XML-based common meta-data structures provide portability and platform independence to a large degree, and there have been some early efforts toward defining DRM meta-data with XML (ContentGuard’s XrML being the best known, but hardly the only effort). In short, the general industry trend toward abstracting meta-data above platforms means that DRM in the enterprise already has some applicable structure.
However, apart from some limited examples—Authentica and Adobe come to mind—there’s still not much in the way of DRM “editorial interfaces” (i.e., rules definition and association) for content management. Fortunately, there’s little barrier to the creation and improvement of such interfaces, and preferably within CM platforms themselves.
But the question remains: is widespread compliance, security, and business processes associated with content likely without a general infrastructure such as the “Trusted Environment” on the Intertrust model? There are plenty of small- and mid-sized companies that won’t be able to afford particular DRM solutions that are not generally addressable. There is a great amount of work left to do to bring DRM into the enterprise, and while some pieces of the puzzle are in place or on their way, I wonder if the lack of working generalized trust environments remains the missing necessary piece for all sorts of “content governance” implementations.
Inxight Software, Inc. announced the latest release of Inxight LinguistX Platform, which adds support for four new languages Catalan, Croatian, Slovak and Slovenian bringing the total number of supported languages to 31. This release also upgrades Inxight’s Japanese language module with content from Inxight partner The CJK Dictionary Institute (CJKI). Inxight’s LinguistX Platform capabilities enable software developers to build multi-language information retrieval and analysis features into their products, which are critical to search and text mining applications. The Inxight LinguistX Platform provides the differentiating technology and language know-how for Inxight’s Entity Extraction, Fact Extraction, Categorization and Search solutions. www.inxight.com