RE: [regrep] RE: Updated ROWS proposal ...

["Patil, Sanjay" <SPatil@iona.com>]

The OASIS Registry charter nowhere says that the objective of the TC
is - "Keeping OASIS Registry as general purpose as possible...".

What it says is - "Registry TC seeks to develop specifications that serve 
a wide range of uses, covering the spectrum from general purpose document 
registries to real-time business-to-business registries."

A very general purpose specification generally ends being referenced in
academic researches and other specification's References section, IMO.
The current registry charter of covering a broad spectrum from general
purpose to very specific user group makes lot of sense to me, from this
context.

By the way, the ROWS proposal does not swing the usefulness of the 
Registry so drastically in either direction (very general purpose to 
solving only one particular problem), as has been perceived by a few
members.

In addition, the ROWS proposal does not harm in any way the general purpose
applicability of the Registry spec, as it does not take out any
functionality.
It however makes the life of the general purpose users a lot easier,
as it proposes a solution for a very "general" problem.

thanks,
Sanjay Patil
----------------------------------------------------------------------------
------------------------------
IONA
Total Business Integration (TM) 
Phone: 408 350 9619                                 http://www.iona.com


-----Original Message-----
From: Scott Hinkelman [mailto:srh@us.ibm.com]
Sent: Friday, October 19, 2001 6:12 AM
To: Munter, Joel D
Cc: Oasis Registry TC
Subject: Re: [regrep] RE: Updated ROWS proposal ...


Agreed. I am opposed to ROWS.

Keeping OASIS Registry as general purpose as possible will maximize its
success likelihood
and gain the widest support from software vendors, given consideration
toward other efforts underway.

Scott
______________
Scott Hinkelman, Senior Software Engineer
XML Industry Enablement
IBM e-business Standards Strategy
512-823-8097 (TL 793-8097) (Cell: 512-940-0519)
srh@us.ibm.com, Fax: 512-838-1074




 

                    "Munter, Joel

                    D"                    To:     Oasis Registry TC
<regrep@lists.oasis-open.org>                  
                    <joel.d.munter@       cc:

                    intel.com>            Subject:     [regrep] RE: Updated
ROWS proposal ...                      
 

                    10/18/2001

                    01:50 PM

 

 




reply:

This is just a nitpick.  I was curious why Section 3 is entitled Use Cases
and then the key Use Case is described within Section 4.

I have raised objections to this proposal in the past and those objections
stay the same.  I am still against this proposal as it deviates from the
stated purpose of the Oasis ebXML Registry and Repository Technical
Committee.  In this case, I am referring to the statement that the Oasis
ebXML Registry TC  is creating specifications for a general purpose
registry.

Joel


-----Original Message-----
From: Patil, Sanjay [mailto:SPatil@iona.com]
Sent: Monday, October 08, 2001 6:31 PM
To: 'regrep@lists.oasis-open.org'
Subject: Updated ROWS proposal ...



Team,

Attached is an updated ROWS proposal. The change is to reword "Business
Service"
to "Service" such that there is no confusion about the business use case
overlap of
the ROWS proposal with the UDDI proposal.
 <<SupportServiceAndServiceBinding.doc>>
An example business use case targeted by the proposal is outlined in the
section 4
of the proposal. I have cut-pasted the use case below for your convenience.
I hope this
use case is clear enough to stand for the primary objective of the proposal

i.e. Service is a very commonly used object and providing first class
support to Service
will be great value add in making the ebXML Registry readily useful
(out-of-the-box complete
solution without requiring additional Registry software).
A business organization provides an OfficeProductsPurchasing "Service" to
its internal users. The service can be accessed by individuals working in
the organization using the web interface. The same service can also be
accessed by automated purchasing processes in the organization. The web
interface relies on a SOAP/WSDL based "Service Binding" of the Purchasing
service. The Purchasing service also provides an IIOP based "Service
Binding" for the automated business processes in the organization.
The SOAP/WSDL based service binding makes use of the SOAP, WSDL and HTTP
technical "Specifications".  Each of these specifications requires a set of
runtime parameters ex. HTTP URL. The set of runtime parameters for each
technical specification can be perceived as a "Specification Link" between
the technical specification and the instance of service binding.


thanks,
Sanjay Patil
----------------------------------------------------------------------------

------------------------------
IONA
Total Business Integration (TM)
Phone: 408 350 9619                                 http://www.iona.com


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>




----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>