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: October 27, 2010
XML Daily Newslink. Wednesday, 27 October 2010

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

This issue of XML Daily Newslink is sponsored by:
Microsoft Corporation

OASIS SOA-EERP Technical Committee Releases Public Review Drafts
Staff, OASIS Announcement

Members of the OASIS Service-Oriented Architecture End-to-End Resource Planning (SOA-EERP) Technical Committee have approved three Committee Draft specifications for public review through November 11, 2010. OASIS encourages feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of OASIS work. The SOA-EERP TC was chartered to develop optimizations for Business Quality of Service (BQoS): "End-to-End Resource Planning (EERP) applies service discovery, composition, simulation, and optimization techniques in a novel way to improve business results. As the software industry has applied SOA to eBusiness deployments, self-optimizing systems as exemplified by EERP have become more feasible and necessary... Different deployments of services onto a business process have varying business value. For example, a shipper might offer faster but more expensive service. EERP models the business process and the range of potential services, then guide the selection and deployment of services based on the overall end-to-end business value."

The SOA-EERP Business Quality of Service Version 1.0 specification defines the XML vocabulary for business quality of service (bQoS), one of three Specifications for end-to-end resource planning (EERP). Business quality of service describes the business-related characteristics or attributes of a service. According to OASIS Reference Model for Service Oriented Architecture (SOA-RM), the Service Oriented Architecture (SOA) is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. The service within SOA is a mechanism to enable access to one or more capabilities, where the access is provided using a prescribed interface and is exercised consistent with constraints and policies as specified by the service description. This specification further defines the Business Quality of Service for the services that is defined in SOA-RM, within the EERP technology. The applications of this specification are any kind of business services, and they are not limited to only Web Services... Modeling the business characteristics of a service is a prerequisite for estimating the business value of the process that uses those services. The business characteristics of the service defined in this bQoS specification will enable EERP to determine the varieties of optimization to be supported, and to select optimal end-to-end solution..."

SOA-EERP Business Service Level Agreement Version 1.0 specifies "the XML vocabulary for business service level agreement (bSLA), one of three Specifications for end-to-end resource planning (EERP). Business service level agreement describes the agreement between two parties, service requester and service provider, on business-related characteristics or attributes of a service. Modeling the business service-level agreements to manage and evaluate services and establishing agreements about the business service is essential to long-term value chain improvement. The details of the business service level agreement defined in this bSLA specification will enable EERP to determine the varieties of optimization to be supported, and to manage the end-to-end business process... The bSLA is different than the SLA (Service Level Agreement) in the software/IT world. The bSLA in this specification is the contact between the service requester and the service provider, and the SLA is the contract between the service provider and the network/system provider..."

The specification SOA-EERP Business Rating of Service Version 1.0 defines an "XML vocabulary for business rating, one of three Specifications for end-to-end resource planning (EERP). Business rating describes the business-related rating and credentials for a service. The BRating is the root element of Business Rating for EERP which is for business reliability and reputation of the service and its services provider. It can have one or more of the following elements: (1) ListOfRating element is for the rating aspect of service which is provided by rating provider and measured in terms of rates for the service. (2) Credentials element is for the rating aspect of service which is measured in terms of credentials for the service that the service provider owns or holds. (3) Any additional elements for the rating aspect of service; for example, this could be one or more elements of 'Performance:QualityAssertionEvaluation' that will provide a mechanism for Service Rating Entities to render their evaluation for how well the provider fulfills the Quality Assertion(s) of its service..."

See also: the OASIS SOA-EERP Technical Committee      [TOC]

Open Data Center Alliance: Big Businesses Get Serious About an Open Cloud
Ted Samson, InfoWorld

"If you were a business operating in the perfect cloud computing world, everything would work in harmony. The stuff under your roof or hosted elsewhere would all operate with plug-and-play simplicity, thanks to open standards. You wouldn't be shackled to any one vendor because its products or services weren't 'optimized' to support another vendor's.

