Archive for the ‘General’ Category

The Global Justice Reference Architecture (JRA) ebXML Messaging Service Interaction Profile Version 1.0

The purpose of this document is to establish a SERVICE INTERACTION PROFILE (SIP) based on the ebXML family of technology standards.

A Service Interaction Profile is a concept identified in the Global Justice Reference Architecture ([JRA2]). This concept defines an approach to meeting the basic requirements necessary for interaction between SERVICE CONSUMERS and SERVICES. The approach utilizes a cohesive or natural grouping of technologies, standards, or techniques in meeting those basic interaction requirements. A profile establishes a basis for interoperability between service consumer systems and services that agree to utilize that profile for interaction. A Service Interaction Profile guides the definition of SERVICE INTERFACES.

In an SOA environment, every service interface shared between two or more information systems should conform to exactly one Service Interaction Profile. Service consumers who interact with an interface should likewise conform to that interface’s profile. The profile discussed in this document is based on the ebXML family of technology standards, defined as follows:

  • OASIS ebXML Messaging Services, Version 3.0: Part 1, Core Features, 2007 [ebMS3]
  • OASIS ebXML ―Conformance Profiles Gateway RX V3 or RX V2/3 for e-Business and e-Government applications [ebMS3-PROFILES]
  • OASIS ebXML Business Process Specification Schema v2.0.4 [ebBP]
  • OASIS ebXML Collaboration-Protocol Profile and Agreement Specification Version 2.0 [ebCPPA v2]
  • The Web Services Interoperability Organization (WS-I) Basic Profile, Version 1.1, dated April 10, 2006 (noted in this document as [WS-I BP]), ebXML Messaging Services v3 is conformant with Section 3 MESSAGES and Section 6 SECURITY and all standards that those sections reference. Section 4 of WS-I Basic Profile does NOT APPLY to ebXML. ebXML does not specify WSDL for service descriptions and service bindings.
  • The WS-I Attachments Profile ([WS-I AP]), Version 1.0, and all standards that it references
  • The WS-I Basic Security Profile Version 1.0 (dated March 30, 2007, 37 noted in this document as [WS-I BSP]), all current Token Profiles, and all standards that they reference.

For more information please visit:


Make use of WS-I resources to test for Web service interoperability

The Web services technology has promised us to provide a high level of interoperability between software components. But what does this mean in practice?

In theory Web services are especially designed to offer “reusable” features that are discovered and bound at runtime using technical “loose coupling.” The Open Solutions Alliance (OSA) has been formed expressly to help speed the creation and adoption of integrated, interoperable business applications based on open source. The OSA recommends that each vendor or project lead should carefully think about which functions in their to need to be triggered by other applications, and ensure that they are exposed in a loosely coupled way so customers and integrators can take care of implementing the process. These functions should be exposed as a service and should be implementation language neutral, so for example a PHP application can invoke a feature in a Java application.

Having in mind that Web services are used by consumers unknown at design-time, and looking at the “Publish-Discover-Invoke-Paradigm” based on standards it will become evident that Web services are fundamentally about “interoperability”. In reality, however, the “standard” protocols are not standard enough to ensure automatic interoperability. Most of the risks stem from subtle variants in implementing a same standard or some borderline option of it (“corner cases”), and from different approaches in integrating several of these standards in the same implementation. Other problems rely on the different programming language implementations of data types like “Date”, “Floating Point” or “BigDecimal”, e.g. when looking at Java & J2EE vs. Microsoft .Net with C++ or C#.

There are many definitions in the industry and academic research that tell us how to interpret the term “interoperability” for Web services. In Microsoft’s “Pattern & practices for building interoperable Web services” book we can find a definition that has been adapted by most of the tool providers in this area:

“An interoperable Web service is one that works across platforms, applications, and languages as well as with Web services from other vendors.”

However, we saw above that interoperability needs consensus, a clear understanding of requirements, and adherence to specifications. In response to these needs, the Web Service Interoperability Organisation WS-I was founded.

WS-I is an open industry organization “chartered to establish Best Practices for Web services interoperability, for selected groups of Web services standards, across platforms, operating systems and programming languages”. The organization is a consortium of Web services companies to provide guidance, recommended practices, and supporting resources for developing interoperable Web services in the SOA world…

To read the full article by Klaus Berg please visit:

Information R/evolution

Happy Nowruz

Nowrūz is the traditional Persian / Iranian new year holiday. Nowruz marks the first day of spring and the beginning of the Iranian year as well as the beginning of the Bahá’í year. It is celebrated on the day of the astronomical vernal equinox (start of spring in northern hemisphere), which usually occurs on the March 21 or the previous/following day depending on where it is observed.

As well as being a Zoroastrian holiday, it is also a holy day for adherents of Sufism as well as Bahá’í Faith. In Iran it is also referred to as an Eid festival, although it is not an Islamic feast.

The term Norooz first appeared in Persian records in the second century AD, but it was also an important day during the time of the Achaemenids (c. 648-330 BC), where kings from different nations under the Persian empire used to bring gifts to the emperor of Persia on Nowruz.

Haft Sîn or the seven ‘S’s is a major tradition of Nowruz. The haft sin table includes seven items specificly starting with the letter S or Sîn (س in the Persian alphabet). The items symbolically correspond to seven creations and holy immortals protecting them. 

