XPDL in the real world

I want to start a discussion about the truely usability this great workflow pattern in the application of the real business applications in companies.
So, i would like to know if there's any real application based on XPDL in buzzworld out of vendor scenario.
What's the truely usability in the real world ? Is there any company using the XPDL for interchange process or for a simple internal corporate workflow process ?

Sincerely, i see many discussion about BPEL and XPDL implementation but it seems me only theorical opinions based on what. Many people published your comments and criticism based on what they read about pros and cos of XPDL (on theorical basis) and other standards formats like BPEL without deeping on technical basis. Anyone can get the XPDL Definition from WFMC and judge it contents. Let's to run it first before to knock it.

Let's simplify to can use !

XPDL or BPEL will be always out of date - it's a technology nature, it's normal.
Ok, let the doubts and development for researchers. They are pays for think about how to do it better.
We common humans (aka System Analysts, Developers and similars) need more theories ? Let's practice it first.

The begin human always want more and not settle for some. Ok, I know it is the rote for the development, but sometimes i think that we have enough to go ahead and we want more without knowledge what's in hand.

My advice:
Start developing with XPDL or BPEL and try to apply it in the practice - try to execute some XPDL/BPEL tools - you'll see that for this moment we don't need other releases. There is much to learn yet.

I would like to know if someone has developed some business applications based on XPDL standard, mainly in Brazil.
Has someone tried to running a truely application using any XPDL vendor tools ?

I have worked with many workflow applications for sometime in my career and have followed the WFMC steps since. Some time ago i was researching and trying to developing an application based on XPDL and i have choosed the Open Busines Engine (OBE) package. My experience using this tool says me that build an application based on it is far for a common user (like a process analyst) not experimented in IT technology and development area.

There's a couple of complexity here, because itsn't subject to modelling process only using a simple editor like JPED or Together - there's many technical work involved in it - Java, XML (and other letters) and much patience. I have worked by many years like a developer and system analyst in many areas and used many tools and i can conclude the following:

Why a company would use a so complexy model in its applications ? Let's think in learning curve to start it running and about the development time and costs to start it running.
I don't want enter in subjects about BPEL and another standards, it doesn't matter because i see the XPDL like a great standard and i would choose it to use in my commercial applications.

Unfortunatelly i don't get to do my own application yet to show the world.
I think that there's many discussion about which the better format (XPDL or BPEL) and few samples of real word to serve like reference. Has anyone doubts about the differences between both of them ? I don't want to start a new discussion here, you can find many articles explaining about it - try google.

I like of the OBE because OBE guys (thanks Adrian) did a good work and let us good reference documents about XPDL and it implementation. Also the code is source code and i can do an introspection in it and learn more about XPDL misteries.

To conclude, the WFMC proposal is fantastic and they did a good work at now, but is necessary to publish more than definitions, specifications and new releases - we (developers, consultants and analysts) need of the world real examples to dissemine it - or we can out a limb to see it drawn down to research intends only.

Gilson DElrei
Sorry, english isn't my first language.