Re: FAQ document review minutes

[Ed Julson <ed.julson@eng.sun.com>]

William,

Please see CAPS below for comments and input to the questions you raise.

Ed

> Date: Wed, 16 Aug 2000 20:02:08 -0400
> From: "William J. Kammerer" <wkammerer@foresightcorp.com>
> Subject: Re: FAQ document review minutes
> To: ebXML Awareness Team <ebxml-awareness@lists.ebxml.org>, 'ebXML 
Coordination' <ebxml-coord@lists.ebxml.org>
> MIME-version: 1.0
> X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
> Content-transfer-encoding: 7bit
> X-Priority: 3
> X-MSMail-priority: Normal
> List-Owner: <mailto:ebxml-awareness-help@lists.ebxml.org>
> List-Post: <mailto:ebxml-awareness@lists.ebxml.org>
> List-Subscribe: 
<mailto:ebxml-awareness-request@lists.ebxml.org?body=subscribe>
> List-Unsubscribe:  
<mailto:ebxml-awareness-request@lists.ebxml.org?body=unsubscribe>
> List-Archive: <http://lists.ebxml.org/archives/ebxml-awareness>
> List-Help: <http://lists.ebxml.org/doc/email-manage.html>, 
<mailto:ebxml-awareness-request@lists.ebxml.org?body=help>
> 
> Tim:
> 
> Thanks for the review of the ebXML FAQ.  I agree wholeheartedly with
> most of the Quality Review team's suggestions in EbXML QR FAQ Aug11.doc
> at http://lists.ebxml.org/archives/ebxml-coord/200008/bin00004.bin.  The
> original FAQ document  is ebXML FAQ-latest.doc at
> http://lists.ebxml.org/archives/ebxml-awareness/200005/doc00000.doc.
> We've learned a lot since the Executive Committee was interviewed at the
> Orlando meeting to come up with the FAQ answers;  we'll make the changes
> and submit them back to you for another five day review.
> 
> Yes, ebXML is more than just message content.  We will emphasize
> business process models, core objects, the Registry-Repository and the
> Transport, Packaging and Routing (or "Messaging" framework).  Reference
> to EDI will be de-emphasized or eliminated entirely so ebXML is not
> thought of as old legacy EDI in new clothing.

LET'S NOT THROW THE BABY OUT WITH THE BATH WATER. THERE'S A COUPLE OF DECADES OF 
SUCCESSFUL EXPERIENCE THAT EDI PROVIDES US. SURELY, WE CAN TAKE THE GOOD THINGS 
OUT OF THE EDI SPACE AND NOT HAVE TO COMPLETELY REINVENT THE WHEEL FOR CORE 
COMPONENTS AND BUSINESS LOGIC. I DON'T SEE ANYTHING WRONG WITH TAKING THE BEST 
THAT EDI HAS TO OFFER AND BUILDING AN OPEN, INTERNET BASED IMPLEMENTATION AROUND 
IT. 
> 
> Do you have suggestions for answering why XML is to be used as a basis
> for ebXML?  We can talk about broad internet standards like XML, schema,
> etc.  Help me out here.
> 
> Yes, B2C is out of scope of ebXML - we'll use your language.

B2B IS OBVIOUSLY OUR HIGHER PRIORITY, BUT THERE'S REALLY NO REASON WHY B2C 
COULDN'T TAKE ADVANTAGE OF THE TR&P SPEC OR OTHER INDIVIDUAL COMPONENTS OF 
EBXML.  
> 
> SMEs' needs addressed not so much (directly) by exploiting open
> standards, but because ebXML facilitates development of shrink-wrapped
> solutions for B2B interoperability.  Will add section on reducing need
> for up-front negotiation (e.g., tpaML).
> 
> We can now name-drop now that we have a better idea of the orgs which
> will adopt ebXML framework, such as OTA and RosettaNet.

LET'S NOT FORGET GCI.
> 
> Deliverables and Milestones question will be filled in with detail as
> you suggested.