The Haft Sīn items are:

  • sabzeh – wheat, barley or lentil sprouts growing in a dish – symbolizing rebirth
  • samanu – a sweet pudding made from wheat germ – symbolizing affluence
  • senjed – the dried fruit of the oleaster tree – symbolizing love
  • sīr – garlic – symbolizing medicine
  • sīb – apples – symbolizing beauty and health
  • somaq – sumac berries – symbolizing (the color of) sunrise
  • serkeh – vinegar – symbolizing age and patience

Other items on the table may include:

  • traditional Iranian pastries such as baghlava, toot, naan-nokhodchi
  • dried nuts, berries and raisins (Aajeel)
  • lit candles (enlightenment and happiness)
  • a mirror
  • decorated eggs, sometimes one for each member of the family (fertility)
  • a bowl with goldfish (life, and the sign of Pisces which the sun is leaving)
  • a bowl of water with an orange in it (the earth floating in space)

Here is a picture of my Haft Sin for Nowruz 1387 (20 March 2008).


Nearly half of UK companies go for SOA

The SOA readiness survey of 180 UK organisations by Birmingham-based systems integrator Griffiths Waite showed that of the 47% of respondents pursuing SOA, 20% had already implemented at least one SOA project.And of that 20%, almost half (49%) said their main reason for adopting SOA was to achieve IT flexibility and 14% said it would enable them to get the most out of their IT investments by providing industry standards for accessing functionality and resources.

Hugh Griffiths, director of Griffiths Waite, said, “This shows UK companies are starting to put money behind SOA, which represents a definite shift away from technical discussions towards mainstream implementation.”

Griffiths said another reason for the shift was an increase in the number and maturity of standards, such as the Business Process Execution Language (BPEL) for specifying business process behaviour for web services.

Read the complete article in Computer Weekly

Chaharshanbe Suri

Chahārshanbe-Sūri is the ancient Iranian festival dating at least back to 1700 BCE of the early Zoroastrian era. The festival of fire is a prelude to the ancient Norouz (Persian New year) festival, which marks the arrival of spring and revival of nature. Chahrshanbeh Suri, is celebrated the last Tuesday night of the year, which would be on 18 March this year. The word Chahar Shanbeh means Wednesday and Suri is red. The bon fires are lit at the sunset and the idea is to not let the sun set. Bon fires are lit to keep the sun alive till early hours of the morning. The celebration usually starts in the evening. On this occasion people make bon-fires on the streets and jump over them. The young shoot lots of fireworks before and during Chaharshanbe Suri.

The tradition includes people going into the streets and alleys to make fires, and jump over them while singing and dancing. There is no religious significance attached to Chahar Shanbeh Suri and it serves as a cultural festival for all Iranian Jews, Muslems, Armenians, Turks and Zoroastrians alike. Indeed this celebration, in particular the significant role of fire, is likely to hail from Zoroastrianism. In addition another tradition of this day is to make a special Ajeel ‘Mixed nuts and berries’. People wear disquise and chadors and go door to door knocking on doors. Receiving of the Ajeel is customary, as is receiving of a bucket of water.

Here are some pictures of Charshanbe Suri in Tehran.


Process Component Models: The Next Generation In Workflow ?

Tom Baeyens, founder of JBoss jBPM gives his view of the state of the BPM / workflow market and introduces a new type of workflow technology called process component models.

This article arguments that the gap between the analysis and the implementation of business processes is far bigger then the marketing of today’s workflow tools might suggest. Also it will propose a much more realistic way of dealing with this situation. The current standards and initiatives will be explained with enough depth so that you can see how they relate to the movements and why.

At the end, a new type of workflow technology is introduced called process component model. This type of framework can handle multiple process languages and it can support process languages that better support the transition from analysis process diagrams to executable processes.

This article is orgnised as follows:

– What is BPEL
     – Thoughts and comments on BPEL
     – BPEL extensions
     – What is BPMN
     – Analysis versus execution
     – Process development process
     – Modelling details
     – Mappings and mismatches
– Other BPM technologies
     – XPDL
     – BPDM
     – jPDL
– Choreography
– Process component models
– Implications of this new approach

Read full article …

Persepolis Recreated

1960s view of the future of e-commerce

A Brief Introduction to REST

You may or may not be aware that there is debate going on about the “right” way to implement heterogeneous application-to-application communication: While the current mainstream clearly focuses on web services based on SOAP, WSDL and the WS-* specification universe, a small, but very vocal minority claims there’s a better way: REST, short for REpresentational State Transfer. In this article, I will try to provide a pragmatic introduction to REST and RESTful HTTP application integration without digressing into this debate. I will go into more detail while explaining those aspects that, in my experience, cause the most discussion when someone is exposed to this approach for the first time.

Key REST principles

Most introductions to REST start with the formal definition and background. I’ll defer this for a while and provide a simplified, pragmatic definition: REST is a set of principles that define how Web standards, such as HTTP and URIs, are supposed to be used (which often differs quite a bit from what many people actually do). The promise is that if you adhere to REST principles while designing your application, you will end up with a system that exploits the Web’s architecture to your benefit. In summary, the five key principles are:

  • Give every “thing” an ID
  • Link things together
  • Use standard methods
  • Resources with multiple representations
  • Communicate statelessly

Let’s take a closer look at each of these principles …