[Fwd: ebXML Requirements Specification 1.04 for QRT Submission]

[Mike Rawlins <rawlins@metronet.com>]

Here are the review comments from the QRT regarding 1.04 of the ebXML
Requirements Specification.  It will go to public review as soon as it
is posted on the ebXML web site.

I propose the following plan to lead to approval in Vienna:

   * Review and disposition QRT comments on listserv and on a conference
     call to be scheduled in the next two weeks
   * Review and disposition any comments received during public review
     immediately after the close of that review period (probably April
     27, depending on when the spec is posted).
   * Submit final version for review prior to plenary on April 30, or as
     soon as it is ready after the close of the public review.  I am
     confident that the rule for posting two weeks prior to final vote
     will be relaxed.
   * Address any final changes or unresolved issues in Vienna before
     approval on Friday.

Regards,

---------------------
Mike Rawlins, ebXML Work Group, Requirements Project Team Leader
http://www.ebxml.org/project_teams/requirements/private/

---

• From: "Tim McGrath" <tmcgrath@tedis.com.au>
• To: rawlins@metronet.com
• Date: Thu, 12 Apr 2001 17:23:51 +0800

The Quality Review team have completed their review of the ebXML Requirements
Specification as submitted by the ebXML Requirements Project Team on March
19th 2001.

We recommend that this document go forward for public review.

However, there are several comments we would like to see addressed before this
material is finalised for voting.  These are mainly editorial, but include
some questions regarding the content.

In addition, there is a critical point that needs clarification as it affects
the relevance of our comments.  We are unsure of the intended final status of
this document.  Is this a revision of the ebXML guideline document voted on at
the Brussel’s plenary or is it an upgrading of this document to the status of
a technical specification?

If it is the latter, then we must also promote the view that previous
acceptance of this material is not a justification for retaining it in the
final document.

The main issues we have with the content are detailed in the attached report.

We apologise for the delay in reviewing this material and acknowledge our
appreciation of the patience of the Requirements team.

Once again, i would ask Klaus and Karl to arrange for this document and our
report to be published on the ebXML website and an announcement made as soon
as possible.  Given the unfortunate delays in this review, the time window for
the Requirements team editting both these any other public comments is very
narrow.

Mike Rawlins wrote:

> The Requirements Team submits version 1.04 of the Requirements
> Specification for quality review.  The document is in MS-Word 97 with
> line numbers, zipped.
>
> The change log from version 1.0 is also submitted.
>
> ---------------------
> Mike Rawlins, ebXML Work Group, Requirements Project Team Leader
> http://www.ebxml.org/project_teams/requirements/private/
>
>   ------------------------------------------------------------------------
>                      Name: ebxmlRS104.zip
>    ebxmlRS104.zip    Type: Download File (application/x-zip-compressed)
>                  Encoding: base64
>
>                           Name: 1-04 Change Log.doc
>    1-04 Change Log.doc    Type: Download File (application/msword)
>                       Encoding: base64

--
regards
tim mcgrath
TEDIS   fremantle  western australia 6160
phone: +618 93352228  fax: +618 93352142

Ebxml-QR-REQ-Review-Apr10.pdf

---