Re: [regrep] ebXML Registry and Workflow

[Duane Nickull <duane@yellowdragonsoft.com>]

Peter:

Good, tough questions to pose. We need to be able to answer these head 
on. There is a lot of good info from the ISO/IEC 11179 that can be used 
to answer these questions.

We could always state the obvious "Becuase we never invented it here"

;-)

Just kidding - no flames please.

Duane

Peter Kacandes wrote:
> Well, this is a question I get within Adobe when I talk about reg/rep.
> 
> Why should I use it (reg/rep) instead of the CMS that I already have?
> 
> We need good answers for that since CMS is already a very established
> category.
> 
> The other question I get is why shouldn't they just use a database?
> 
> Below is a directly quoted excerpt of the types of questions I get. It would
> be very useful to have very crisp answers to these types of inquiries:
> 
> "What are adjacent or competing solutions and what subset of problems is the
> ebXML registry best suited to?  Does this double as a DM/CM repository? Is
> it really a smarter 2nd generation repository?  How does this compete, if at
> all, with solutions offered by ECM or DAM vendors? Why and when use this
> rather than a database?  For what types of problems is it the best solution,
> and for which is it less optimal? Why?"
> 
> 
> cheers
> 
> pk
> 
> 
> -----Original Message-----
> From: Farrukh Najmi [mailto:farrukh.najmi@sun.com]
> Sent: Wednesday, June 25, 2003 7:16 AM
> To: Chiusano Joseph
> Cc: regrep@lists.oasis-open.org
> Subject: Re: [regrep] ebXML Registry and Workflow
> 
> 
> Registry can facilitate workflows like databases can facilitate workflows.
> 
> The ebXML Registry to me is first and foremost a general purpose content
> management system (CMS). This is a step beyond databases since it is not
> restricted to rows and columns.
> 
> It would be good if we can carve out this CMS niche for ourselves and
> establish ebXML Registry as the standard for CM.
> 
> A good starting point may be that we emphasize the CMS aspect of
> registry in all our PRs, presentations, papers and conversations.
> 
> That said, I can see the value of marketing the fact that registry can
> be used to support workflow in ways you suggested.
> 
> --
> Farrukh
> 
> 
> 
> Chiusano Joseph wrote:
> 
> 
>>Oh - and of course BPSS as well!
>>
>>Chiusano Joseph wrote:
>>
>>
>>
>>>[I've got my marketing hat on again]
>>>
>>>It seems to me that there is a high synergy between ebXML Registry and
>>>workflow, from the perspectives of:
>>>
>>>- Registering/maintaining workflow definitions (UML, BPEL4WS, WSCI
>>>scripts, etc.) in an ebXML Registry
>>>
>>>- Associating a CPA with a workflow definition
>>>
>>>- Potentially constructing XML-based workflow definitions (such as
>>>BPEL4WS and WSCI) from vendor tools that access ebXML Registry for the
>>>workflow definitions schemas
>>>
>>>...and probably several more. Does anyone else see this? If so, should
>>>we promote this aspect further?
>>>
>>>Joe
>>>
>>> ------------------------------------------------------------------------
>>>You may leave a Technical Committee at any time by visiting
>>
> http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.
> php
> 
>>>
>>
>>Chiusano Joseph wrote:
>>
>>
>>
>>>[I've got my marketing hat on again]
>>>
>>>It seems to me that there is a high synergy between ebXML Registry and
>>>workflow, from the perspectives of:
>>>
>>>- Registering/maintaining workflow definitions (UML, BPEL4WS, WSCI
>>>scripts, etc.) in an ebXML Registry
>>>
>>>- Associating a CPA with a workflow definition
>>>
>>>- Potentially constructing XML-based workflow definitions (such as
>>>BPEL4WS and WSCI) from vendor tools that access ebXML Registry for the
>>>workflow definitions schemas
>>>
>>>...and probably several more. Does anyone else see this? If so, should
>>>we promote this aspect further?
>>>
>>>Joe
>>>
>>> ------------------------------------------------------------------------
>>>You may leave a Technical Committee at any time by visiting
>>
> http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.
> php
> 
>>>You may leave a Technical Committee at any time by visiting
>>
> http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.
> php
> 
> 
> 
> 
> 
> You may leave a Technical Committee at any time by visiting
> http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.
> php
> 
> 
> You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.php


-- 
Yellow Dragon Software Corp. - http://www.yellowdragonsoft.com
Service Oriented Architectures - ebXML, Web Services, Registry, SOAP
Project Team lead - United Nations CEFACT eBusiness Architecture
+1 (604) 738-1051
***********************************