This issue of XML Daily Newslink is sponsored by:
Converting Annotated RELAX NG Schemas for Use in I-Ds or RFCs
Ladislav Lhotka (ed), IETF Internet Draft
This memo presents a method for annotating XML schemas expressed in the RELAX NG language and transforming them to a form suitable for direct inclusion in an XML source of an IETF Internet Draft (I-D) or Request for Comments (RFC). The Extensible Stylesheet Language Transformations (XSLT) stylesheet performing the transformation also automatically generates cross-references between RELAX NG pattern definitions and their references. In the context of IETF activities, the most natural way of publishing and/or standardizing an XML schema is to make it a part of an Internet Draft or RFC that describes the application the schema is used for. However, including an annotated schema directly in an I-D or RFC is not optimal since the annotations wrapped in XML elements are clumsy and hard to read. XML comments are better in this respect, but still the best option for rendering the annotations is to convert them into standard paragraphs of the I-D or RFC. The strategy presented here for annotating RELAX NG schemas and transforming them for inclusion into XML source follows methods documented in "Writing I-Ds and RFCs using XML" (RFC 2629). The method presented in this memo is similar in spirit to "literate programming in XML", which may be applied to arbitrary XML documents, for example XSLT stylesheets. However, its main benefit, namely that it allows for arbitrary modularization and reordering of the original document, just duplicates the intrinsic functionality of RELAX NG based on the "define" and "ref" elements. Therefore, the specialized XSLT stylesheet rng2rfc.xsl is considerably simpler and yet achieves better results.
See also: XML and Literate Programming
Reliable Messaging in Ruby with AP4R
Sebastien Auvray, InfoQ
Shun'ichi Shinohara and Kiwamu Kato have been working on bringing reliable messging to Ruby with their own API and protocol project, based on previous experiences designing a Java-based high volume messaging framework. AP4R, Asynchronous Processing for Ruby, is an implementation of reliable asynchronous message processing, providing message queuing and message dispatching. Shun'ichi and Kiwamu gave a presentation at RubyKaigi 2007 about their API emphasizing its key design philosophies: Robustness and Lightweight. The project is just a year old, and already supports: (1) Business logic can be implemented as simple Web apps or ruby code, whether it's called asynchronously or synchronously; (2) RBMS (MySQL) or file-based message persistance; (3) Load balancing over multiple AP4R processes on single/multiple server(s) is supported; (4) Multiple protocol support: XML-RPC, SOAP, HTTP POST, and more.
See also: the online documentation
Enabling Read Access for Web Resources
Anne van Kesteren (ed), W3C Technical Report
This Isn't Your Father's IBM
Darryl K. Taft, eWEEK
Big Blue may still deal in COBOL and target big enterprises, but alphaWorks shows that the company also is delving deep into Web 2.0 technologies. IBM is gearing up to deliver a new version of the alphaWorks site in August, according to Chris Spencer. With the new version of alphaWorks, IBM is planning to let the community have a hand in shaping the site. "We're going to put out a beta and see what the market wants and likes," he said. "Then we'll change it to reflect that. One thing we found interesting is that developers aren't just interested in tools, but increasingly they have interest in the business side of things." One thing the new alphaWorks will do is facilitate more interactivity between the community and IBM's emerging technology creators. For example, the person who created an emerging technology will conduct a webinar on the technology, then a demonstration, followed by a live question-and-answer session where observers can use VOIP (voice over IP) to ask questions of the creator. ThinkPlace, another alphaWorks Service, is a Web application for facilitating innovation through idea generation, collaboration and refinement. QEDWiki, yet another of the alphaWorks Services, is an environment that extends current wiki technology to enable rapid deployment, content aggregation, structured data and powerful extensibility. Other alphaWorks Services include the IBM Development Engagement (also known as DevEngage) Deep Thunder, and Web Relational Blocks. IBM Development Engagement Service is an online service providing an AJAX-based development environment that enables business users to visually develop form applications.
Symmetric Key Services Markup Language (SKSML) Requirements
Arshad Noor, et al; OASIS Committee Draft
Members of the EKMI Symmetric Key Services Markup Language (SKSML) Subcommittee have released a draft of the SKSML Requirements document, approved as a Committee Draft by the OASIS Enterprise Key Management Infrastructure (EKMI) Technical Committee. The OASIS Symmetric Key Services Markup Language (SKSML) is the proposed language/protocol that defines how a client on a network will request and receive services for symmetric encryption cryptographic keys from a server. The document establishes the requirements for SKSML, as well as the rationale for those requirements. Clients may consist of computerized devices such as Personal Digital Assistants (PDA), telephones, laptop, desktop and server-class computers, applications such as office productivity, database, e-commerce, healthcare, financial or other applications, and/or devices such as routers, printers, disks, tape-drives, etc. Symmetric encryption cryptographic keys may consist of Triple Data Encryption Standard (3DES) or the Advanced Encryption Standard (AES).
See also: the EKMI TC FAQ document
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: email@example.com
Newsletter unsubscribe: firstname.lastname@example.org
Newsletter help: email@example.com
Cover Pages: http://xml.coverpages.org/