Suggestion

[<marchadr@wellsfargo.com>]

Miko,

I would like to suggest that maybe we have people establish what they want to see come out of the group.
If we can get people to send it through email we can help to establish an end target goal of the blueprints.

Also with that in mind I will contribute my thoughts to this based on some experience I have defining internal SOA blueprints.

I see the blueprints can be established in a few different ways.

First, an SOA blueprint can be how the services interact and are managed within the context of your service oriented environment.
Second, an SOA blueprint can be an expression of how common business process can be evolved into an SOA.
Third, an SOA blueprint is specific to a domain since the domain establishes business processes and the SOA realizes those processes.

The first can be leverage by the other ones. The last one is a difficult exercise to achieve and is very similar to having a unified business language (see the oasis standard).
Maybe in some ways the SOA blueprints can leverage some of the work that is done by the unified business language standard.

These are some ideas to trigger more definition on the end state of this technical committee.
Thoughts?

Obviously the body of work that was done as part of the middleware group seems to straddle the First and Second points.

Thanks,

Daniel Marchant
Architect
Wells Fargo