Re: Please Clarify Role of QR Team in Review Process

["Paul R. Levine" <plevine@telcordia.com>]

I agree that the QR Team reports their recommendations on a specification to the
Exec, and does not have the power to "release" or "hold back."  Then the Exec
can support the QR recommendations or not.  If not, I would expect the Exec to
offer what is needed to resolve the issue.  Since the StC is provided the draft
spec and QR recommendations FYI, it has the information it needs to vote on what
to do if the submitting team does not agree with the Exec's remedy.

Regards,

Paul Levine



Mike Rawlins <rawlins@metronet.com> on 09/22/2000 12:17:12 PM

Please respond to rawlins@metronet.com

To:   ebxml-stc <ebxml-stc@lists.ebxml.org>
cc:    (bcc: Paul R. Levine/Telcordia)
Subject:  Please Clarify Role of QR Team in Review Process




Folks,

I've seen a few messages go by that indicate to me a need to clarify the
role of the QR Team (and formerly QA team) in the review process.  My
understanding from our StC discussions was that the QR team would only
*report* review results to StC and the Exec.  No mention was made either
of granting QRT the power to "hold back" submitting a specification to
general ebXML comment, or of the Exec "releasing" a specification for
comment.  Neither of those being discussed, it seems to me that it still
falls to the submitting team to decide whether or not to submit a
draft.   If someone has an issue with a team submitting a specification
that they feel isn't ready, the default then would be to deal with that
issue as we do all other issues, i.e, formally raise it to StC and have
us vote on it.   I'm all for using what few procedures we have in place
and keeping things as simple as possible.

If anyone has a different understanding of the process, I suggest we
clear this up right away.

Regards,
--
Michael C. Rawlins, Rawlins EC Consulting
http://www.metronet.com/~rawlins/