introducing Classifier Sections (CSects)

Norm made a comment that tags are CSects. That got me thinking.

In eariler implementations of AgileWiki, we had a variety of rich classifiers for expressing relationships: names, includes, tags, matches, -tags and -matches, each with its own specialized implementation. Further, there were limits imposed, like only being able to assign a single value to a tag. Rolonicly, these are all CSects. Perhaps we should go for a more uniform implementation in AW3?

Lets have CSect rolons. Usage is "CSect". And they are first class user objects. Then for each type of CSect, we would of course have a different DescriptorUnit. This will help especially in the implementation of the ApplicativeContext, which would then simply be the ordered list of CSects. Now it is easy to have more than one CSect for a given tag, each with its own value. It also becomes easy, or at least reasonably possible, to extend CSects to include other semantic relationships.

You may have noticed that to date I have not implemented any of these CSect types except for tags, which is acknowledged to be a broken implementation as I want to reduce tags to being Cabinet in scope. So there's not a lot of code to be ripped out to do this.

Norm, what do you think? With JSects and CSects as first class user objects, AgileWiki3 should get pretty interesting, mm? I'm thinking also that this should make AW easier to explain from a Rolonic perspective. Its really gotten to the point where everything in AW3 is clearly identified as Classifier, Descriptor, Ledger or Journal, with structure being a special case of Classifier.

Bill