Such is the vision of the newly formed Open Data Center Alliance (ODCA), a group headed by large, deep-pocketed companies, including BMW, China Life, Deutsche Bank, JPMorgan Chase, Lockheed Martin, Marriott International, National Australia Bank, Shell, Terremark, and UBS. Notably absent from the group's headline members is any of the big IT vendors—except Intel, which is serving as the alliance's technical adviser..."

According to the Open Data Center Alliance web site: "the Open Data Center Alliance is a consortium of leading global IT managers with over $50 billion in collective IT spending who are dedicated to defining future data center and cloud usage models in an open, industry-standard and multi-vendor fashion. Over 70 members have joined the Open Data Center Alliance... Members have come together to find answers to the [cloud] challenges, and are creating a vendor-agnostic Usage Model Roadmap to guide us as we define open, interoperable, standards-based solutions to provide our businesses with greater efficiency, reduced costs, less complexity, increased flexibility, more choice and faster time to market. The Usage Model Roadmap defines usage model requirements and reference architectures to resolve key IT challenges and fulfill cloud infrastructure needs into the future. This vendor-agnostic roadmap serves helps guide member planning of future data center deployments, and relies on open, interoperable, industry-standard solutions...

In support of its mission, the Alliance has established five Technical Workgroups focused on Infrastructure, Management, Security, Services, and Government & Ecosystem. Each Workgroup will fully define the requirements of each prioritized usage model toward the future delivery of a detailed technical documentation suite to be utilized by vendors and members as guidance for deployments. In addition, the working groups are chartered to finalize the current 0.5 Roadmap with a public delivery of the Roadmap and initial usage models in Q1, 2011..."

See also: the Open Data Center Alliance announcement      [TOC]

W3C Last Call Review: SOAP Over Java Message Service 1.0
Phil Adams, Peter Easton, Eric Johnson (et al), W3C Technical Report

The W3C SOAP-JMS Binding Working Group has published a Last Call Working Draft for the specification SOAP Over Java Message Service 1.0. This document is based on the W3C Submission 'SOAP Over Java Message Service 1.0'. A list of changes is available in H Change Log, and the status of issues raised since the previous version can be seen in the Working Group's disposition to comments document. The authors of this document consider it to be stable, and invite reviewers and implementors to send comments to the public mailing list before the deadline of November 19, 2010. The Working Group may request to move to W3C Proposed Recommendation after the end of the Last Call period.

The document specifies how SOAP binds to a messaging system that supports the Java Message Service (JMS). Binding is specified for both SOAP 1.1 and SOAP 1.2 (SOAP 1.2 Messaging Framework) using the SOAP 1.2 Protocol Binding Framework. The specification also describes how to use WSDL documents to indicate and control the use of this binding... The work described in this and related documents is aimed at a set of standards for the transport of SOAP messages over JMS. The main purpose is to ensure interoperability between the implementations of different Web services vendors. This will also enable customers to implement their own Web services for part of their infrastructure, and to have this interoperate with vendor provided Web services. The main audience will be implementers of Web services stacks; in particular people who wish to extend a Web services stack with an implementation of SOAP/JMS. This will enable them to write a SOAP/JMS implementation that will interoperate with other SOAP/JMS implementations, and that will not be dependent on any specific JMS implementation.

A motivational example is a customer who has different departments that use Web services infrastructure from two different vendors, VendorA and VendorB. The customer has a need for reliable Web services interaction between the departments. Where both these vendors provide support for SOAP/JMS according to this standard, it ought be possible for a client running using VendorA to interoperate with a service using VendorB.

The standards will also be of interest to providers of Web services intermediary services such as routing gateways; or SOAP/HTTP to SOAP/JMS gateways. We do not discuss any details of how such gateways might be designed and configured, but adherence to the standard will help the gateway ensure proper interoperation with SOAP/JMS clients and services..."

