|
XML and Web Services In The News - 15 June 2006
Provided by OASIS |
Edited by Robin Cover
This issue of XML.org Daily Newslink is sponsored by SAP
HEADLINES:
IBM Hands Over More WSDM Code to Open Source
China Martens, InfoWorld
IBM Corp. is contributing more code to the open-source community based
on the WSDM (Web Services Distributed Management) standard. WSDM, often
pronounced "wisdom," is an OASIS standard that helps manage a wide
variety of hardware and software and brings more autonomic or self-
healing capabilities to systems management software used in data centers.
Automating more aspects of systems management should help to lower IT
support costs as well as increase technology utilization as systems
bottlenecks become easier to identify. IBM is making its implementation
of the Common Event Base framework for WSDM freely available to the
open-source Apache Muse Project. The vendor previously contributed WSDM
development tools to the Eclipse Foundation. With more than 30 IBM
products already incorporating WSDM, IBM thought the time was right to
open source more of its code relating to the standard.
See also: WSDM references
Companies Demonstrate Interoperability of Service Provisioning Markup Language (SPML) 2.0 Standard
OASIS Staff, Consortium Announcement
OASIS announced that six international companies joined together at the
Burton Catalyst 06 conference in San Francisco to demonstrate
interoperability of the Service Provisioning Markup Language (SPML)
version 2.0. Developed by the OASIS Provisioning Services Technical
Committee, SPML is an approved OASIS Standard that lets companies
manage the provisioning and allocation of identity information and
system resources within and between organizations. The Catalyst
demonstration scenarios involve a group of companies that outsource
various services to application service providers (ASPs). Each ASP
publishes a SPML interface for provisioning accounts. Each company uses
a SPML client that makes provisioning requests to the ASPs as needed.
The roles of company and ASP are interchangeable among all six InterOp
participants. Members of the OASIS Provisioning Services TC include
representatives of BEA Systems, BMC Software, CA, Capgemini, Hewlett-
Packard, IBM, Microsoft, Oracle, SAP, SOA Software, Sun Microsystems,
and others.
See also: the OASIS TC
The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)
Jonathan Rosenberg (ed)., IETF SIMPLE Working Group
The IESG received a request from the SIP for Instant Messaging and
Presence Leveraging Extensions WG to consider "The Extensible Markup
Language (XML) Configuration Access Protocol (XCAP)" as a Proposed
Standard. XCAP allows a client to read, write and modify application
configuration data, stored in XML format on a server. XCAP maps XML
document sub-trees and element attributes to HTTP URIs, so that these
components can be directly accessed by HTTP. In many communications
applications, such as Voice over IP, instant messaging, and presence,
it is necessary for network servers to access per-user information in
the process of servicing a request. This per-user information resides
within the network, but is managed by the end user themselves. Its
management can be done through a multiplicity of access points,
including the web, a wireless handset, or a PC application. This
specification describes a protocol that can be used to manipulate this
per-user data. XCAP is a set of conventions for mapping XML documents
and document components into HTTP URIs, rules for how the modification
of one resource affects another, data validation constraints, and
authorization policies associated with access to those resources.
Because of this structure, normal HTTP primitives can be used to
manipulate the data. XCAP is based heavily on ideas borrowed from the
Application Configuration Access Protocol (ACAP) [25], but it is not
an extension of it, nor does it have any dependencies on it. Like ACAP,
XCAP is meant to support the configuration needs for a multiplicity of
applications, rather than just a single one.
See also: SIMPLE specifications
ISO Schematron Standard Published
Rick Jelliffe, O'Reilly News
"The paper and online versions of the ISO Schematron standard are now
available from ISO for CHF120 and from ANSI for US$98. I believe it is
being translated into Japanese as a JIS standard and will be cloned
as a British Industrial Standard. I'd like to thank everyone involved
at ISO SC34, notably Ken Holman, Martin Bryan, Murata Makoto, Yushi
Komachi, James Clark, Alex Brown, Eric van der Vlist, Lynn Price, and
Charles Goldfarb. Special mention to my far-thinking sponsors at
Academia Sinica, Taipei, for letting me developer the ideas and
implementation, in particular Dr Simon Lin and Prof. C.C.Hsieh. Thanks
also to various patient bosses or business partners at Geotempo,
Topologi and Allette Systems. After almost a year with little news, it
seems not a day goes by without someone from a large government
organization or Fortune 500 company dropping me a line saying that they
use Schematron: millions of documents. Schematron has been ticking away
as a grassroots phenomenon: indeed AFAIK every implementation of it is
Open Source. But Schematron's strength is not comprehensiveness but
that it is a simple layer to allow validation using XPaths without
requiring programming knowledge (e.g. XSLT skills). XPaths really are
fantastic." According to the Schematron Implementer's FAQ, the ISO
Secretariat "is still considering the request from ISO SC34 to make [the
specification] free. There are drafts available at Schematron.com. The
only technical difference in the final version is that "/" was missing
as an allowed node in the context XPath, and the attribute name
@queryLanguage was misnamed in one place.
See also: ISO DSDL Part 3
Laying the Groundwork For 'Process Oriented Architecture'
Joe McKendrick, ZDNet Blog
This blog records a conversation with Joe Chiusano, associate at Booz
Allen Hamilton and a member of OASIS' SOA Reference Model Technical
Committee. The SOA-RM is in public review stage, and Chuisano and his
colleagues hope to release it as a spec before the year is out. To
date, there has not been a solid definition of what constitutes a
"service-oriented architecture." There has been raging debate, in fact,
on what exactly an SOA should be, and how much of it is Web services,
and how much of it is other types of services. Chiusano and the
SOA-RM committee hope to finally settle this question, but not lock
in technologies or methodologies that will be outdated 10 years from
now. The SOA Reference Model outlines concepts such as "service,"
"service description," "visibility," "real-world effect," and
"contract and policy." A real-world effect, for example, may be the
result from interacting with a service. For instance, Chiusano
explains, "if we had a service consumer that wanted to reserve a
seat on a plane, and the airline was the service provider. When all
is said and done, and everything goes well in the transaction, the
real-world affect would be that a seat is indeed reserved on a
plane." The SOA Reference Model may be employed in mergers between
organizations.
Reference Model for Service Oriented Architecture 1.0
C. Matthew MacKenzie et al (eds), OASIS Public Review Draft 2
Members of the OASIS SOA Reference Model TC recently released a second
public review draft for "Reference Model for Service Oriented
Architecture 1.0." This specification provides an abstract framework
for understanding significant entities and relationships between them
within a serviceoriented environment, and for the development of
consistent standards or specifications supporting that environment. It
is based on unifying concepts of SOA and may be used by architects
developing specific service oriented architectures or in training and
explaining SOA. A reference model is not directly tied to any standards,
technologies or other concrete implementation details. It does seek to
provide a common semantics that can be used unambiguously across and
between different implementations. While service-orientation may be a
popular concept found in a broad variety of applications, this
reference model focuses on the field of software architecture. The
concepts and relationships described may apply to other 'service'
environments; however, this specification makes no attempt to
completely account for use outside of the software domain.
See also: the TC web page
Proposed Edits for W3C Core XML Specifications
XML Core Working Group, Proposed Edited Recommendations
Members of the W3C XML Core Working Group have released four Proposed
Edited Recommendations for core XML specifications. The XML Core WG is
chartered to develop and maintain the specifications for XML itself
and closely related specifications such as Namespaces in XML, the
XML Information Set, and XInclude. The updated specifications include
the fourth edition of Extensible Markup Language (XML) 1.0, and second
editions of Extensible Markup Language (XML) 1.1, Namespaces in XML
1.0 and Namespaces in XML 1.1. Proposed for the convenience of readers,
thewse publications incorporate corrections for all errors reported to
date, and are not new versions. The test suites have been updated. For
XML, markup for RFC 2119 key words has been improved. Public comments are
welcome through 12-July-2006.
See also: XML Namespaces references
AJAX Developers Tell Microsoft IE Is Not Enough
Darryl K. Taft, eWEEK
When it comes to Asynchronous JavaScript and XML programming, browser
compatibility is number one for Microsoft, according to a key Microsoft
partner who spoke at the Microsoft TechEd 2006 conference on the
company's behalf. Jeff Prosise, co-founder of Wintellect, a Knoxville,
Tenn., consulting, debugging and training firm specializing in Microsoft
.NET and Windows technologies, spoke about Microsoft's AJAX development
framework, known by its codename "Atlas." Prosise: With Atlas, Microsoft
is able to make "JavaScript 'goo'" look "a little bit more like C#." For
example, JavaScript does not support things like interfaces, namespaces
and inheritance, but Atlas does, which makes the language behave more
like C#... Atlas is actually two things, in that you can program it for
the client or the server. On the server Atlas is essentially a set of
controls the developer can drag and drop: The server-side controls render
out Atlas XML Script and that script fires up an XML service and turns
that XML script into declarative code, JavaScript... So the developer has
two choices: to write JavaScript code of their own or write Atlas XML
Script by hand to go against the client-side framework..."
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. |
