How universal?

I want CompStrm to be a powerful tool for building interesting capabilities. (Application here carries other connotations.) Just keeping every change in the database, some would argue, places a tremendous constraint on applicability. In the past I would have agreed. But things have changed a lot and keep on changing.

Data sets seem to be a pretty useful and barely constrained (non-cyclic structures only, please!) way of organizing things at the top level. Attaching a list of well knowns to a well known adds even more flexibility. Support for references, citations and qualified names adds tremendously to the whole thing. Making it all accessible as a wiki (all be it, a command-based wiki) makes it usable. But do these things constrain the capabilities as well?

Having a document (wiki page) and a list of well knowns attached to every well known seems like a constraint, but these are really optional. And it is nice to be able to attach descriptive material (i.e. the wiki page) to something--potentially a big aid to user comprehension.

I'll note that there's still a lot of flexibility by either defining new well known types or by attaching new types of files to the well known's group. What needs solving is reference/citation processing when new properties are added which may reference other well knowns.

But I think the constraints really lie in what is missing. Like a federated identity service. Always there is just too much to do.