New DP Template

[Pete Wenzel <pete@seebeyond.com>]

Jacques asks:
> Can you quickly review the two docs posted today on our site:
> (a) an update of the general Deployment Profile Template document structure
> (meta-data), as proposed for replacement of the old one.
> (b) a draft of what the ebMS 2.0 Template conforming to this meta-data would
> look like.
> And tell me what you'd vote on approving the new template structure?
> (I'll put it to vote later this week...)

I looked through the Template, and the meta-Template, and believe they
capture everything we need.  I would be in favor of proceeding in this
direction.

I am wondering about the "Test References" field, however.  It seems
to me that in ECOM's guide, this is intended and used as a further
narrowing of the "Profiling" field: similar in nature, but more
specific, because it is only applicable within a certain (test)
context.  Could this be better handled through a separate instance of
the profile, which is used to describe the profiling requirements for
a specific test environment?

For example, we would have ECOM Deployment Profile for ebMS, in which
"Profiling" field contains allowed values/ranges/etc. narrowed from
the base specification.  Then we would have a separate ECOM ITG Test
Profile for ebMS, which would contain the more-constrained values in
its "Profiling" field, to be used only when implementing the ITG Test
Suite, instead of the original values.  The second document does not
have as wide a scope of applicability as the first, so maybe we should
not encourage them to be mixed into one document.

--Pete
Pete Wenzel <pete@seebeyond.com>
Senior Architect, SeeBeyond
Standards & Product Strategy
+1-626-471-6311 (US-Pacific)