See also: the W3C SOAP-JMS Binding Working Group      [TOC]

Location Conveyance for the Session Initiation Protocol
James Polk, Brian Rosen, Jon Peterson (eds), IETF Internet Draft

IETF participants have published an updated Standards Track Internet Draft for the specification Location Conveyance for the Session Initiation Protocol. The IETF Session Initiation Protocol (SIP) Working Group was chartered to maintain and continue the development of SIP (RFC 3261), and its family of extensions. SIP is a text-based protocol, similar to HTTP and SMTP, for initiating interactive communication sessions between users. Such sessions include voice, video, chat, interactive games, and virtual reality.

The "Location Conveyance for the Session Initiation Protocol" document defines an extension to the Session Initiation Protocol (SIP) to convey geographic location information from one SIP entity to another SIP entity. The extension covers end-to-end conveyance as well as location-based routing, where SIP intermediaries make routing decisions based upon the location of the user agent client.

From the Introduction: "Session Initiation Protocol (SIP) creates, modifies and terminates multimedia sessions. SIP carries certain information related to a session while establishing or maintaining calls. This document defines how SIP conveys geographic location information of a Target (Target) to a Location Recipient (LR). SIP acts as a Using Protocol of location information, as defined in RFC 3693.

In order to convey location information, this document specifies a new SIP header, the Geolocation header, which carries a reference to a Location Object. That Location Object may appear in a MIME body attached to the SIP request, or it may be a remote resource in the network... A Target could be a SIP user agent (UA), some other IP device (a router or a PC) that does not have a SIP stack, a non-IP device (a person or a black phone) or even a non-communications device (a building or store front). In no way does this document assume that the SIP user agent client which sends a request containing a location object is necessarily the Target. The location of a Target conveyed within SIP typically corresponds to that of a device controlled by the Target, for example, a mobile phone, but such devices can be separated from their owners, and moreover, in some cases the user agent may not know its own location... The location conveyance mechanism can also be used to deliver URIs point to such Location Servers where prospective Location Recipients can request Location Objects..."

See also: the IETF Session Initiation Protocol (SIP) Working Group      [TOC]

Proposed Charter for OASIS Business Document Exchange (BusDox) TC
Staff, OASIS Announcement

OASIS members have proposed the creation of a new Technical Committee with the provisional name "OASIS Business Document Exchange (BusDox) Technical Committee." As proposed, this TC would "define, enhance and maintain profiles of existing standards (from OASIS and elsewhere) that specify interfaces for a lightweight and federated messaging infrastructure supporting a 4-corner model of secure and reliable exchange of electronic documents..."

In addition to OASIS individual members, representatives of the following institutions have provided statements of support for the charter proposal: Denmark Ministry of Science, Technology & Innovation; Tradeshift Network Ltd; Sonnenglanz; Document Engineering Services; AITI - Associazione Italiana dei Tesorieri d'Impresa; WSO2.

Excerpt: "The BusDox TC does not replace existing messaging service standards. It provides a simplified interface independent of the various standards used for the exchange of documents... The foundation for the work are the specifications developed as part of the PEPPOL project, providing the infrastructure for public eProcurement in Europe. But the specifications can be used for any business processes. It is intended that the OASIS BusDox TC will become the maintenance forum for interfaces implemented by the PEPPOL project and similar infrastructure initiatives.

Proposed Committee Specifications will cover: (1) Profiles for a robust, secure, federated and lightweight addressing mechanism. (2) Profiles for one or more secure, trusted, asynchronous and reliable messaging protocols. The initial profile to be covered will be the START profile (Secure Trusted Asynchronous Reliable Transport). (3) A profile of a secure and reliable, lightweight messaging protocol, LIME (Lightweight Message Exchange). (4) A profile of ebMS 3.0, its multi-hop feature and AS4 profile. (5) Test and conformance suites aiding the development of interoperable implementations of the profiles..."

