[
Lists Home |
Date Index |
Thread Index
]
"Bullard, Claude L (Len)" wrote:
>
> Please explain how a registry solves the problem
> of including an insecure or unreliable software
> component to process a given part of the composition.
Sure - it could solve it by holding the registry authorities accountable
for testing and "certifying" the reliability of a given software
component, according to criteria that are created as part of the concept
of operations (CONOPS) for the registry, perhaps by the Community of
Interest (CoI) that the registry serves.
> Composability is based on namespaces. What is
> registered, the namespace or the implementation?
Ah, that brings me to a proposal for a "Namespace Manager" function that
I offered to the ebXML Registry TC back in January 2002:
http://lists.oasis-open.org/archives/regrep/200201/msg00061.html
More than 2 years later, I still very much see the need for such a
function as "native" to the registry architecture - we've laid some
foundations in the meantime that have brought us closer to realizing
this goal. I hope this feature will be included in a future version of
the registry specs.
> Does the registry authority vette the implementation?
Depends on what you mean by "vette", and with whom.
> How would that be sustained?
>
> Does the implementor check the registry or does
> the RADE vendor pass a conformance test and then
> is enabled to register the component such that
> selection of a service within the RADE is warrantied?
It all depends on the registry CONOPs and policies.
> Would you conjecture that Homeland Security systems
> such as those that support GJXDM will require
> registration and vetting?
The GJXDM folks have been talking about registries for quite some time,
so I foresee that in the future. They are also now discussing SOAs, so
registries will become even more important than ever.
Kind Regards,
Joe Chiusano
Booz | Allen | Hamilton
Strategy and Technology Consultants to the World
> len
>
> From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]
>
> Some of this will be solved by use of registries (such as UDDI and ebXML),
> in
> which the registry "authorities" are held accountable for the security
> and reliability of the services that are registered there. The UDDI TC
> is in the process of creating a Technical Note called "Representing Web
> Services Quality of Service Information in UDDI" that covers this
> concept. The ebXML Registry specifications also have this capability as
> well, but a Technical Note has not (yet) been created for it.
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>
--
Kind Regards,
Joseph Chiusano
Associate
Booz | Allen | Hamilton
|
