Proposal to add 'xsd:any' (extension point) to testAssertion and testAssertionSet

[Stephen Green <stephen.green@documentengineeringservices.com>]

I'd like to propose adding 'xsd:any' (extension point) to
testAssertion and testAssertionSet. There seems to be
a clear use case that people will want to combine a
set of test assertions with their own syntax (such as for
describing a specification which contains some test
assertions - as we already accommodate in the TAML
schema by making both 'testAssertion' and
'testAssertionSet' global elements which can be
embedded in other documents if need be). By providing
an 'xs:any' element at the end of 'testAssertionSet_type'
and 'testAssertion_type' we would allow these types to
include further custom elements defined in a different
namespace (not TAML's). There are some alternatives,
such as whether to put the extendable 'any' inside a
wrapper element to allow it to go at the top of the
sequence; whether to allow multiple other-namespace
elements or just one (which would then have to contain
any multiplicity of elements inside a wrapping element).
I think it is a good practice which makes a lot of sense
to make it easier to combine Test Assertion Markup
Language elements with other elements in a clear,
controlled, predictable way to help implementation of
TAML.
---
Stephen D Green