Arbortext, Inc. announced the availability of Epic Intermarket, a solution that enables suppliers and net marketplaces to deploy catalog applications that offer more extensive, more personalized and more usable content. Epic Intermarket is built upon Arbortext’s Epic E-Content Engine (E3), a Web-based system for aggregating, storing, assembling and distributing enriched content. Epic Intermarket leverages the power of E3 to gather content from multiple sources including Word, FrameMaker and Interleaf, and convert that content into reusable XML components. E3 also works with Arbortext’s Epic Editor and Epic Editor LE, both of which enable direct creation of XML content. Epic Intermarket integrates with repositories from Oracle, Documentum and others to enable seamless creation and management of reusable and intelligent XML information components. Through E3, Epic Intermarket extracts content from the repository, assembles it according to individual requirements, and automatically transforms it for any purpose – not only for publishing to the Web, but also for traditional catalog formats such as print and CD-ROM as well as newer devices such as PDAs, e-Books and cellular phones. In addition, Intermarket can syndicate catalog content to multiple marketplaces. Epic Intermarket supports the e-commerce schema standards from Open Applications Group, Inc., so Intermarket can exchange catalog content with business-to-business online marketplace providers such as Ariba, CommerceOne and Oracle. Epic Intermarket will ship in January 2001. Epic Editor and the Epic E-Content Engine are included in a minimum Intermarket installation. Epic Intermarket runs on the Microsoft IIS Web server running on NT Server 4.0/SP5 or later or Netscape’s iPlanet Web server running on Sun Solaris 7. Epic Intermarket works with Oracle 8iFS and Java Runtime Engine 1.1.8 or later. www.arbortext.com
Day: November 12, 2000
Reciprocal Inc. unveiled Version 3.0 of Reciprocal Commerce Access Protocol. This enhanced XML-based communications technology enables the secure transfer of permit order information between Reciprocal and its customers. Reciprocal Commerce Access Protocol allows content companies, retailers or distributors to better control and manage digital content by communicating order information back to Reciprocal’s clearinghouse. This communication allows clients to easily integrate their content business with Reciprocal’s DRM services. Information and a series of instructions are communicated via the Reciprocal Commerce Access Protocol from a retail site to the Reciprocal Digital Clearing Service, which then fulfills the retailer’s instructions and issues the permits that allow the end-user to have access to secure content files. Once packaged, the digital content can then be securely distributed with predefined business rules that consumers must satisfy before accessing the content. Business rules can range from payment, collection of consumer information, or other exchanges of value defined by the content owner. Retailers looking to take advantage of Reciprocal Commerce Access Protocol do not need to install any new hardware or software. Rather, they can simply send a secure XML message to integrate with Reciprocal’s services. www.reciprocal.com
The World Wide Web Consortium (W3C) released the Document Object Model Level 2 specification as a W3C Recommendation. The specification reflects cross-industry agreement on a standard API for manipulating documents and data through a programming language (such as Java or ECMAScript). Created and developed by the W3C Document Object Model (DOM) Working Group, this specification extends the platform- and language-neutral interface to access and update dynamically a document’s content, structure, and style first described by the DOM Level 1 Recommendation. The DOM Level 2 provides a standard set of objects for representing XML documents and data, including namespace support, a style sheet platform which adds support for CSS 1 and 2, a standard model of how these objects may be combined, and a standard interface for accessing and manipulating them. DOM Level 1 was designed for HTML 4.0 and XML 1.0. With DOM Level 2, authors can take further advantage of the extensibility of XML. Simply put, anywhere you use XML you can now use the DOM to manipulate it. The standard DOM interface makes it possible to write software for processing customized tag-sets in a language- and platform-independent way. DOM Level 2 provides support for XML namespaces, extending and improving the XML platform. The DOM provides a uniform way to produce programs that work across a variety of different devices, so all may benefit from dynamically generated content. The DOM Level 2 Cascading Style Sheet (CSS) API makes it possible for a script author to access and manipulate style information associated with contents, while preserving accessibility. DOM Level 2 also includes an Events API to provide interactivity anywhere someone uses XML – in documents, in data, or in B2B applications. Other W3C Working Groups are currently at work in extending further the DOM Level 2 platform for Scalable Vector Graphics (SVG) and Mathematical Markup Language (MathML). The DOM Working Group is currently at work developing DOM Level 3, the next layer of functionality for DOM. www.w3c.org
