This issue of XML Daily Newslink is sponsored by:
SAP AG http://www.sap.com
Translation Memory eXchange (TMX) and Segmentation Rules eXchange (SRX)
Rodolfo M. Raya, Network Posting
LISA (Localization Industry Standards Association) has released the Translation Memory eXchange (TMX) 2.0 specification for public comment, together with Segmentation Rules eXchange (SRX) Version 2.0. "TMX is the vendor-neutral open XML standard for the exchange of Translation Memory (TM) data created by Computer Aided Translation (CAT) and localization tools. The purpose of TMX is to allow easier exchange of translation memory data between tools and/or translation vendors with little or no loss of critical data during the process. In existence since 1998, TMX is a certifiable standard format. TMX is developed and maintained by OSCAR (Open Standards for Container/Content Allowing Re-use), a LISA Special Interest Group. According to research conducted by OSCAR, Translation Memory assets increasingly represent a strategic corporate asset, worth, in some cases, millions of dollars, and supporting hundreds of millions of dollars of international business. TMX provides a way to protect these assets against market and technology changes since TMX keeps users from being locked into a particular CAT tool. Segmentation Rules eXchange (SRX) is an XML-based standard for description of the ways in which translation and other language-processing tools segment text for processing. It was created when it was realized that TMX leverage is lower than expected in certain instances due to differences in how tools segment text. SRX is intended to enhance the TMX standard so that translation memory (TM) data that is exchanged between applications can be used more effectively. Having the segmentation rules that were used when a TM was created will increase the leverage that can be achieved when deploying the TM data."
See also: SRX
GCN Interview: David Schell, A New Worldview
Patrick Marshall, Government Computer News
David Schell founded the Open Geospatial Consortium in 1994. Since then, OGC has grown to encompass 341 member companies and organizations. That includes all the major geospatial developers, along with many government agencies and universities. GCN spoke with Schell to discuss the current state of geospatial standardization. Schell: "We invented a program called the Interoperability Program. In this program, we invited large organizations who had major requirements to state those requirements and to put up some resources to help stimulate a process to have those requirements looked at. OGC then issues an RFP to the community and asks the community to make proposals against these requirements. We usually get 40 to 50 responses from development organizations. They propose either working for some basic amount of resources to cover expenses, or they propose providing in-kind resources. They do this because they want to be involved in the development of an authentic solution that's going to be used just as soon as it is developed. The Interoperability Program has become a way that we are able to use user requirements—to drive the standards process. What's really nice about it is that everybody knows—it's a low-budget process. So the sponsors put up what they can. The developers provide in-kind participation. The result is that we very frequently get a one-to-three to a one-to-five return on investment. It's not just about standards and best practices. The result is really a collaborative community within the market... One of our great challenges right now is to harmonize the existing geospatial market, which comprises traditional powers like ESRI, Integraph and Autodesk as well as the new, dynamic, young companies like Ionic. And Google just joined the consortium. That's tremendously important for the industry because Google has really ensured that there is broad awareness for spatial information. The second great challenge is to get a lot more participation on the part of major industry players, including the auto industry, telecommunications and others. They all use and depend upon spatial information. Government agencies are all now lining up and adopting these standards, but many vendors are still stovepiped and haven't gotten involved in industrywide standards processes."
See also: OpenGIS Specifications
Collaboration, Interoperability, and Standards I
John Harrison, Blog
In today's operating environment everyone is talking about collaboration. However in order to collaborate communication is required. This sounds simple. Practically speaking it is not. In the Chemical Industry the automatic assumption would be to use the CIDX or Chem. eStandards. However this standard was designed to apply to inter-enterprise communication (but some companies have used this standard for intra-enterprise communication). The Chem eStandards have been developed by the members (chemical companies) of the Chemical Industry Data Exchange (CIDX) organization. These standards are used extensively in communication between chemical business partners. Even here with an agreed upon and supported standard there is room for confusion. When a company says that they support the standard, or follow the business process as described in the CIDX business process guidelines, what do they truly mean? Which release of the standard are they following, 2.0, 2.01, 2.03, 3.0, 4.0, or a combination of all the versions depending on the business process being followed? As a matter of fact, some companies modify the standard messages for their own use (which is fine) and still say that they follow the standard (which is not). Even more confusion takes place when companies venture into areas where the standards are not well defined. Take for example ISA-SP95 (Enterprise Control Integration Standard) used in manufacturing, many companies have different interpretations of the implementation of this standard. B2MML (Business to Manufacturing Markup Language), and BatchXML for example are examples of an implementation of the ISA-SP95 standard. Are standards important for Internal Communication? If so what standards do you use for which scenarios?
W3C Track Announced at WWW 2007 Conference
Staff, W3C Announcement
The World Wide Web Consortium welcomes the public to meet the W3C Staff and Members, who will present recent achievements and future work plans through the W3C Track at the WWW 2007 conference, to be held in Banff, Alberta, Canada, from 9 to 11 May 2007. Chaired by Marie-Claire Forgue, the nine sessions and some 34 presentations cover recent achievements and future work plans of W3C Activities. A session on "Architectural Integration" addresses the goal of combining markup from different namespaces together into a cohesive document—good if they all agree on core semantics such as events, submission, and data storage, thus forming a unified architecture for applications. These talks present ongoing work to define such semantics, and demonstrate them in use. ['The W3C Rich Web Application Backplane'; 'XML Application Components and Controllers'; 'xH: A Standards-based Web Application Programming Language']. A session "Web of Services for Enterprise Computing" covers the core parts of Web Services: "This session presents three of the latest developments: WSDL 2.0, the Web Services Description Language for SOAP based and HTTP-only services, WS-Policy 1.5, a general purpose languages to describe the policies of Web Services, and SAWSDL 1.0 to allow the description of additional semantics of WSDL components. Each presentation will include an introduction to the specifications as well as implementation reports/demonstrations. The session will also include a report on the W3C workshop on the Web of Services for Enterprise Computing, looking at the future of Services on the Web." A session "Advances in Semantic Web" shows three different aspects of the Semantic Web activity at W3C. The RIF presentation gives an overview of one of the developments for the ground Semantic Web infrastructure. The GRDDL and RDFa talk concentrates on technologies whose primary goal is to outreach to other technologies and communities. Finally, an example will show how a large user community uses this technology to solve its own research and development problems.
See also: the announcement
Rogue Wave Launches HydraSCA for High Performance SOA Applications
Staff, Rogue Wave Software Announcement
Rogue Wave Software, a division of Quovadx, Inc. and supplier of software development solutions for high performance business applications, has announced the release of Rogue Wave HydraSCA as "the first service grid for deploying high performance Service Oriented Architecture (SOA) applications based on the Service Component Architecture (SCA) specification." HydraSCA is the latest release in the Rogue Wave Hydra Suite and is the first high performance service grid based on SCA specification. The completion of the SCA 1.0 specification was announced in March 2007 by the Open SOA Collaboration, an informal group of industry leaders, which includes Rogue Wave Software. SCA significantly reduces the complexity commonly associated with SOA by simplifying the creation and composition of services regardless of programming languages, including Java, C++ and BPEL. Rogue Wave HydraSCA enables application developers to quickly increase performance and scalability of an individual service or a globally distributed application by employing concurrently running services -- all without requiring special expertise in multi-threaded programming. "As the first service grid based on Software Pipelines, a methodology designed to leverage concurrent computing to deliver high performance business applications, Rogue Wave HydraSCA allows developers to tie existing components together in a powerful, agile business process and run them concurrently—without rewriting for multi-threading."
XML Daily Newslink and Cover Pages are sponsored by:
|BEA Systems, Inc.||http://www.bea.com|
|Sun Microsystems, Inc.||http://sun.com|
XML Daily Newslink: http://xml.coverpages.org/newsletter.html
Newsletter Archive: http://xml.coverpages.org/newsletterArchive.html
Newsletter subscribe: firstname.lastname@example.org
Newsletter unsubscribe: email@example.com
Newsletter help: firstname.lastname@example.org
Cover Pages: http://xml.coverpages.org/