Where to use X.500?

[Marty Schleiff <[e-mail]>]

I'm trying to figure out what types of applications and
what types of information could benefit from X.500.  So 
far I'm thinking that X.500 is appropriate for information
which meets the following criteria (or a subset thereof):

1) Structured information - Should be able to be represented 
   as an entity with associated attributes.  Documents might
   not be appropriate; but and index to documents probably
   would be appropriate.

2) Frequently accessed information - If it's not frequently
   accessed is it worth the expense to carry it in the 
   Directory?

3) Primarily read only information - Even though some level
   of user-initiated update activity may be acceptable, the 
   ratio of queries to updates should be high.

4) Centrally managed information which is beneficial to many
   information consumers - Human Resources information is 
   probably the most obvious example.

5) Information which may benefit from replication - e.g., for
   performance reasons it may be desireable to dedicate a DSA
   to a specific application and replicate required information
   to that DSA.

6) Latency tolerant information - If the information is 
   replicated, latency measured in hours should be acceptable
   instead of latency measured in seconds.

If anyone has any comments/additions I would sure appreciate
hearing them.

Thanks,

Marty Schleiff
Boeing Corporate Electronic Directory Service   
[phone] 
[e-mail]