XML and Web Services In The News - 27 February 2006
Provided by OASIS |
Edited by Robin Cover
This issue of XML.org Daily Newslink is sponsored by SAP
HEADLINES:
Open-Source 'Higgins' Project Takes on Microsoft's InfoCard
Darryl K. Taft, eWEEK
IBM, Harvard Law School's Berkman Center for Internet & Society, Novell and Parity Communications on Feb. 27 announced that they are contributing code to an open-source initiative, code-named the Higgins Project, which will help give people more control over their personal online identity information. The Higgins Project announcement, which comes just weeks after Microsoft announced a similar initiative, called InfoCard, at the RSA Conference, is for a user-centric identity management system where users actively manage and control their online personal information for things like bank accounts, telephone and credit card numbers, or medical and employment records. The open-source Eclipse Foundation is heading up the effort and is promoting the use of open standards, so Higgins will support Linux as well as Windows or any operating system, or any identity management system.
See also: Higgins announcement
An Introduction to WSDM
Vaughn Bullard, Bryan Murray, Kirk Wilson (eds), OASIS Committee Draft
The WSDM (Web Services Distributed Management) standard is more than a
management protocol, SNMP trap handler, or simple distributed management
technology. As a standard, it seeks to unify management infrastructures
by providing a vendor, platform, network, and protocol neutral framework
for enabling management technologies to access and receive
notifications of management-enabled resources. Though built upon a
standardized suite of XML specifications, it provides features to
enable resources that other proprietary management technologies do not.
It can be used to standardize management for many devices, from network
management devices as well as consumer electronic devices, such as
televisions, digital video disc players, and PDAs. This Introduction
provides an overview to the WSDM specification and its associated
sub-specifications. In addition, it covers the historical motivations
for the creation of WSDM as well as the motivations for why would want
to use WSDM as a management specification within their information
technology environment. The introduction is directed towards a wide
audience of architects, developers, systems and software integration
specialists and users. The introduction provides simple examples of
how WSDM can be used in end devices to give the reader ideas of how
the WSDM standard can be used in the real world. It it is intended
to provide an easily read and understood summary of the fundamentals
of creating and using WSDM-compliant management applications and
manageable resources.
See also: WSDM Primers
Building Workflow Applications with XML and XQuery
Michael Kay, Stylus Studio Online Tutorial
XML encourages you to change the way you think about application design.
Rather than starting in the traditional way by designing a central
database for storing the data, it encourages you to think in terms of
the data as it moves around the system: a process-oriented rather than
data-centric approach. This works particularly well when you design
the application as a document-based workflow, perhaps mimicking the
design of an existing business process based on paper documents.
Michael Kay argues that the bulk of the application logic required for
typical XML workflow applications can be written in high-level XML
processing languages, notably XSLT and XQuery, with individual
components linked together in a pipeline processing framework. By
writing the logic in these high-level languages (rather than say Java
or C#), the biggest benefit you gain is flexibility and adaptability
-- the ability to change the application in response to changing
business needs. XML gives you this flexibility in terms of data design;
don't lose it by writing applications that freeze the data structure
into Java or C# classes. This tutorial on Building XML Workflow
Applications covers the following topics: (1) Modeling XML Workflow
Applications; (2) Choosing a Centralized or Decentralized Architecture;
(3) The Life-Cycle of a Document; (4) Finding Resources using
Directory Services Markup Language; (5 Writing XML Workflow Applications.
The Future of HTML, Part 2: XHTML 2.0
Edd Dumbill, IBM developerWorks
In this two-part series, Edd Dumbill examines the various ways forward
for HTML that Web authors, browser developers, and standards bodies
propose. This series covers the incremental approach embodied by the
WHATWG specifications and the radical cleanup of XHTML proposed by the
W3C. Additionally, the author gives an overview of the W3C's new Rich
Client Activity. Here in Part 2, Edd focuses on the work in process at
the W3C to specify the future of Web markup. The XHTML 2.0 approach
offers a cleaned-up vocabulary for the Web where modular processing of
XML, CSS, and ECMAScript is rapidly becoming the norm. Embedded devices
such as phones and digital TVs have no need to support the Web's legacy
of messy HTML, and are free to take unburdened advantage of XHTML 2.0
as a pure XML vocabulary. Additionally, the new features for
accessibility and internationalization make XHTML 2.0 the first XML
document vocabulary that one can reasonably describe as universal, and
thus a sound and economic starting point for many markup-based endeavors.
See also: Part I
XFire: Open Source, High Performance SOAP
Dan Diephouse, XFire Software Announcement
The Codehaus XFire team is proud to announce their 1.0 release! XFire is
an open source Java SOAP framework built on a high performance,
streaming XML model. XFire includes support for web service standards,
an easy to use API, Spring integration, JBI support, and plugable
bindings for POJOs, JAXB, and XMLBeans. XFire 1.0 includes support for
WSDL 1.1, SOAP 1.1 and 1.2, WS-Addressing, WS-I Basic Profile 1;
Pluggable bindings for POJOs, XMLBeans, JAXB 1.1, JAXB 2.0, and Castor
support; Support for many different transports - HTTP, JMS, XMPP,
In-JVM, etc.; Spring, Pico, Plexus, Loom, and Yan support; JBI Support;
Embeddable and Intuitive API; Client and server stub generation; and JSR
181 2.0 API to configure services via Java 5 and 1.4 (Commons attributes
JSR 181 syntax).
XML.org is an OASIS Information Channel sponsored by Innodata Isogen and SAP.
Use http://www.oasis-open.org/mlmanage to unsubscribe or change an email address. See http://xml.org/xml/news_market.shtml for the list archives. |