The Cover PagesThe OASIS Cover Pages: The Online Resource for Markup Language Technologies
Advanced Search
Site Map
CP RSS Channel
Contact Us
Sponsoring CP
About Our Sponsors

Cover Stories
Articles & Papers
Press Releases

XML Query

XML Applications
General Apps
Government Apps
Academic Apps

Technology and Society
Tech Topics
Related Standards
Last modified: May 05, 2009
XML Daily Newslink. Tuesday, 05 May 2009

A Cover Pages Publication
Provided by OASIS and Sponsor Members
Edited by Robin Cover

This issue of XML Daily Newslink is sponsored by:
Sun Microsystems, Inc.

OASIS Advances KMIP Standard for Enterprise Encryption Key Management
Staff, OASIS Announcement

OASIS announced the formation of a new group to enable interoperability of key management services and clients. The new OASIS Key Management Interoperability Protocol (KMIP) Technical Committee will work to define a single, comprehensive protocol for communication between encryption systems and a broad range of new and legacy enterprise applications, including email, databases, and storage devices. KMIP will enable key lifecycle management, including the generation, submission, retrieval, and deletion of cryptographic keys. Designed for use by both legacy and new encryption applications, KMIP will support symmetric and asymmetric keys, digital certificates, and other 'shared secrets'. "As encryption technologies become more pervasive across the enterprise, key management quickly becomes a mission critical activity for protecting the sensitive data. Without a standard way to integrate encryption technologies and key management systems, data confidentiality and integrity may actually degrade," said Jon Oltsik, Principal Analyst at the Enterprise Strategy Group. "To address this issue, I've long been a strong proponent of key management standards and did what I could to push leading security vendors in this direction. I'm happy to say that the OASIS KMIP effort may finally fill this void." Robert Griffin of EMC, co-chair of the OASIS KMIP Technical Committee: "Our goal is to dramatically simplify the way companies encrypt and secure information." Anthony Nadalin of IBM, co-chair of the OASIS KMIP Technical Committee: "By removing redundant, incompatible key management processes, KMIP will provide better data security while at the same time reducing expenditures on multiple products."

See also: KMIP details and references in Cover Pages

What Can You Do with Extensible Messaging and Presence Protocol (XMPP)?
Kathryn Barrett,

"The Extensible Messaging and Presence Protocol (XMPP) is an open technology for real-time communication, using the Extensible Markup Language (XML) as the base format for exchanging information. In essence, XMPP provides a way to send small pieces of XML from one entity to another in close to real time. XMPP is used in a wide range of applications, and it may be right for your application, too. To envision the possibilities, it's helpful to break the XMPP universe down at a high level into services and applications. The services are defined in two primary specifications published by the Internet Engineering Task Force (IETF) (the "RFC" series), and in dozens of extension specifications published by the XMPP Standards Foundation; the applications are software programs and deployment scenarios that are of common interest to individuals and organizations, although the core services enable you to build many other application types as well. XMPP provides Core Services, Channel Encryption, Authentication. Presence, Contact Lists, One-to-one messaging, Multi-party Messaging, Notifications, Service Discovery, Capabilities Advertisement, Structured Data Forms, Workflow Management, Peer-to-peer Media Sessions, etc... Although XMPP was originally developed in the Jabber open source community, the protocol itself is not an open source project like Apache, but rather an open standard like HTTP. As a result, XMPP is an open technology that is not tied to any single software project or company. The XMPP specifications define open protocols that are used for communication among network entities. Much as HTTP and HTML define the protocols and data formats that power the World Wide Web, XMPP defines the protocols and data formats that power real-time interactions over the Internet. The protocols are as free as the air, which means they can be implemented in code that is licensed as free software, open source software, shareware, freeware, commercial products, or in any other way. This open standards model is different from the open source or free-software model for software code, wherein the code is often licensed so that modifications must be contributed back to the developers...

The original Jabber developers were focused on building an instant messaging system. However, the extensible nature of XML has made XMPP attractive to application developers who need a reliable infrastructure for rapidly exchanging structured data, not just IM features. As a result, XMPP has been used to build a wide range of applications, including content syndication, alerts and notifications, lightweight middleware and web services, whiteboarding, multimedia session negotiation, intelligent workflows, geolocation, online gaming, social networking, and more. Over the years, the developer community defined a large number of extensions to the core protocols. These extensions are developed through an open, collaborative standards process and published in the XSF's XMPP Extension Protocol (XEP) series... [Note: this article was prepared/adapted as an extract from the book "XMPP: The Definitive Guide." by Peter Saint-Andre, Kevin Smith, and Remko Troncon.]

See also: the XMPP Standards Foundation

Hierarchy Extensions to Atom Feeds
Colm Divilly and Nikunj Mehta (eds), IETF Internet Draft

This revised level -00 Internet Draft defines a mechanism to create and remove AtomPub collections using the AtomPub protocol as well as to express hierarchies of feeds within the Atom Syndication Format. Introduction: "Many applications provide their data in the form of syndicated Web feeds using formats such as Atom ("The Atom Syndication Format", RFC 4287) in order to enable application integration. Applications may also manipulate the contents of these data feeds using protocols such as AtomPub ("The Atom Publishing Protocol", RFC 5023). A key requirement for application data feeds is the ability to dynamically create new Collections and identify relationships among such feeds and Collections. This specification defines a mechanism for identifying hierarchical master-detail relations among data feeds so that consumer applications can perfrom standard AtomPub operations on them. A hierarchical master-detail relation of an Entry to a Feed implies the detail Feed is created when the master Entry is created and the Feed is removed when the Entry is removed. The Entry is called the "master entry" and the Feed is called "detail feed". This relationship allows a client to use AtomPub to create a new Collection by posting an Entry to an existing Collection. This specification proposes optional and compatible extensions to Atom and AtomPub to ease the process of creating and manipulating collections and feeds based on those collections... Protocol Model: Hierarchy extensions to Atom specify operations for creating, updating, and removing AtomPub Collections using existing AtomPub methods and extensions to Atom syntax... Feed Classification: AtomPub defines Feed, Entry, and Collection resources in the Atom syntax (RFC 4287). The hierarchy extensions to Atom are designed for use with unmodifiable Atom Feeds as well as with AtomPub Collections. The extensions in this specification define two specialized kinds of Feeds -- master Feed and detail Feed. Both are represented as Atom Feed Documents..."