See also: archives of the OASIS Charter Discussion list      [TOC]

Balisage 2010 Permanent Proceedings Now Available Online
B. Tommie Usdin, Community Announcement

An announcement has been published for the final, complete, permanent proceedings of "Balisage: The Markup Conference 2010" and "International Symposium on XML for the Long Haul." In addition, the Balisage 2011 conference dates are being announced: August 01, 2011 for the pre-conference symposium, and August 2-5, 2011 for "Balisage: The Markup Conference 2011."

The online Proceedings includes a cumulative Topic Index (topical assignments given to the papers, each with the papers to which it is assigned), Author Index, Series Master Bibliography, and Series Policy on Stability and Persistence. The Series Master Bibliography lists in order of their primary authors, including Balisage: The Markup Conference 2008 (August 12 - 15, 2008); International Symposium on Versioning XML Vocabularies and Systems (August 11, 2008); Balisage: The Markup Conference 2009 (August 11 - 14, 2009); International Symposium on Processing XML Efficiently: Overcoming Limits on Space, Time, or Bandwidth (August 10, 2009); Balisage: The Markup Conference 2010 (August 3 - 6, 2010); International Symposium on XML for the Long Haul: Issues in the Long-term Preservation of XML (August 2, 2010)

Balisage "is an annual conference devoted to the theory and practice of descriptive markup and related technologies for structuring and managing information. The conference takes its name from the French term for 'markup', in a friendly gesture towards the city of Montreal, where for years people interested in markup have met each August for informed technical discussion, occasionally impassioned debate, good coffee, and the incomparable ambience of one of North America's greatest cities. The organizers welcome anyone and everyone interested in open information, reusable documents, vendor and application independence, and the other benefits of descriptive markup. Participants typically include XML users, librarians, archivists, computer scientists, XSLT and XQuery programmers, implementers of XSLT and XQuery engines and other markup-related software, Topic-Map enthusiasts, semantic-Web evangelists, members of the working groups which define the specifications, academics, industrial researchers, representatives of governmental bodies and NGOs, industrial developers, practitioners, consultants, and the world's greatest concentration of markup theorists. Discussion is open, candid, and unashamedly technical. Content-free marketing spiels are forbidden.

Persistence: "The Balisage Series on Markup Technologies is envisaged as a long-lived research archive supporting the markup theory and practice community. In order to support this mission, the owners will preserve indefinitely, to the best of our ability, the availability of the material in this series, at the URIs currently assigned. These URIs are intended to be permanent, and links to this material may be expected not to break, at least as long as the publisher remains in existence and the current URI infrastructure is available..."

See also: the Balisage Series on Markup Technologies, Master Bibliography      [TOC]

HTML5 Is Taking Off
Abel Avram, InfoQueue

According to Avram, "54% of the video published on the Internet is currently available in the HTML5 format, according to MeFeedia, and new HTML5 editing tools are announced by Adobe and Sencha, showing that HTML5 is taking off.

MeFeedia, an online video portal, has conducted a study to find out how much HTML5 content is out there. Having a video index with millions of entries and covering over 33,000 video publishers, the study concluded that online video content available as HTML5 has doubled over the past 5 months from 26% to 54%, and it has grown 5 times since the beginning of the year when it was only 10%...

In the same time, new visual HTML5 editors are announced. One of them is Edge from Adobe, a prototype tool addressed to Photoshop, Illustrator and Flash Pro users for creating HTML5 animations...

Another tool recently announced is Sencha Animator, a GUI-based editor for interactive designers interested in creating HTML5 animations. Animator was created with Ext JS, a cross-browser JavaScript library providing widgets for RIA applications, and it generates pure CSS3 animation code working with any JS library..."

See also: the HTML5 Draft      [TOC]


XML Daily Newslink and Cover Pages sponsored by:

IBM Corporation
ISIS Papyrus
Microsoft Corporation
Oracle Corporation

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: