Re: [ebsoa] eBizQ.net Article: "ebXML's Move To SOA:Clearly A Good One"

["David RR Webber" <david@drrw.info>]

Joe,

Part 2 - What winemaking is teaching us about content assembly:-

#1 - Ancient Greeks - delivery involved decanting product directly
       into simple containers with basic structure.  Packaging and security
       was minimal and delivery direct to local customers.
      Context was largely implied.  When mistakes occur they are
      only local and easily remedied in time honoured fashion.  Such
      mistakes are rarely repeated again.

#2 - Romans had more large scale demands, and thus adapted
        Greek practice mainly for delivery in bulk.  This can be
        still seen today with the Italian practice of bottling product
        directly into 50,000 gallon railcar tankers.  The goal is to
        ship as much product as possible over a limited bandwidth,
        with as little direct inspection as possible.  Product has a
        niche use profile (cleaning windows, mopping floors, wiping
        down table tops).  Context is mostly unknown and superfluous.
        Mistakes can occur, and often have wide impact and are
        costly.  Ability to trace the source of the mistake is difficult if
        not impossible.  Customer adoption is characterized by
        forced consumption driven by large distributors to often
        captive markets.  While profits may soar, customer satisfaction
        is low and product loyality non-existent.

#3 - French - benefited from the invention of printing presses and
        hence availability of superior markup.  This has led to
        development of sophisticated ontologies, classifications and
        categorization for content - along with a rich vocabulary to
        describe aspects of the make-up of the product.  Context
        is extremely important.  Compliance checking and
        conformance testing are rigorously adherred too with
        strict tests and procedures.  Product is of the highest quality,
        and is uniformly replicatable.  Integration of product is
        carefully tailored to its delivery environment to match the
        characteristics of the associated products.  Mistakes only
        occur when untrained personnel are assigned in the
        final delivery phase.  Customer adoption and satisfaction
        is high.   Overall costs approach those of cheap unregulated
        processes, especially when maintenance and support costs
        are factored.

What was that waiters name again?  Obviously a MBA candidate
from New Orleans State University.

DW.

----- Original Message ----- 
From: "Chiusano Joseph" <chiusano_joseph@bah.com>
To: "David RR Webber" <david@drrw.info>
Cc: "ebSOA" <ebsoa@lists.oasis-open.org>
Sent: Tuesday, May 04, 2004 4:20 PM
Subject: Re: [ebsoa] eBizQ.net Article: "ebXML's Move To SOA:Clearly A Good
One"


> "Winemaking? CAM can do that!"
>    - April 2004, Waiter, Bourbon Street Restaurant, New Orleans
>
> ;)
>
> David RR Webber wrote:
> >
> > Joe,
> >
> > Great article.  And I like Dave's list of next for ebXML...since
> > CAM does one of those (so OK that was predicatable!) -
> > but he missed:
> >
> > 5) context
> > 6) linking and switching
> > 7) use of registry at runtime, not just design time
> >
> > 4 out of 7 ain't half bad though!
> >
> > DW
> >
> > ----- Original Message -----
> > From: "Chiusano Joseph" <chiusano_joseph@bah.com>
> > To: "ebSOA" <ebsoa@lists.oasis-open.org>
> > Sent: Tuesday, May 04, 2004 3:46 PM
> > Subject: [ebsoa] eBizQ.net Article: "ebXML's Move To SOA: Clearly A Good
> > One"
> >
> > > Has anyone seen this eBizQ.net 4/29/04 article [1] from David
Lincthicum
> > > about our TC? Title: "ebXML's Move To SOA: Clearly A Good One".
> > >
> > > We were so busy on Bourbon St., we didn't notice it...
> > >
> > > Joe
> > >
> > > [1] http://www.ebizq.net/hot_topics/soa/features/4323.html
> > > --
> > > Kind Regards,
> > > Joseph Chiusano
> > > Associate
> > > Booz | Allen | Hamilton
> > >
>
> -- 
> Kind Regards,
> Joseph Chiusano
> Associate
> Booz | Allen | Hamilton
>