[uddi-comment] Best practices: custom categorization taxonomies

[Paul Sterk <paul.sterk@sun.com>]

Hi,

First, thanks to all for the very helpful responses!  I hope not to have
too many more questions:

I am using tModels for a custom categorization taxonomies according to
tn-taxonomy-provider-V1.01-Final-20010717.pdf.  Are there any best
practices for deciding what is an appropriate categorization, or is it
up to the registry provider to decide?

I can think of several different custom taxonomies that could be used to
categorize a web service:

- Version – (e.g., 0.1, 0.2, 1.0, 1.1, 2.0, etc.)
- Deployment type – (e.g., development, prototype, test, production)
- Application criticality – (e.g., Mission Critical, Business Critical,
Business
      Operational, Administrative Services)
- IT Group - (e.g., Sales, Finance, Human Resources)
- Quality of service targets – (e.g., 99.9% available, 99% available,
95% available,
       90% available)
 - Security level – (e.g., 1 – Very High, 2 – High, 3 - Low)

Are there other useful categorizations that have been implemented?

Paul