Why does that have to be done through a specification though? Why couldn’t
it be done through a discussion between likeminded individuals, groups or
vendors who share the same problem, have different proposed solutions, go
away and try them, then come back at some time (perhaps pre-determined) to
share their experiences and move forward to standardise what works? Now that
problem statement and the range or proposed solutions should be documented
somewhere and I suppose we could call it an “alpha release of the
specification” or maybe just on a wiki or mailing list or google doc or
something else.
Mark.
On 31 May 2018, at 07:46, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
While there will always be product-specific features, some of which might
make
their way into future versions of the specification, wouldn't it also be
nice if
multiple independent implementations of new functionality could be created
simultaneously to experiment with the new features in different contexts
and
with different customers? I just don't see how to do that without having
some
sort of specification being developed at the same time as the
implementations.