I have to agree with Duane and others on this one. If we continue to scrutinize each and every section before submitting the document to the Quality Review team, then we will never finish before Vancouver, thus delaying the plenary vote, and also potentially delay to overall debut of the ebXML Standards in Vienna. Bob Cunningham shares this sentiment and expressed a need for the TA Team to draw the line and formally vote to freeze the document for Quality Review. After the document is approved by QR, we most certainly will review and incorporate the comments from within the ebXML community. We are at a critical point right now and MUST submit the document to the QR team for review. This does not diminish the continued constructive comments, but rather allows the document in its current version to be reviewed by the masses.

Forst of all - Merry Christmas. I am in Germany until Jan 5 so I maynot be able to respond immediately.

As for the current spec, the exact thing that I did not want to happenhas happened. People are submitting fixes, comments etc BEFORE it hasgone out for comment. Here is what has to happen:

1. Vote by TA committee to send it out to QRT AS IS2. QRT PT to okay document for submission to the Plenary for generalcomments

NOTE: Items 1 and 2 are done with an explicit view that the document isNOT in its' final form. We are putting it out for comments. THe BPsection will have others commenting on it besides just a few in the BPteam. As for the other comments, they are useful but we have aresponsibility to collect a wider range of comments.

I am not saying any of the input is not good, just that we have aprocess to follow.

3. The comments period

This is where we want corrections on spelling, grammar, wording etc. Doing it now will just delay the specification unnecessarily.

TA Team - lets' vote on this spec AS IS. IF there is something thatneeds to be changed - it can be changed during the comment period.