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


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] Composability: Do the Emperor's Clothes Fit? (RE: [xml-d

[ Lists Home | Date Index | Thread Index ]
  • To: 'Chiusano Joseph' <chiusano_joseph@bah.com>
  • Subject: RE: [xml-dev] Composability: Do the Emperor's Clothes Fit? (RE: [xml-dev] Costs, benefits, and emperors with wardrobe malfunctions - was Re: [xml-dev] WS-Emperor naked?)
  • From: "Bullard, Claude L (Len)" <clbullar@ingr.com>
  • Date: Tue, 6 Apr 2004 10:39:44 -0500
  • Cc: xml-dev@lists.xml.org

Please explain how a registry solves the problem 
of including an insecure or unreliable software 
component to process a given part of the composition. 

Composability is based on namespaces.   What is 
registered, the namespace or the implementation?

Does the registry authority vette the implementation? 
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?

Would you conjecture that Homeland Security systems 
such as those that support GJXDM will require 
registration and vetting?


From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]

Some of this will be solved by use of registries (such as UDDI and ebXML),
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.


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS