|
Because a discussion doesn't give you
legal rights to the IP, unless the discussion is part of a defined
process with a legal framework for IP flow. That's the
specification process we're defining here.
Mark Little wrote on 5/31/18 3:50 AM:
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.
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.
---
Mark Little
JBoss, by Red Hat
Registered Address: Red Hat Ltd, 6700 Cork
Airport Business Park, Kinsale Road, Co. Cork.
Registered
in the Companies Registration Office, Parnell House,
14 Parnell Square, Dublin 1, Ireland, No.304873
Directors:Michael
Cunningham (USA), Vicky Wiseman (USA), Michael
O'Neill, Keith Phelan, Matt Parson (USA)
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
|