Commentary: Julian Reschke noted that "there is overlap with the AtomPub bindings in CMIS (see CMIS working draft version .61) would be totally great if we could find out whether a single set of extensions would be sufficient..." Specification co-editor Nikunj Mehta clarified: "There is a good chance we will harmonize the names and semantics of the link relations and h:role attribute between the hierarchy I-D and CMIS. However, I want to clarify that the hierarchy-ID doesn't define entry types in a way that can be compared with CMIS entry types directly. The h:role concept is used only in the app:collection elements to control publishing of new entries only. On the contrary, CMIS specifies hard typing for entries that stays with the entry for as long as it is alive." [Note: Bill de hOra and Ashish Motivala reviewed early drafts of this Internet Draft and helped strengthen the text and make it easier to read.]

See also: Atom references

Basic and Advanced XML Schema Patterns for Databinding Version 1.0
Jonathan Calladine, George Cowe (et al, eds), W3C Working Group Notes

As part of the W3C Web Services Activity, members of the XML Schema Patterns for Databinding Working Group have published two Notes on Schema patterns. As presented in the Notes, "Schema patterns describe the ways people use XML for common data structures in programming languages. The data structures described are intended to be independent of any particular programming language, database or modelling environment. Basic XML Schema Patterns for Databinding Version 1.0 provides a set of basic XML Schema 1.0 patterns known to be interoperable between state of the art databinding implementations. The patterns may be used to describe XML 1.0 representations of commonly used data structures. The data structures described are intended to be independent of any particular programming language, database or modelling environment. Authors of XML Schema 1.0 documents may find these patterns useful in providing a better user experience for consumers of their schemata using databinding tools. Whilst it is not possible to guarantee that schemata produced using these patterns will give a good user experience with the universal set of databinding tools, the patterns contained in this specification have been all been tested with a number of different tools covering a variety of different programming languages and environments. Implementers of databinding tools may find these patterns useful to represent simple and common place data structures. Ensuring tools recognize at least these simple XML Schema 1.0 patterns and present them in terms most appropriate to the specific language, database or environment will provide an improved user experience when using databinding tools.

The Note Advanced XML Schema Patterns for Databinding Version 1.0 was created using evidence and experience gained examining the interoperability of a significant number of state of the art databinding implementations using a test suite, as presented in the Advanced Patterns Implementation Report and a collection of implementation reports including the collection of patterns detected from the wild.

See also: Advanced XML Schema Patterns

Day Software and Nuxeo Support Apache Chemistry Project for CMIS
Staff, Nuxeo and Day Software Joint Announcement

Content management vendors Day Software and Nuxeo have joined forces on the Apache Software Foundation's (ASF) Chemistry incubator project, which aims to produce a generic, open source reference implementation of the CMIS standard. CMIS is designed to benefit the growing number companies looking for a standards-based API to access documents stored in a wide-variety of ECM repositories. Both companies will be discussing their joint work on Apache Chemistry in an upcoming webinar on May 26, 2009...

As an industry-led movement towards a new content management standard, CMIS represents an ideal candidate for a community-driven open source project supported by leading ECM vendors to create a common reference implementation that can be liberally incorporated into their product stacks with the business-friendly Apache licensing model. As founding members of the project, both Day Software and Nuxeo have contributed their own bespoke implementations of CMIS to create a common, unified implementation to create a larger, more vibrant developer community around CMIS that avoids risks associated with vendor lock-in... The proposed CMIS standard has re-ignited interest and demand in content management standards, a movement initiated with the ratification of the industry's first content management standard, JSR-170 and the Apache Jackrabbit project.

Day Software and Nuxeo, whose product offerings both leverage the Apache Jackrabbit open source core, see continued collaboration within the ASF on Apache Chemistry as a natural extension of their continuing work on driving content management standards. Through Apache Chemistry, Day and Nuxeo look to build broad community participation in driving a common implementation of CMIS that can support any enterprise content repository, including any repository compliant with the JSR-170 standard. With the same open, collaborative model as OASIS specification process, Apache Chemistry promises to accelerate the development, ratification, and adoption of the CMIS standard, a goal that Nuxeo and Day both see as being important to continued growth of the ECM and WCM industry...

See also: the Apache Chemistry news story


XML Daily Newslink and Cover Pages sponsored by:

IBM Corporation
Microsoft Corporation
Oracle Corporation
Sun Microsystems, Inc.

XML Daily Newslink:
Newsletter Archive:
Newsletter subscribe:
Newsletter unsubscribe:
Newsletter help:
Cover Pages:

Hosted By
OASIS - Organization for the Advancement of Structured Information Standards

Sponsored By

IBM Corporation
ISIS Papyrus
Microsoft Corporation
Oracle Corporation


XML Daily Newslink
Receive daily news updates from Managing Editor, Robin Cover.

 Newsletter Subscription
 Newsletter Archives
Globe Image

Document URI:  —  Legal stuff
Robin Cover, Editor: