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: June 30, 2008
XML Daily Newslink. Monday, 30 June 2008

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

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

Service-Oriented Architecture End-to-End Resource Planning (SOA-EERP) TC
OASIS, Staff Announcement

OASIS has issued a Call for Participation in a newly formed Technical Committee "Service-Oriented Architecture End-to-End Resource Planning (SOA-EERP)." According to the TC's published statement of purpose: "As Service-Oriented Architecture (SOA) has matured as a development, deployment, and governance paradigm, the performance of SOA deployments has received increasing attention. 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 Technical Committee will focus on enablers for optimization. The enablers are, for example, definitions of the framework for representing the business process service rating terms, such how to represent cost, time, value, etc. Planned deliverables include: (1) Vocabulary, high level model, use cases, and requirements document; (2) Business Quality of Service specification—BQoS; (3) Service and business process extensions to BPMN, WS-BPEL, and CSA-BPEL; (4) Business Reliability and Reputation specification—WS-Rating; (5) Business Service Level Agreement specification—Business SLA; (6) Reference model for SOA Optimization Implementations. Representatives from the following corporate entities are listed as proposers and initial supporters of the the TC Charter and projected meeting schedule: Beijing CE Open Source Software Co. Ltd., Beijing Digital China, Beijing Redflag Chinese 2000 Co. Ltd., Beijing Sursen Co. Ltd., Beijing Tong Tech Co Ltd ChangFeng Alliance, Nortel, Redflag Software Co. Ltd., and UOML Alliance. The SOA-EERP Inaugural TC Meeting will be held on Wednesday, August 06, 2008.

See also: the SOA-EERP web site

AtomTriples: Embedding RDF Statements in Atom
Mark Nottingham and Dave Beckett (eds), IETF Internet Draft

A version -00 Internet Draft for "AtomTriples: Embedding RDF Statements in Atom" has been published through the IETF process. specification describes AtomTriples, a set of Atom (RFC 4287) extension elements for embedding RDF statements in Atom documents (both element and feed), as well as declaring how they can be derived from existing content. Statements can be embedded directly as RDF/XML using the at:md element at the feed or entry level. Additionally, a feed can declare that specific Atom elements (or extensions) can be parsed into RDF statements using the 'at:feedmap' element (for metadata attached to a feed) or an 'at:entrymap' element (for metadata attached to entries). The semantics of a property that appears in both places (e.g., in a feed-level 'at:md' as well as derived from a 'at:feedmap') is undefined; presumably, they would be added to the model as two separate statements. Likewise, the mechanics of combining metadata from multiple instances of the same entry, or from multiple feed documents, is out of the scope of this specification. Unless specified otherwise, AtomTriples elements may contain foreign markup, which should be handled according as it is in the Atom syndication format. RDF statements can be directly embedded in Atom feeds and entries as RDF/XML using the 'at:md' element. The 'at:md' element may occur as a child of atom:feed or atom:entry, and contains any number of RDF statements which must be serialised as RDF/XML. It may occur in a given context any number of times. The subject of these statements is, by default, the value of the atom:id element in the same context ('atom:element' or 'atom:feed'). However, this behaviour may be overridden by specifying the subject attribute. After the subject is determined, the contents should be processed as a 'propertyEltList', per the W3C Recommendation "RDF/XML Syntax Specification (Revised)." When present, the subject attribute indicates how to derive the RDF subject of statements sourced from the element it is attached to. It must contain a URI which must be interpreted as a link relation; the first such occurrence of an atom:link element in the same context as its parent element with that relation (in lexical order) will indicate the URI to use as the subject. All XML elements in the specification use the the namespace URI ''.

See also: Atom references

SOAP Node Basics
Rob Henley and Matthew Golby-Kirk, IBM developerWorks

SOAP nodes send and receive SOAP-based Web services messages, allowing a message flow to interact with Web service endpoints. SOAP nodes are used together to implement common Web services scenarios and are generally the best choice for new message flows working with Web services. SOAP nodes, which are configured using Web Services Description Language (WSDL) 1.1, support SOAP-based Web services, sending and receiving messages that can be plain SOAP (version 1.1 or 1.2), SOAP with Attachments (SwA), or MTOM (Message Transmission Optimization Mechanism). They combine message transport and SOAP semantics to support a consistent SOAP domain logical tree format and the next-generation Web services standards WS-Security and WS-Addressing. Transport-specific nodes, such as HTTPInput and HTTPReply, are still useful in certain circumstances. For instance, you can use them if you have existing flows using these nodes and you don't foresee any requirement for WS-Addressing or WS-Security support, or you don't have a WSDL definition and don't intend to create one—maybe because you're using a non-SOAP-based Web service technology like XML Remote Procedure Call (XML-RPC) or Representational State Transfer (REST). But if you're creating a new message flow and using WSDL, then the SOAP nodes offer a more complete solution. This four-part series describes the SOAP nodes, the logical tree for the new SOAP domain, and details of configuration and runtime behavior. In this first article, you learn about the basic use of the nodes. You should have a general familiarity with SOAP-based Web services and WSDL to follow along with this article series. Article Part 2 covers the SOAP logical tree and its use.

See also: Web Services Addressing 1.0 - Core

Public Comment Invited on OpenGIS Web Coverage Service Extensions
Staff, Open Geospatial Consortium Announcement

The Open Geospatial Consortium, Inc. (OGC) membership approved a 30-day public comment period for a revision to the OpenGIS Web Coverage Service (WCS) Interface Standard. The revision includes two extensions to WCS: the WCS 1.1 Transaction Extension and the Web Coverage Processing Service Processing (WCPS) Extension. The WCS Interface Standard specifies an application programming interface (API) for requesting coverage data, such as imagery, from one or more distributed sources. A WCS provides access to potentially detailed and rich sets of geospatial information, in forms that are useful for client-side rendering and input into scientific models and other clients. A WCS provides access to potentially detailed and rich sets of geospatial information, in forms that are useful for client-side rendering, multi-valued coverages, and input into scientific models and other clients. The WCS may be compared to the OGC Web Map Service (WMS) and the Web Feature Service (WFS); like them it allows clients to choose portions of a server's information holdings based on spatial constraints and other criteria. The WCS 1.1 Transaction Extension defines how WCS clients can request that a WCS server import one or more new coverages into that server, update existing coverages, and/or delete existing coverages. The WCPS Extension adds a raster expression language to WCS which allows analysis and processing of multi-dimensional grid coverage data over the World Wide Web. Resulting coverages can be transmitted directly or made available for download by URLs communicated to the client.

See also: Geography Markup Language (GML)

New W3C Working Drafts: Protocol for Web Description Resources (POWDER)
Phil Archer, Kevin Smith (et al., eds), W3C Technical Report

Members of the W3C Protocol for Web Description Resources (POWDER) Working Group have released Working Drafts for "POWDER: Grouping of Resources" and "POWDER: Description Resources." The Protocol for Web Description Resources (POWDER) facilitates the publication of descriptions of multiple resources such as all those available from a Web site. These descriptions are always attributed to a named individual, organization or entity that may or may not be the creator of the described resources. This contrasts with more usual metadata that typically applies to a single resource, such as a specific document's title, which is usually provided by its author. POWDER takes a very broad approach so that it is possible for both the resource creator and third parties to make assertions about all kinds of things, with no architectural limits on what they are making claims about. For example, medically proficient organizations might be concerned with properties of the agencies and processes that produce Web content (e.g. companies, people, and their credentials). Equally, a 'Mobile Web' application might need to determine the properties of various devices such as their screen dimensions, and those device types might be described with such properties by their manufacturer or by others. (1) The "POWDER: Description Resources" document sets out how Description Resources (DRs) can be created and published, how to link to DRs from other online resources, and, crucially, how DRs may be authenticated and trusted. The aim is to provide a platform through which opinions, claims and assertions about online resources can be expressed by people and exchanged by machines. (2) "POWDER: Grouping of Resources" describes how sets of IRIs can be defined such that descriptions or other data can be applied to the resources obtained by dereferencing IRIs that are elements of the set. IRI sets are defined as XML elements with relatively loose operational semantics. This is underpinned by the formal semantics of POWDER which include a semantic extension, both defined separately. A GRDDL transform is associated with the POWDER namespace that maps the operational to the formal semantics.

See also: POWDER Grouping of Resources

Sling: Apache Looks to Bring Fun Back to Java
Paul Krill, InfoWorld

Apache has announced the first release of Apache Sling, an open-source Web framework that brings content into the Web and provides a platform to manage and upgrade content. Santi Pierini, senior vice president of marketing at Day Software: ""We're trying to create a Web framework that makes it easier to build what they call RESTful apps. With Sling, a content delivery framework and content access capabilities are provided so that developers not have to code these themselves. Sling can be used for building various types of Web applications, including wikis, blogs, customer self service, and digital asset management systems" According to the project description: "Apache Sling (currently in incubation) is a web framework that uses a Java Content Repository, such as Apache Jackrabbit, to store and manage content. Sling applications use either scripts or Java servlets, selected based on simple name conventions, to process HTTP requests in a RESTful way. The embedded Apache Felix OSGi framework and console provide a dynamic runtime environment, where code and content bundles can be loaded, unloaded and reconfigured at runtime. As the first web framework dedicated to JSR-170 Java Content Repositories, Sling makes it very simple to implement simple applications, while providing an enterprise-level framework for more complex applications. Sling is offered in four "flavors": (1) A standalone application featuring a JAR (Java Archive) file with everything needed to get started with Sling; (2) A Web application that can be dropped into a Web container; (3) A full source package; (4) Maven artifacts. Maven is Apache's software project management and comprehension tool.

See also: Sling

W3C Report: Role of Mobile Technologies in Fostering Social Development
Staff, W3C Announcement

W3C announced the publication of a report on the June 2008 Workshop on the "Role of Mobile Technologies in Fostering Social Development." Workshop participants discussed how numerous available services on mobile phones could help people in underserved regions. Discussion underlined the need for a concerted effort among all the stakeholders (including practitioners, academics, regulators, and mobile industry) to build a shared view of the future of the mobile platform as a tool to bridge the digital divide. The Workshop was jointly organized by W3C and, with the generous support of UNDP and Fundacion CTIC (Gold Sponsors), Opera Software and (Silver sponsors). This work takes place under the European Union's 7th Research Framework Programme (FP7), part of Digital World Forum project. The different findings identified during the workshop will now be transferred to the new W3C group Mobile Web for Social Development, which will investigate them further, and build consensus around the most appropriate actions to engage the relevant stakeholders in order to seed the development and creation of ICT services exploiting the full potential of the mobile platform and the Web. The discussion around this roadmap, and public feedback, will be gathered and documented as the group moves forward, and also through the organization of a new workshop at beginning of 2009, most likely somewhere in sub-saharan Africa.

See also: the Report Executive Summary

OOXML Projects Bolster Microsoft's Interoperability Efforts
Elizabeth Montalbano, Network World

Microsoft has unveiled projects to improve data portability between Office 2007 and other document file formats, including the design of a new translator for exchanging OOXML (Office Open XML) and HTML documents. The company also posted the 1.0 version of technical documentation for protocols in Office and other software that enable those applications to interact with third-party programs. The moves are part of a companywide commitment, unveiled in February, to foster interoperability, an initiative launched under pressure from an ongoing antitrust case in the European Union and competition from Linux and open-source software. On Monday Microsoft also outlined some efforts it's been making to work in the community to help third parties develop interoperable technologies and promote data portability between its products and others, notably between its controversial OOXML file format and other formats for exchanging documents. For example, the company is working on a new translator to read from documents in the Open XML file format to HTML. The company has posted information about the project on its Codeplex site. Microsoft has said it will support a rival file format and ISO standard, ODF (OpenDocument Format), in Office 2007 in a service pack to be released early next year. It has slated support for OOXML in Office for the next version of Office, code-named Office 14, but no official release date has been set for that product. Many expect it will be released next year as well, however. In another data-portability effort, Microsoft is working with Beihang University in Beijing to develop translators between Uniform Office Format (UOF), an open standard in China for office documents, and Microsoft Excel and PowerPoint so users have more options to open and save UOF documents in Microsoft Office 2007 and 2003. Also on Codeplex is information about a project to develop PowerTools PowerShell commands for OpenXML to enable IT managers to perform document management tasks. PowerShell is a command-line shell and task-based scripting technology for Windows Server that provides control and automation of system administration tasks.

See also: the announcement

Zembly: Sun Sponsors Social Apps Platform
Paul Krill, InfoWorld

Sun Microsystems is sponsoring a collaborative environment for building and hosting social applications that would run on environments like Facebook and OpenSocial. Called zembly, the project currently is in a private beta stage. With zembly, applications can be developed in whatever language is preferred and run on different types of devices, including mobile and desktop systems. Zembly serves as sort of a Wikipedia for social applications, according to the zembly site. Participants can author social applications using a browser, collaborate with others, use popular Web APIs to build applications, and publish these applications to multiple social platforms. Applications developed with zembly consist of widgets and services. Users only need to some basic scripting with JavaScript and HTML. And the Web serves as a "palette..." Participants receive their own profile that can be customized and then accessed by others. Services furnished by Web APIs can be integrated into zembly. Web API providers already doing so include Amazon Web Services, Dapper, Flickr, Google, Meebo, Twitter, Yahoo Developer Network, YouTube,, and Zvents. Sun technologies powering zembly include the Solaris OS, Java, Glassfish application server and the MySQL database. Sun's cloud computing platform also is used. Todd Fast, who has served as a Sun engineer, is chief architect for zembly. From the web site description: "Using just your browser and your creativity, and working collaboratively with others, you create and publish Facebook apps, Meebo apps, OpenSocial apps, iPhone apps, Google Gadgets, embeddable widgets, and other social applications... At zembly, you can easily and instantly... (1) author social applications using your browser; (2) participate and collaborate with others around live, editable code; (3) use the richness of popular web APIs to create your applications; (4) publish your social applications to multiple social platforms with a single click..."

