[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: FW: Proposal: A Registry Browser GUI tool
Message text written by "Burdett, David" >-> The BusinessProcessCollection contains BusinessProcessDescriptors. A BusinessProcessDesciptor contains one reference to an IdentifiableBusinessProcess, which could be a reference into a Registry for a RegisteredBusinessProcess (default), or some user-defined way (same issue as Partyid and URI default). A BusinessProcessDescriptor also contains a list of steps/actions that the business supports within that IdentifiableBusinessProcess. Each supported step/action contains a list of technology capabilities (perhaps ranked to support spontaneous business invocation success likelihood) that indicate what *can* be used, not what *will* be used. None of this is an agreement, and all of it is associated with a Party. <<<<<<<<<<<<<<<<<< Scott - oh yes - you knew I was going to like this - and then a getRegisterBusinessProcess is a 'canned' query that retrieves same and the BP/CC model for this is the default classification scheme within the Registry itself. I'm actively looking at the BP DTD in this context of being able to drive this mechanism. As David Burdett noted - this BP DTD can also simply be an XML doc' that was stored by the SME - example: http://www.aol.com/members/frankspoolservice/ebXML/profile.xml and then registered with a registry service (in this case probably AOL's). Thanks, DW.
Powered by eList eXpress LLC