I have a few beginner questions about UDDIv3, and UDDI in general:
I.
"Ontology" is the way we describe services, for instance the fields/metadata that gives parameters about the service. So for example language=english, availability=99%, location=us; in this example language, availability, and location would be the ontology set.
"Taxonomy" is how the services are categorized in the registry, categorizes the actual service provided.
Is this a correct understanding?
II.
When a service is UDDIv3 compliant, does this mean that inherently any vendor implementing the standard v3 will be able to be integrated with any other UDDIv3 compliant vendor? For example, if we have several organizations, and each organization chooses a different UDDIv3 compliant vendor to implement their registry, will the overall enterprise registry still be able to serve it's purpose, regardless of vendor product? What does the implementation of the subscription API have to do with this concept?
III.
Why would a UDDIv3 vendor provide an SDK for their product? Are these for using the added features, above and beyond UDDIv3 compliant features? What types of features?
Thanks,
Lisa
I.
"Ontology" is the way we describe services, for instance the fields/metadata that gives parameters about the service. So for example language=english, availability=99%, location=us; in this example language, availability, and location would be the ontology set.
"Taxonomy" is how the services are categorized in the registry, categorizes the actual service provided.
Is this a correct understanding?
II.
When a service is UDDIv3 compliant, does this mean that inherently any vendor implementing the standard v3 will be able to be integrated with any other UDDIv3 compliant vendor? For example, if we have several organizations, and each organization chooses a different UDDIv3 compliant vendor to implement their registry, will the overall enterprise registry still be able to serve it's purpose, regardless of vendor product? What does the implementation of the subscription API have to do with this concept?
III.
Why would a UDDIv3 vendor provide an SDK for their product? Are these for using the added features, above and beyond UDDIv3 compliant features? What types of features?
Thanks,
Lisa
