Day Software (SWX:DAYN) (OTC:DYIHY) announced that the company is delivering a Java Technology API standard (JSR 170) connector for FileNet P8 Content Manager. Other connectors that are in development include interfaces for Microsoft SharePoint, IBM Domino.doc, and Software AG Tamino, among others. The FileNet P8 Content Manager connector is part of Day’s Content Integration family of products that enable enterprises to access and manage all organizational content through a standardized API. This technology allows the implementation of content access, synchronization and consolidation, leveraging future-proof standardization, even if the content resides in data stores that do not provide a JCR compliant API. http://www.day.com
Category: Enterprise software & integration (Page 24 of 31)
Ipedo announced major enhancements to the XQuery Views capabilities in Ipedo XIP. In conjunction with the W3C’s formal establishment of the XQuery standard, Ipedo now provides organizations with enhanced XML query processing and data virtualization in their EII platform. Ipedo’s XQuery Views – a data virtualization approach that allows data to be combined without the need to copy, stage and transform it – also enables queries across combinations of data from remote XML and relational sources. This feature increases access to data and content across organizations. Ipedo’s XQuery can be used in conjunction with the XML processing and XQuery now available in Oracle 10g, DB2, and Microsoft SQL Server. Ipedo XIP allows XQuery Views results to be cached natively in XML. The new XQuery engine implements query operators that stream data values, so that query evaluation is memory efficient. XQuery Views can now be invoked directly via a Web Services API. Ipedo XIP can automatically generate the WSDL file needed for a particular XQuery View. In addition to standard data sources, Ipedo’s XQuery extension framework now makes it possible for users to make custom data sources, such as in-house applications accessed using custom APIs. In addition to the above features, Ipedo has developed further enhancements to XQuery in Ipedo XIP’s Dual-Core Query Architecture, including access to stored procedures in relational databases with support for parameterization of the XQuery Views that access them, and extended query plan description that will allow deeper drilldown of the steps involved in XQuery execution. These enhancements are available immediately for Ipedo XIP version 4.2 on Windows 2000, Windows NT, Sun Solaris, Red Hat Linux and SuSE Linux. Pricing is on a per-CPU basis. http://www.ipedo.com
Vamosa has released version 2.9 of their content analysis and migration software, Vamosa Content Migrator. Vamosa Content Migrator version 2.9 has enhanced document migration capabilities and introduces ‘link cohesion’ for the document world. Link Cohesion has been a long-standing feature of Vamosa Content Migrator and has been used to great effect when migrating web content to translate all internal website hyperlinks. The extension of this functionality to incorporate documents will be beneficial to organisations with large document and content repositories. Link Cohesion for documents allows Vamosa Content Migrator to analyse organisation’s documents (Word, Excel or PDF etc) and examine links held within those documents. Where necessary the product will automatically and intelligently adjust these links to maintain their validity and ensure that the content referred to by the link remains accessible in the new content management system and architecture. http://www.vamosa.com
There are two new posts on the CTO Blog to check out: Eric Severson on XML and Office 2.0, and Carl Sutter on What is the future of software as a service.
As Tim Bray says “Wow”. Here is the announcement post with a huge number of comments. This is discouraging. As I have argued before, we need the kinds of capabilities WinFS was striving for to make the next leap in managing information. I remain skeptical that database platforms are a sufficient solution for effective object management – they may be the necessary next step, but they are certainly not the ultimate answer.
There are no doubt many easier, shorter-term ways to get return on software development than a radically different operating system, but hopefully at some point there will be sufficient recognition by all the software infrastructure vendors that working together to build a modern OS would be worth it. On the other hand, perhaps what has happened to WinFS is really a sign that the days of huge operating systems are numbered. The problems are really bigger than any one platform. What kind of cross-platform infrastructure is feasible to accomplish the fluid, granular and meaningful interchange of content and behavior we know we need? This is a more interesting question than whether WinFS itself is dead.
UPDATE: There is a lot of commentary out there, but as usual Jon Udell has a view worth reading.
Since we have our conference on Content Technologies for Government in Washington this week I probably will not get to Tech-Ed which is at our new convention center here in Boston, even though it is less than 2 blocks away. But if I had the time, I would be there scouting out the new WinFS beta and the intriguing Project Orange, (which may be relevant to the previous post on Viper). Mary Jo Foley has a list of the top 10 things to watch for there. She and others have pointed to this post for some clues on Project Orange.
Our colleagues over at CMS Watch have published a new report on enterprise portals. As our earlier reports here and here on the portal market suggested, the list of vendors covered in the report shows the market is now dominated by infrastructure players. Janus Boye, the author of the report is giving a tutorial on Enterprise Portal Software: Architecture and Products – Intensive Review & Roadmap for Product Selection at our upcoming conference in San Francisco, and also speaking on Challenges in Integrating Portals & Content Management Systems. The report, tutorial, and conference session would be a great way to get fully up-to-speed on corporate portals and content management.
Microsoft’s InfoPath was announced with great fanfare in October 2003 as part of the Office 2003 release. Microsoft then included some enhancements to InfoPath in a Service Pack release (SP1) of Office, which was distributed in June 2004. Since then, there has been little news about InfoPath. The InfoPath team blog at the Microsoft Developer Network went quiet in early 2005, with its last post in November of 2005, which was an announcement of an InfoPath 2003 Toolkit for Visual Studio 2005. There is a newish InfoPath tips-and-tricks blog by Microsoft blogger Tim Pash, but other than that, Microsoft has been very quiet about InfoPath. Does this suggest a reduced commitment by Microsoft?
UPDATE: As you can see from the comments, Microsoft appears to be plenty busy with InfoPath. See also this post from Eric Richards, who is a development lead on Microsoft Office.