I was extremely unsatisfied with my previous attempts at section 3.0 of
the document. I re-read some books on the subject then derived a new
meta model for our Patterns.
The new metamodel for patterns is actually not new - it is an
aggregation of several industry standard practices for architectural
patterns. The new document is an adoption and aggregation of several
components that are specific to our use within our document.
The document 3.0-SOA_Archtiectural_Patterns.pdf is now uploaded to our
TC private pages. IMHO - encourage everyone to read it. It is actually
not too painful ;-)
It describes what a pattern is and how we break a pattern down into a
syntax including some mandatory parts. It also works in the concept of
a Story as opposed to an "example" used by many others. This is a good
touch point to speak to business users. Another part entitled "Known
uses" also let us tie in existing standards for certain components.
This is a powerful tool to promote reconciliation of ebXML and WS stacks.
An actual example case will be also posted soon to provide further
examples. These are first edits.