OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

regrep message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


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



Thanks Joel. Let us separate real issues from nitpicks. For now,
I am focusing on real issues (nitpicks can easily be ironed out later).

The objections that you had raised during the subteam discussion
were taken care by the updated proposal that was submitted to the
broader Registry TC. 

If you still have objections, could you please summarize in bullets
for the understanding of everybody. For the one that you raised
in the following email, I fail to understand how the proposal
deviates from the Registry's charter. Here is a cut-paste from
the oasis web site -
The OASIS ebXML Registry TC develops specifications to achieve interoperable
registries and repositories, with an interface that enables submission,
query and retrieval on the contents of the registry and repository. Further,
the 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. Additionally, as part of its
specification development work, this TC explores and promotes various
emerging models for distributed and cooperating registries. 

Please elaborate. Again, if you could summarize all your important
objections in bullets, that will be awesome.

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


-----Original Message-----
From: Munter, Joel D [mailto:joel.d.munter@intel.com]
Sent: Thursday, October 18, 2001 1:51 PM
To: Oasis Registry TC
Subject: [regrep] RE: Updated ROWS proposal ...


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>


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC