Build, protect and deploy apps across any platform and mobile device
Leverage a complete UI toolbox for web, mobile and desktop development
Automate UI, load and performance testing for web, desktop and mobile
Build mobile apps for iOS, Android and Windows Phone
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premise data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Automate decision processes with a no-code business rules engine
As you may know, UDDI (Universal Description, Discovery and Integration) was originally designed for publicly accessible registries. As part of making this possible, UDDI includes an "elegant" (engineer speak for "indescribably complex") mechanism for defining taxonomies (known as tModel's for those that have had the pleasure of working with them). It was once thought that taxonomies and categories are supposed to make it easier to find relevant information when you wanted to search for web services.
Then a funny thing happened. First there was Google. No need to scan through a hierarchy of terms to find the relevant terms (which you would have probably organized differently and certainly interpreted differently than the original authors intended) -- you just type in a few terms and voila, you have reasonably relevant matches. People suddenly realized that taxonomies aren't necessary, and in many cases, got in the way. The 1-2 punch came from tagging, comments, ratings, and other "folksonomy" related tools which have all but assured the death of taxonomy based approaches.
SOA What? With all of this Web 2.0 development, it's clear that internet scale folksonomies work far better than taxonomies. On the other hand enterprises are, for the most part, stuck with UDDI-related SOA governance tools and their strict taxonomy and categorization mechanisms. The open question though... is this really a problem?
View all posts from dan foody on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2017, Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.