RE: [soa-blueprints] Joined the tc for...

["Miko Matsumura" <mmatsumura@infravio.com>]

To clarify:
 
The committee itself must publish vendor neutral specifications.
 
That said, the blueprints (once published by the TC) could have vendor specific implementations--much like WS-Security (or name your standard) also have vendor specific *implementations*. These would not be related in any way to the activities of the TC and would be considered a royalty free use of the available intellectual property as published by the TC.
 
Miko
 
-----Original Message----- 
From: Don Flinn [mailto:flinn@alum.mit.edu] 
Sent: Wed 1/25/2006 5:10 PM 
To: soa-blueprints@lists.oasis-open.org 
Cc: 
Subject: Re: [soa-blueprints] Joined the tc for...



	It would bother me if an international consortium such as OASIS, would
	produce a standard that contains vendor specific implementation
	information.  IMHO anything that we produce MUST (RFC 2119) be totally
	vendor neutral.
	
	Don
	
	On Wed, 2006-01-25 at 11:02 -0500, Michael Stiefel wrote:
	> I thought that the SOA RM TC would provide a reference model for SOAs and
	> some reference architectures. The Blueprints group would provide concrete
	> architectures that could have some vendor specific implementations.
	>
	> Michael
	>
	> At 09:56 AM 1/25/2006, marchadr@wellsfargo.com wrote:
	>
	> >Each of use joined the TC for some reason what was it exactly?
	> >
	> >What did each of you expect to get or contribute from it?
	> >
	> >This is the real question it seems.
	> >
	> >- dan
	>
	>
	>
	>
	--
	Don Flinn
	President, Flint Security LLC
	Tel: 781-856-7230
	Fax: 781-631-7693
	e-mail: flinn@alum.mit.edu
	http://flintsecurity.com