Re: ebXML Core Components Submission Version 1.03

[Tim McGrath <tmcgrath@tedis.com.au>]

once again, thank you and your team for your time in the QR conference
call.

as we discussed, our understanding of 'ebXML environment' is the implementation of ebXML framework technologies.   that is, within the other ebXML core components and business process definitions.  we did not mean the ebXML standards process.  hope that clarifies the statement.

it is not usual practice for QR comments to be in the document, we just dont want to put our words in your mouth.  if you are happy, we have no concerns about whether the "Quality Review qualified statement" is left in or not.  our main concern is that the actual statement be in the introduction.

"Blantz, Mary Kay" wrote:

 Hi Tim,Not sure why you would say that it's primary purpose is for use within an ebXML environment.  If Vienna isour last meeting, then there will be no ebXML environment.  It would make one wonder why we wouldbother with it at all.Is it typical to include QR comments in an approved document?Mary Kay

-----Original Message-----
From: Tim McGrath [mailto:tmcgrath@tedis.com.au]
Sent: Thursday, April 19, 2001 4:10 AM
To: Blantz Mary Kay
Cc: James Whittle; 'Gait Boxman'; 'Becker Thomas'; Mike Adcock; Sue Probert; 'Lisa Shreve'; ebxml-core@lists.ebxml.org; Bob Sutor; Bill Smith; Ray Walker; knaujok; knaujok; ebxml-stc@lists.ebxml.org; 'ebXML Coordination'
Subject: Re: ebXML Core Components Submission Version 1.03
 

The Quality Review team have completed their review of  "ebXML Naming Convention for Core Components v1.03" document from the Core Components project team as submitted on 12th April 2001.

We recommend that this document go forward for its second round of public review, given the following condition.

A note is insert into Section 1 "Status of this Document", that reads...
Quality Review qualified statement:
This specification is one of several cornerstones for the overall Core Components specifications.  Whilst it may be considered for stand-alone use, its primary purpose is for use within an ebXML environment.  It has limited value as an independent document.

I would ask that James Whittle be authorised to make these changes and then liaise with Klaus and Karl Best in order that this be posted for public review as soon as possible.

Our review has also identified some other issues that should be addressed during the public review period.  These are included in the attached report.

The Quality Review team have also received a copy of the "Core Component and Business Process Document Overview Version 1.03" document.

This is, almost by definition, the document that should be reviewed after all the documents to which it refers.  Therefore, we feel unable to comment meaningfully on this document at this time.  The analogy would be to ask for comment on a roadmap when the roads had not yet been built.

I would like to take this opportunity to invite the team leads and editors of the Core Components team to participate in a conference call with representatives of the QR team to discuss these comments.  The call details are:

Time:
Friday 20th April 09:30am Pacific summer time
(see:http://www.timeanddate.com/worldclock/fixedtime.html?day=20&month=4&amp;year=2001&amp;hour=9&amp;min=0&amp;sec=0&amp;p1=224)

Call numbers are:
USA  888 296 1938
International  304 345 7506 (limited number, sorry!)
participation code  262658

"Blantz, Mary Kay" wrote:

Hello all,

The attached zip files contain the Core Components submission to QRT to be
considered for public review. The following documents are included;

*       CC and BP Document Overview Ver 1.03
*       ebXML Naming conventions for Core Components and Business Processes
        Ver1.03
*       Comments logs for both of the above

We would like to stress the importance that comments following the procedure
documented at http://www.ebxml.org/specdrafts/specs_for_review.htm
<http://www.ebxml.org/specdrafts/specs_for_review.htm>  and point out that
comments which do not adhere to this criteria may not be considered.

All comments should be sent to James Whittle (james.whittle@e-centre.org.uk
<mailto:jameswhittle@e-centre.org.uk> ) and copied to the Core Components
list serve (ebxml-core@lists.ebxml.org <mailto:ebxml-core@lists.ebxml.org> )

Mary Kay Blantz

 <<CC and BP Document Overview Ver 1.03.zip>>  <<ebXML Naming Convention
Ver1.03.zip>>  <<CC and BP Dcument Overview Ver 1.03 comment log.zip>>
<<ebXML Naming convention Ver 1.03 comment log.zip>>

  ------------------------------------------------------------------------
                                               Name: CC and BP Document Overview Ver 1.03.zip
   CC and BP Document Overview Ver 1.03.zip    Type: Download File (application/zip)
                                           Encoding: base64

                                          Name: ebXML Naming Convention Ver1.03.zip
   ebXML Naming Convention Ver1.03.zip    Type: Download File (application/zip)
                                      Encoding: base64

                                                          Name: CC and BP Dcument Overview Ver 1.03 comment log.zip
   CC and BP Dcument Overview Ver 1.03 comment log.zip    Type: Download File (application/zip)
                                                      Encoding: base64

                                                       Name: ebXML Naming convention Ver 1.03 comment log.zip
   ebXML Naming convention Ver 1.03 comment log.zip    Type: Download File (application/zip)
                                                   Encoding: base64

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

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