What are "Clippings?"
- IBM's BPWS4J Version 2.0 Supports BPEL4WS 1.1.
- Topologi Collaborative Markup Editor Version 1.1.3.
- GNOME Print Backend for PangoPDF.
- Updated Draft Version of GenXML 2.0.
[April 30, 2003] IBM's BPWS4J Version 2.0 Supports BPEL4WS 1.1. An updated [April 30, 2003] release of the IBM alphaWorks BPWS4J application provides support for BPEL4WS version 1.1 and contains an additional sample that makes use of the new BPEL4WS 1.1 features. The updated editor supports Eclipse 2.1. "The IBM Business Process Execution Language for Web Services Java Run Time (BPWS4J) includes the following: a platform upon which can be executed business processes written using the Business Process Execution Language for Web Services (BPEL4WS); a set of samples demonstrating the use of BPEL4WS; and a tool that validates BPEL4WS documents. The BPWS4J platform also includes an Eclipse plug-in that provides a simple editor for creating and modifying BPEL4WS files. Its main features are as follows: (1) Synchronized XML source and tree views of the business process being created; (2) Flexibility for accomodating bottom-up as well as top-down approaches to process design; (3) Context-sensitive menus that facilitate creation of specification-compliant processes; (4) Validation of process against specification requirements during editing session. For each process, the BPWS4J engine takes in a BPEL4WS document that describes the process to be executed, a WSDL document (without binding information) that describes the interface that the process will present to clients (partners in BPEL4WS terms), and WSDL documents that describe the services that the process may or will invoke during its execution. From this information, the process is made available as a Web service with a SOAP interface. A WSDL file that describes the process's interface may be retrieved from the run-time. The BPWS4J engine supports the invocation, from within the process, of Web services that have a SOAP interface, that are EJBs, or that are normal Java classes. BPWS4J has been tested on WebSphere Application Server 4.0+ and on Apache Tomcat under both Linux and Windows." On BPEL4WS version 1.1, see "OASIS Forms Web Services Business Process Execution Language TC (WSBPEL)."
[April 08, 2003] Topologi Collaborative Markup Editor Version 1.1.3. Rick Jelliffe posted an announcement for the release of the Topologi Collaborative Markup Editor Version 1.1.3. Text: "Version 1.1.3 of the Topologi Collaborative Markup Editor is released now on all platforms (Windows, Linux, Mac). Version 1.1.3 additions include: (1) New button bar and menu arrangement, for more convenient validation and preview; (2) Complete help files; (3) See whether a file is currently being edited by another member of your workgroup; (4) List and sort validation results; (5) Check the path of the current element; (6) Improved usability for low-vision users. Previous recent enhancements include: Validate with James Clark and Makoto Murata's ISO RELAX NG compact syntax; Validate with Eric van der Vlist's simple Examplotron; Enhanced visual cues for changed lines and lines with syntax errors; Reloading externally-changed files. The editor is available for individual users for US $60. A 30-day free evaluation copy can be downloaded. A special free license is available for charities and training. Supported site licenses with integration assistance is available for organizations. Related Topologi products include Preview-to-PDF for Advent 3B2, Preview-to-PDF for Adobe FrameMaker, and Web Relayer for peer access over HTTP." See details reported earlier: "Topologi Collaborative Markup Editor Supports XML and SGML."
[April 08, 2003] GNOME Print Backend for PangoPDF. Tony Graham (XML Technology Center, Dublin) announced an initial release of a GNOME Print backend for PangoPDF; see the CVS link. PangoPDF implements a version of the Pango library with a PDF backend for creating PDF output. This library also implements several of the inline properties defined by XSL that are not currently implemented by Pango. PangoPDF is designed to be API-compatible with the corresponding Pango version. The version number of the PangoPDF library, therefore, reflects the version number of the Pango version upon which library is based. The current PangoPDF version is 22.214.171.124, since it is based upon Pango 1.2.0. The goal of this project is to make itself redundant by implementing PDF support and XSL support so well that the additions are incorporated into Pango itself. The PangoPDF library tracks the official Pango library so the PangoPDF library can incorporate non PDF-related improvements and API changes as they are incorporated into Pango. PangoPDF uses PDFlib for PDF generation, but the long-term plan is to use gnome-print. PangoPDF writes PangoLayouts to a supplied PDF file, just as other Pango backends render PangoLayouts on a supplied bitmap..." See the SourceForge Project: Pango with PDF Backend. The PangoPDF Wiki contains semi-structured notes about PangoPDF that haven't yet made it into either the main web site or into the PangoPDF API documentation.
[April 04, 2003] Updated Draft Version of GenXML 2.0. Christoffer Owe released an updated draft version of GenXML 2.0. "GenXML is a file format for exchange of data between genealogy programs. It is an alternative to Gedcom 5.5. It is based on XML and defined by a XML schema. It is not intended to be used as an internal format of any genealogy programs, although it may be possible. The idea of GenXML is that: (1) it shall be easy to read by most genealogical programs; (2) it shall be easy to write by most genealogical programs; (3) it shall be easy to manipulate by third party programs; (4) all kinds of information shall fit into one and only one place... GenXML is mainly inspired by the theoretical Gentech Data Model..." Author's note 2003-04-04 for the draft version 31-March-2003: "I have uploaded a new GenXML 2.0 draft... Finally I have added an evidence model similar to GDM using a hierarchy of sources, while retaining compatibility with the Gedcom 5.5 data model. I have also replaced the former event structures with a singel event structure supporting an unlimited number of participants. In this way the group and couple structures of GenXML 1.0 becomes unnecessary. The result is both simpler and more powerful. In addition there are several major and minor changes. Note that this is still a draft. Some parts are not quite finished, and there are probably errors in it..." Available in PDF format. See general references in "Genealogical Data and XML."