OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

soa-blueprints message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [soa-blueprints] Primer

I have not been following the email carefully enough, so forgive me if this has already been established but

1. Exactly what is a blueprint?
2. What purpose does it serve?
3. Why should I think one will be generally applicable?
4. Why do I care?

Do we expect that a blueprint will be a sort of turnkey formula?  How do we determine the limits of applicability for a given blueprint?  Are there underlying assumptions that all blueprints have in common, or is each blueprint fundamentally different (a very possible construction), or are there fundamental groupings with multiple non-redundant examples in each group?

I think agreeing on a clear strawman definition of blueprint is essential.  It can be modified as we learn more but we need a clear starting point.


On Nov 21, 2005, at 9:12 PM, <marchadr@wellsfargo.com> <marchadr@wellsfargo.com> wrote:

One question to pose to the group is maybe the case study actually becomes a type of primer for the blueprints once the blueprints are defined.



Ken Laskey
MITRE Corporation, M/S H305     phone:  703-983-7934
7515 Colshire Drive                        fax:        703-983-1379
McLean VA 22102-7508

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]