[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: a few questions to kick-off the discussion
A few questions to kick-off the
debate (feel free to add more): I suggest to identify questions with
numbers, so that we can refer to them easily later (so yours will start with 7,
8, 9…) Jacques 1- A test
assertion model: how general can it be? Should we claim applicability to *
all* OASIS specs? Can we identify different categories of specifications
or standards? (e.g. XML mark-ups, message protocols, horizontal vs
industry-specific) 2- Can we
reconcile generality with providing enough guidance and details for writing TAs
in various conditions? Should the abstract model be “branched” into
more concrete sub-models more appropriate for different types of tests / types
of specs? 3- Can we
identify cases where TAs have been automatically generated from the spec
material? Should a TA model be applicable in such cases? 4- the scope of
the deliverable, i.e. content of the guideline: what should the guideline cover
besides a TA model. In particular, should we consider a TA XML mark-up?
(some orgs have already done that and will do again: WS-I) If yes, what kind of
use should we support for such a mark-up? (what kind of processing is envisioned) 5- How to deal
with examples / samples – given the broadly applicable nature of this work,
should some more interactive way to gather sample material – before and
after finalizing a guideline? 6- how to
cooperate with other orgs (W3C, WS-I…) in order to produce a guide that
is consensual beyond OASIS. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]