RosettaNet

Instead, you write an XQuery that transforms your existing response data into a RosettaNet response.

RosettaNet has promised these problems will go away when they roll out a re-modeled, well-connected schema.

This e-business dialogue will be based on a real-world business problem, which will be addressed by using a proven solution from RosettaNet.

RosettaNet, however, seems more carefully grounded in the real world, and its PIPs are tested by consortium members.

In RosettaNet, the e-business dialogues are defined with UML activity diagrams, text tables, and XML documents.

The workaround is to use best practices from RosettaNet in the Web services paradigm.

We could use BPEL4WS to create brand new business processes, or we could use it to model RosettaNet-based e-business processes.

Now let us look at the components of RosettaNet and how RosettaNet-based e-business dialogues work.

Other options for semantic anchoring include ebXML core components and RosettaNet dictionaries, both of which I've covered in this column.

As I explained earlier, this is where you can leverage RosettaNet components, to build your own real-world e-business dialogues.

RosettaNet takes its name from the Rosetta stone, which a soldier in Napoleon's army discovered in Egypt in 1799.

You also need to start exchanging real RosettaNet-based purchase order data.

For example, imagine a buyer who standardizes on a standard like RosettaNet and is away from the original in-house developed schema.

In this article, I will talk about the conceptual steps required to create RosettaNet-based Web services.

I introduced the specification of RosettaNet and how to leverage them.

Standing on the shoulders of a giant: Web services with RosettaNet

The mapping between RosettaNet PIP and WSDL is as follows

I believe that we should use RosettaNet-based Web services for the following reasons