communicated, e.g. defining one as an ontology and the other using RDF.
yet indicate that all these ways talk about the same offer.
realize it (first time buy, repeated buy, w/RFQ, etc).
and decoupled from any specific business protocol.
you counter offer, etc) for the same business commitment.
> those of us that are not exactly following?
> Or is this trivial?
> but the distinctions I made have evidence behind them.
> They are not arbitrary.
> > > of the rules of contract formation.
> > > UNECE Recommendation 31.
> > > (which RosettaNet is actually developing).
> > the same level.
> found in a commercial law book.
> #2 is a description of how to do #1 electronically.
> > No #3 and no #4 seem to be at the same level.
> #3 is a document.  It is not executable.
> #4 is a script meant to be executed.
> already has #3, and is working on #4.
> want to generate #4 from #3 using production rules.
> They'll also generate RDF from #3.
Previous message: Edwin Khodabakchian: "Transforming Integration With XML Web Services"