Re: [ebxml-iic] RE: impl guidelines,on the "technical" and "depl oyment" sides

From
Yan Guo <>
Date
2002-06-18T15:24:54+00:00
ID
009c01c216dc$75d896a0$581a030a@YGUO
Thread
Re: [ebxml-iic] RE: impl guidelines,on the "technical" and "depl oyment" sides
Title: RE: [ebxml-iic] RE: impl guidelines, on the "technical" and "depl oyment" sides

Is EAN.UCC TRP 
implementation guidelines available for public review ? If it is, where can 
I find a copy of it ? Thanks for help in advance.

 

Yan Guo

webMethods, Inc.

  
----- Original Message ----- 

  
From: 
  Jacques 
  Durand 

  
To: 'Eric VanLydegraf' ; 'Pete Wenzel' ; 
  Jacques 
  Durand 

  
Cc:  
  ; '' ; Federico 
  Franciosi ; Thomas Bikeev 

  
Sent: Monday, June 17, 2002 10:12 
PM

  
Subject: RE: [ebxml-iic] RE: impl 
  guidelines, on the "technical" and "depl oyment" sides

  

  
OK, Eric you are on the team for the "deployment template" 
  design, 
with Monica & Pete... (and Michael Wang of 
  course as editor, in so far 
as the outcome is still 
  assumed to be a merged document.) 

  
So I assume the subteam for now is: 
 (make sure to CC each other in this group, on this topic, 
  
unless you send to ebxml-iic + EAN folks, which is 
  perfectly OK): 

  
 
 
  
 
 
 
  
 
 

  
Regards, 

  
Jacques 

  
-----Original Message----- 
From: Eric 
  VanLydegraf [mailto:] 
Sent: Monday, June 17, 2002 6:14 PM 
To: 'Pete 
  Wenzel'; Jacques Durand 
Cc: ; 
  ''; 
  
''; 
  Federico Franciosi; Thomas Bikeev 
Subject: RE: 
  [ebxml-iic] RE: impl guidelines, on the "technical" and 
"depl oyment" sides 

  
I'd like to say the template idea is a really good one. 
  

  
I found the EAN.UCC document had a very good outline and broke 
  apart the 
sections of MSH in a nice way, the parts 
  where it stressed 
compliance with recommended or 
  optional portions of the ebMSG spec struck me 
as "best 
  practices" something we should consider inclusion of or at least 
  
discussion to see if that's a good "best practices" or more 
  specific to EAN 
concerns. The more detailed portions 
  were specific business application of 
ebXML to EAN.UCC 
  only - which I would consider is the details filled into 
the template creating the EAN instance of the IIC standardized template 
  doc. 

  
M. Wang's document has very good specific implementation 
  guidelines but 
doesn't have the organization of tying 
  the details to the more general 
portions of the 
  MSH. 

  
So I propose a good 1st draft strategy is to consider the EAN 
  outline with 
the specific guidelines from M. Wang's 
  document placed in the appropriate 
MSH outline 
  sections and to have something like a fill-in-the-box areas for 
  
business recommendations or requirements for ebXML framework 
  usuage in a 
particular deployment. In this way you've 
  got the pure technical details on 
things like defaults 
  and design approaches, best practices recommendations 
and a placeholder for specific business requirements of a 
  particular 
deployment. 

  
-----Original Message----- 
From: Pete 
  Wenzel [mailto:] 
  
Sent: Monday, June 17, 2002 12:40 PM 
To: Jacques Durand 
Cc: 
  ; ''; 
''; Federico Franciosi; Thomas 
  Bikeev 
Subject: Re: [ebxml-iic] RE: impl guidelines, 
  on the "technical" and 
"deployment" sides 
  

  
Thus spoke Jacques Durand () on Mon, 
  Jun 17, 2002 at 
12:21:11PM -0700: 
> ... 
> As for the "deployment" side of 
  the guidelines, a cooperation path seems 
> to 
  emerge with EAN.UCC, 
> where Federico and Bolivar 
  (EAN), will work with Pete Wenzel 
> 
  (CycloneCommerce), on some 
> "deployment" (or 
  business customization?)  template - whatever name they 
> agree on - that should help 
> user 
  communities to achieve this layer of interoperability beyonf 
> technical MSH interaction, 
> but before 
  payload business content (e.g. as specified by OAG or 
> RosettaNet). 
> EAN would provide a 
  first instance of such template. 
> Such template 
  would also help in standardizing test cases for this 
> layer. 

  
My contact information is found below (please note correct 
  company 
affiliation).  Monica Martin 
  <> has also expressed 
her 
  interest in helping to develop and/or review such a template. 

  
--Pete 
Pete Wenzel 
  <> 
SeeBeyond 
Standards & Product Strategy 
+1-626-471-6311 (US-Pacific) 

  
---------------------------------------------------------------- 
  
To subscribe or unsubscribe from this elist use the 
  subscription 
manager: <http://lists.oasis-open.org/ob/adm.pl>