RE: [regrep] Clarification of 3 implementations requirement

["Matthew MacKenzie" <matt@yellowdragonsoft.com>]

Joe,

And those folks in the federal space making that claim are correct, in
my estimation.  My company, Yellow Dragon, is the only one offering a
COTS product actively.  There is another outfit offering a COTS product,
but it seems as though they are only offering EJB entity beans of RIM
and not a full blown product.

We'll pay finders fees if people can convince our federal friends that
the absence of strong vendor support is a good thing due to shorter
evaluation cycles :-)

-matt

-----Original Message-----
From: Chiusano Joseph [mailto:chiusano_joseph@bah.com] 
Sent: Thursday, May 29, 2003 6:29 PM
To: Matthew MacKenzie
Cc: 'ebXML Regrep (E-mail)'
Subject: Re: [regrep] Clarification of 3 implementations requirement


On the general subject of COTS ebXML Registry implementations: Do we
believe that there are currently:

(a) Lots of COTS ebXML Registry implementations in the marketplace
(b) A medium level of COTS ebXML Registry implementations in the
marketplace
(c) A very scant level of COTS ebXML Registry implementations in the
marketplace

The reason I ask is that in the federal space, often I hear "ebXML
registry? There are hardly any COTS product implementations available".

Joe

Matthew MacKenzie wrote:
> 
> It seems like a cheat to claim that an instance of an implementation 
> be used to fulfil the OASIS requirements.  I think the spirit of the 
> "3 implementations" rule is to validate that the architecture is 
> implementable.  If 2 Yellow Dragon Software customers were to come 
> forward and claim that they are using an ebXML Registry server, what 
> does that prove?  It proves that we were able to sell the software to 
> 2 customers.
> 
> Another issue is that there are three "registry vendors" that are 
> openly marketing themselves:
> 
> - YDS
> - XMLG
> - ebxmlrr
> 
> All three currently are problematic under the OASIS rules.  YDS & XMLG

> are currently not member organizations (YDS will be), nor is ebXMLRR. 
> http://ebxmlrr.sf.net/ doesn't appear as an OASIS Sponsor or 
> Contributor, although I'm sure Farrukh will just point to Sun's web 
> services grab bag up at java.sun.com and say it's a Sun product :-)
> 
> I think OASIS needs to clarify this, if only to make the 
> organization's intent more clear to us.
> 
> ...and since Peter appears to be getting away with a Blatant Product
> Plug(tm) --
> 
> I hear that you can download an easily installed ebXML Registry 
> product
> here: http://www.yellowdragonsoft.com/downloads/registry/  Explore all
> of the wonders of
> ebXML Registry in moments from the comfort of your home, MySQL server
> installation
> sold separately ;-)
> 
> Matthew MacKenzie
> President & CTO
> Yellow Dragon Software
> http://www.yellowdragonsoft.com
> 
> -----Original Message-----
> From: Peter Kacandes [mailto:pkacande@adobe.com]
> Sent: Thursday, May 29, 2003 4:34 PM
> To: ebXML Regrep (E-mail)
> Subject: RE: [regrep] Clarification of 3 implementations requirement
> 
> I guess the question though would be do you have to be using the 
> specification for your own implementation or do you just have to be 
> successfully using "an" implementation.
> 
> The only implementations that I know of are the ebxmlrr and the xmlg 
> (or is it formerly xmlg now known as yds?). Are there others?
> 
> So, if we (Adobe) are successfully using the os implementation for 
> demonstration purposes, does that count??
> 
> BTW, for those of you that may be interested, we will be doing our 
> demo of PDF/XML forms integrated with the ebxmlrr and web services on 
> Monday at the Federal Enterprise Architecture meeting for Web Services

> subcommittee. If I'm not mistaken, it was Joe that developed the SF424

> schema for egrants that we will be showing integrated with the PDF 
> version of the form.
> 
> If anybody wants it, I can send you a demo pdf file that shows how you

> can get arbitrary customer defined XML data out of PDF forms. Of 
> course, you will need the just released Acrobat 6 to export the data 
> as XML. As an enterprise you can also collect the  data from users 
> with just the free Adobe Reader 6 once you have "enabled" the form 
> with reader extensions.
> 
> cheers
> 
> pk
> 
> -----Original Message-----
> From: Breininger, Kathryn R [mailto:kathryn.r.breininger@boeing.com]
> Sent: Thursday, May 29, 2003 4:02 PM
> To: ebXML Regrep (E-mail)
> Subject: [regrep] Clarification of 3 implementations requirement
> 
> Here is a snip from the TC guidelines for the 3 implementation 
> requirement prior to submission of a TC approved spec to OASIS 
> membership for voting:
> 
> "Certification by at least three OASIS member organizations that they 
> are successfully using the specification. (Despite numerous requests, 
> the OASIS TC Administrator feels it is not in the TC's best interests 
> to further define the meaning of "successfully using". The 
> implementation could really be anything from prototypes or proof of 
> concept all the way up to shrink-wrapped software. Defining this 
> further would only restrict the definition and make it harder for 
> member organizations to say that they are successfully using the 
> specification.) This certification can be in the form of a simple 
> statement in email from a company representative, e.g. "I certify that

> XYZ company is successfully using...." The implementers must also 
> certify that their implementations comply with known IP encumbrances."
> 
> See http://www.oasis-open.org/committees/guidelines.php#spec_standard
> for the full requirements.
> 
> Kathryn Breininger
> CENTRAL Project Manager
> Emerging Technologies
> Boeing Library Services
> 
> 425-965-0182 phone
> 425-237-3491 fax
> kathryn.r.breininger@boeing.com
> 
> You may leave a Technical Committee at any time by visiting 
> http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_work
> gr
> oup.
> php
> 
> You may leave a Technical Committee at any time by visiting 
> http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_work
> gr
> oup.php
> 
> You may leave a Technical Committee at any time by visiting 
> http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_work
> group.php