April 2005 - Posts

WS-* interoperability

Companies like Microsoft, IBM or Systinet among 14 organizations joined together for the first time to demonstrate interoperability of the WS-Security OASIS Standard at the Gartner Application Integration and Web Services Summit in Los Angeles. I think that this a cool practice to follows with other WS-* protocols.

Posted by gsusx | with no comments

WS-Discovery

WS-Discovery specification has been updated.

Posted by gsusx | with no comments

JBI

Java Business Integration JSR 208 recently passed the JCP public review ballot. However both IBM and BEA abstained.

Posted by gsusx | with no comments

WS-RM news

WS-RM and WS-RM Policy are now submitted to OASIS.

 

Twenty-five months after the first public announcement for the Web Services Reliable Messaging Protocol (WS-ReliableMessaging), the co-authors BEA Systems, IBM, Microsoft, and TIBCO have announced that the WS-ReliableMessaging and WS-RM Policy specifications will be submitted to OASIS for further refinement and finalization as a Web services standard.

In February 2005, WS-RM was re-published as two separate specifications: one for the core protocol elements and one for the related policy assertion. WS-ReliableMessaging "describes a protocol and SOAP binding that allows messages to be delivered reliably between distributed applications in the presence of software component, system, or network failures. The protocol is described in this specification in a transport-independent manner allowing it to be implemented using different network technologies. The protocol depends upon other Web services specifications for the identification of service endpoint addresses and policies." The Web Services Reliable Messaging Policy Assertion (WS-RM Policy) specification refactors the Reliable Messaging policy assertion into a discrete specification.

Posted by gsusx | with no comments

BPEL and Java

Nice reading about BPEL and Java written by Matjaz B. Juric.

Posted by gsusx | with no comments

JSR-181

These are great news for the J2EE Web Services developers.

 JSR-181, which defines eight annotations to enable easy definition of Java Web Services in a J2EE container, has been approved.

Posted by gsusx | 1 comment(s)

WSDL Binding

The WSDL Binding for WS-Addressing specification has been updated.

The Web Services Addressing Working Group has released an updated Working Draft of Web Services Addressing 1.0 - WSDL Binding. The document defines how the properties in Web Services Addressing 1.0 - Core are described in the Web Services Description Language (WSDL). Web Services Addressing provides transport-neutral mechanisms and is designed to work with both WSDL versions 1.1 and 2.0.

Posted by gsusx | with no comments

RDDL

Nice comment about Use RDDL instead of XML Schema at the Namespace URI?
Posting to W3C Web Services Addressing Working Group List
Proposal: "Place a RDDL document at each of the namespace URIs defined by WS-Addressing. Provide a 'latest schema' link as well as dated links to the schema. State in the document that the resources (schemas) at the dated links are immutable, the list of dated schemas may grow to incorporate fixes, and the latest schema link will always point to the latest." Justification: "One advantage of RDDL is that it would enable one to discover, through the namespace URI, a number of schemas for the namespace. This is especially interesting when errata are taken into account. The WS-I BP promulgated some fixes to the WSDL 1.1 schema, but since it is also desirable to have a stable document at the namespace URI, it published alternative dated versions with various fixes in them, and pointed to those dated versions from the spec. It might have been simpler and more discoverable to find all the related (dated) schemas through a RDDL document at the namespace URI."

Posted by gsusx | with no comments

XRI news

A set of XRI documents are available for public review:

The XRI specification suite presented for public review contains four parts. A non-normative document Introduction to XRIs summarizes the uses and features of XRIs and is intended to serve as an entry point for the XRI 2.0 suite. It clarifies what XRIs are in terms of the supported Uniform Abstract Identification Layer. It provides examples of the types of problems XRIs are designed to solve, for example: The Broken Links Problem (Persistent Identification); The Multiple Authority Problem (Federated Identification); The N-Squared Mapping Problem (Shared Identification); The Exploding Addresses Problem (Simplified Identification); The Bootstrap Discovery Problem (Metadata Identification); The Public Identifier Problem (Privacy-Protected Identification); The Future-Proofing Problem (Extensible Identification).

The XRI Syntax document defines the normative ABNF grammar for XRIs, transformations from XRIs into IRIs and URIs, relative XRI references, and normalization/comparison. XRI syntax "extends generic IRI syntax in the following four ways: (1) Persistent and reassignable segments; unlike generic URI syntax, XRI syntax allows the internal components of an XRI reference to be explicitly designated as either persistent or reassignable; (2) Cross-references, which allow XRI references to contain other XRI references or IRIs as syntactically-delimited sub-segments; (3) Global context symbols, or shorthand symbols for establishing the abstract global context of an identifier; (4) Standardized federation, in which federated identifiers are those delegated across multiple authorities, such as DNS names; XRI syntax standardizes federation of both persistent and reassignable identifiers at any level of the path."

Posted by gsusx | with no comments
More Posts Next page »