RE: [soa-rm] More on the Diagrams

["Peter F Brown" <peter@justbrown.net>]

Rex:
Thanks for your additional comments. To be sure, I've nothing against what I
called "fancy graphics", I like to use them too, when persuasiveness is key.
As you rightly surmised, my concern is not mixing up what we want to present
to whom. For as long as the graphic is (initially at least) to serve as a
"tool" for our discussion, I would like it kept simple, is all...

I'm glad you didn't take offence: none was intended

-Peter

________________________________

From: Rex Brooks [mailto:rexb@starbourne.com] 
Sent: 30 May 2005 17:28
To: peter@justbrown.net; 'Rex Brooks'
Cc: soa-rm@lists.oasis-open.org
Subject: RE: [soa-rm] More on the Diagrams


Hi Peter,

As I said in the second sentence below: "The fact is I need to add it to my
explanations of SOA and the presentations I have built over the last two
years, so here it is as far as I can take it now, reflecting my own
opinion."

However, as it happens, I agree with you that I should add the "etc," with
regard to "Service Descriptions, T-Models , WSDL Bindings", so I have done
that and have attached it.

If the TC wants to adapt it I will be happy to make the changes (and they
can only be at no charge), and please remember that although I am disclosing
my IPR interest, I also state that I am offering these contributions to the
TC for the TC's use under the same conditions as any other contributions
(that is, specifically that they are free of charge, but not necessarily
unencumbered). I will be happy to produce a version that reflects the TC's
position.

On the more presentational concern, those effects as of wooden drawers are
unintentional. The renderer of the 3D program makes it look that way, and I
won't go into the details of why this is so, nor will I burden folks with
the reasons for the choices I made except to say that I made it as abstract
but readable as I know how. If I have time, and this took more than I should
have allotted for it, I will address those concerns. There is always a
trade-off between the degree of transparency and the type of rendering
algorithms one chooses.

I agree that for the model itself, as opposed to presentational or
educational materials, we should stay with flat diagrams, but I can tell you
from more experience than I want to recall that when attempting to explicate
concepts to the less- or non-technical audiences I often make presentations
for, "fancy" graphics often work where chalkboards don't.

However, we can only do our best, and, given my particular skill sets, my
personal "best" requires that I attempt to translate our concepts into
visual terms my experience tells me will work with some audiences within the
spectrum we will be serving. On that level, we are all obliged to do our own
"best" and represent our own opinons as what we think is appropriate, and on
that we have every right to disagree, which we do, and I applaud you for
doing so without intentionally or unintentionally being disagreeable about
it.

Just as an aside, I have presentations coming up in the next few weeks where
I need to use these, but I will not portray them as representing the TC.
Also, just to be fairly clear, I think we are getting close to a diagram
that I will be satisfied with, so I felt it was worth my effort to get this
underway. I fully expect it will  need to be changed, and I will also
endeavor, if I can, to make it "read" more abstractly than the illusion of
wood grain presently allows.

Thanks for honest and constructive criticism.

Ciao,
Rex


At 4:27 PM +0200 5/30/05, Peter F Brown wrote:

	Rex:
	If you are copyrighting the fancy graphics, fine: but the content is
a mix
	of SOA-RM TC output so far - which belongs to all of us - or stuff
not
	directly related and which I do not think (at best) reflects the TC
	consensus so far or is (at worse) misleading.
	Also, the phrase "Registries-Repositories facilitate discovery of
service
	descriptions, T-Models, WSDL Bindings" should at the very least have
an
	"etc." at the end. I would not otherwise be happy that this is a
statement
	of our position.
	On a more presentational concern: I think it is not a good idea to
represent
	an abstract reference model using "real life" images. The (what look
like)
	nested wooden drawers at the bottom are misleading. These concepts
(and they
	are no more concrete than that for the RM) are not nested, for
starters...
	I strongly feel we should keep it as a simple "chalkboard" drawing.
Let's
	agree the diagram first...then maybe we could commission you to come
up with
	a nice figure (and the graphics are good, they just need to be
appropriate

	too)
	
	-Peter
	
	-----Original Message-----
	From: Rex Brooks [mailto:rexb@starbourne.com]
	Sent: 30 May 2005 03:38
	To: soa-rm@lists.oasis-open.org
	Subject: [soa-rm] More on the Diagrams
	
	Hi Folks,
	
	I decided to go ahead  and build one of my presentation type
diagrams,since
	I will inevitably do so and waiting until we have finalized the RM
will not

	allow me to use it in the interim. The fact is I need to add it to
my
	explanations of SOA and the presentations I have built over the last
two

	years, so here it is as far as I can take it now, reflecting my own
opinion.
	While I am willing to donate it to the TC according to the OASIS
guidelines,
	I am hereby giving the chair official notice that my copyright rides
along,
	free of charge only to the TC for use in the RM, and that I am
willing to
	make reciprocal agreements with any company or individual
	(independent) OASIS member for royalty-free use of my materials
between that
	organization and Humanmarkup.org, Inc., the non-profit I represent
and to
	which I am donating this work for this purpose. I am also including
a sister
	diagrams that reflects how I see this diagram of RM fitting into the
Web
	Services Stack and the OSI Model. Please note that I represent the
overlap
	of OSI layers by repeating the Application Layer. The diagram titled
SOA-RM
	Infrastructure reflects my interpretation of Ken Laskey's diagram
but with
	Service Description subsumed in the Registry/Repository-SOA RM
Central
	Stack.
	I wanted to show that the Resources and Service Consumers connect to
the
	common infrastructure of the Internet with Intranets considered as
part and
	parcel of that backbone, while Services aggregate and coordinate
those
	resources through the central registry model.
	
	Ciao,
	Rex
	
	P.S. I leave the Mind-Map to those more familiar with it, since I am
more
	familiar with the task of explaining and building graphics to aid
that.
	--
	Rex Brooks
	President, CEO
	Starbourne Communications Design
	GeoAddress: 1361-A Addison
	Berkeley, CA 94702
	Tel: 510-849-2309



-- 

Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-849-2309