TO MY KNOWLEDGE, THIS INFORMATION DOESN'T EXIST YET.
> 
> Do you have reasons why ebXML will reduce costs?  Shrink-wrapped
> software for the SME?  Reduced need for up-front TP negotiation?  How
> does Registry/Repository reduce costs?

EBXML WILL REDUCE COSTS BY AUTOMATING THE EXCHANGE OF INFORMATION BETWEEN 
COMPANIES. ANY TIME A HUMAN BEING HAS TO TOUCH A DOCUMENT, IT ADDS COST AND 
INCREASES THE CHANCE OF ERRORS. AUTOMATED DOCUMENT EXCHANGE SPEEDS TRANSACTION 
TURNAROUND TIME, SPEEDS CYCLE TIMES,  AND SIGNIFICANTLY REDUCES COST - ALL OF 
WHICH TRANSLATE TO COMPETETIVE ADVANTAGE.  

THE KEY ADVANTAGE TO REG/REP IS THAT IT PROVIDES A PUBLIC DISCOVERY MECHANISM 
FOR THE COMMON VOCABULARIES THAT ARE BEING CRANKED OUT NOW IN NUMEROUS VERTICAL 
MARKETS. IT ENABLES A "BEST OF BREED" APPROACH TO THE DEVELOPMENT AND DEPLOYMENT 
OF BUSINESS VOCABULARIES AND MAKES IT EASIER FOR TRADING PARTNERS TO FIND A 
SCHEMA THAT THEY CAN AGREE TO USE. REG/REP ALSO PROVIDES THE ABILITY FOR VERSION 
CONTROL MANAGEMENT OF SCHEMAS; SOMETHING THAT WILL BE MORE IMPORTANT OVER TIME.

YOU CAN THINK OF A SCHEMA REPOSITORY AS A PUBLIC LIBRARY, WHERE SOMEONE CAN 
SEARCH FOR SCHEMAS MUCH THE SAME WAY AS A LIBRARY PROVIDE SOPHISTICATED SEARCH 
CAPABILITES WITH COMPUTERIZED INDEXING SYSTEMS TODAY.
> 
> Is there any competitive advantage to using ebXML besides something to
> the effect that if my competitor is using it and I'm not, then I will
> not be invited to the dance?  This is kind of a negative message which
> was always used to justify legacy EDI.  Folks won't buy the same
> argument twice!
> 
> We'll change the EDI investment preservation question around to
> emphasize that we're building on experience and expertise gained from
> EDI.
> 
> Do you have reasons as to why an organization should join ebXML?
> 
> All negative spins will be removed as you suggest.  EDI will be
> de-emphasized.
> 
> William J. Kammerer
> FORESIGHT Corp.
> 4950 Blazer Memorial Pkwy.
> Dublin, OH USA 43017-3305
> +1 614 791-1600
> 
> Visit FORESIGHT Corp. at http://www.foresightcorp.com/
> "Commerce for a New World"
> 
> 
> ----- Original Message -----
> From: Tim McGrath <tmcgrath@tedis.com.au>
> To: 'ebXML Coordination' <ebxml-coord@lists.ebxml.org>
> Sent: Wednesday, August 16, 2000 5:56 PM
> Subject: FAQ document review minutes
> 
> 
> 
> Here are the notes i made during our document review last friday.
> 
> technically, we are supposed to respond by Friday - so i suggest i
> collect any comments/changes by email and send the final copy to the MAE
> and STC lists on Friday.
> --
> regards
> tim mcgrath
> TEDIS   fremantle  western australia 6160
> phone: +618 93352228  fax: +618 93352142
> 
> 
> 
> 

=====================================================
Ed Julson			Sun Microsystems
XML Marketing			901 San Antonio Rd.
XML Technology Center		MS UMPK16-201
				Palo Alto, CA 94303

ed.julson@eng.sun.com
650-786-9258 (x89258)
=====================================================