See also: the Zembly web site

Creative Commons Global Case Studies Project
Staff, Creative Commons Announcement

Creative Commons (CC), in association with Creative Commons Australia, has officially announced the release of the Case Studies Project, which is a large-scale community effort to encourage all to explore and add noteworthy global CC stories. Creative Commons provides free tools to allow copyright-holders to clearly show rights associated with creative works, and now this project shows how notable adopters like author Cory Doctorow, web video-sharing company, and open film project "A Swarm of Angels" have successfully used CC licenses. This wiki project aims to examine the motivations and outcomes of CC license adoption in a variety of different situations and highlights the work being done by the creators and content aggregators in the CC community. Anyone can explore the global CC landscape by browsing with a variety of filters including the license-types used, the media created, and whether the project curates or creates material. Some examples include the Google Summer of Code program, the Big Buck Bunny 2nd Open Source 3D animation led by the Blender Foundation, and Sony's EyeVio video sharing social network service. Beyond easily viewing the compilation, the Case Studies Project encourages users to edit the wiki and add innovative and noteworthy CC projects happening in jurisdictions worldwide. To lower the barriers for participation, the Case Studies Project provides contributors with an easy form to enter data into the wiki and examples of other featured initiatives... The initiative will also find its way into the print medium regularly. Working with the user-generated Case Studies material, CC Australia is releasing "Building an Australasian Commons Booklet," the first of a number of planned printed publications based on the project. The book is a first attempt to chronicle the tales of the Australasian commons. Featuring over 60 case studies, it maps the current state of play surrounding free culture in the region. From private individuals to large corporations, the studies clearly show the mechanisms and motivations to share and experiment without the restrictions of the pre-digital era. Across the domains of democratic change, filmmaking, music, visual arts, libraries, museums, government, education and research, the book will explore how Australasian creators working with CC licensing are making their mark...

See also: Creative Commons Project

What Benevolent Dictator?
Ian Jacobs, W3C Blog

The contribution "What Benevolent Dictator?" comes from the "W3C Questions and Answers Blog - 'Join the Conversation with W3C Members, Staff and Contributors'"—at a URI which used to be associated with the home page for the Quality Assurance activity at W3C. This resource has since been broadened in scope and audience to become the Q&A weblog. The blog is intended to foster polite on-topic discussions. Ian writes: From time to time I hear people refer to Tim Berners-Lee as a "benevolent dictator." In most cases they utter the phrase through a smile, but I find the phrase distasteful. It is also inaccurate. The W3C process has evolved to reduce the central role of the Director. Without this evolution, W3C would not have been able to reach its current work capacity. Steve Bratt (the CEO) has taken on much of the management of the process. For Web architecture issues, the Technical Architecture Group (TAG) was chartered in 2001 to document principles of Web architecture and help resolve issues about Web architecture inside and outside W3C. A full-time staff of around 70 people help support the Director and CEO. The reality is that W3C has intentionally distributed decision-making responsibility to a number of parties in order to grow. Most importantly, most technical decision-making happens in the groups themselves. W3C operates as a decentralized community of collaborating groups. They function independently, but not in a vacuum. In a presentation to the W3C Advisory Committee in April of this year, Tim wrote: "Each group, whether or not in W3C, has a duty to act as a responsible peer to other groups, recognize it is part of a larger community, and to spawn independent subgroups to do cleanly defined parts of the work when the task is big." By coordinating, groups benefit through reviews of specifications, shared understanding with other communities, and useful architectural consistency... When there is disagreement over a group decision, the Director and CEO assess whether the group has duly considered the minority views and whether the technical reasoning behind the decision is sound. In short: has the group done its job? When presented with a Formal Objection, the Director makes an informed decision, siding at times with the majority, and at other times with the dissenter. Members not satisfied with a Director decision can appeal it. It only takes 5% of the Membership to overrule Tim, hardly a dictatorship.

See also: the W3C Blog


XML Daily Newslink and Cover Pages sponsored by:

IBM 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: