Mini-language has evolved a lot over the years. Most of the development
has occurred on an as-needed basis, so there is no clear design or
implementation - things just get tacked on over time.
A recent discussion has opened up the possibility to rework the
mini-language <set> element. From my perspective, that task is long overdue.
Also, the schemas are out of date, and they are unnecessarily
complicated. So, those need a thorough going over.
While we are at it, why don't we create a draft design document based on
the current implementation, and then use it to look for other ways
mini-language can be improved? We can all offer suggestions and
comments, agree on a final design, finalize the draft, and then
implement it in code. The design document then becomes the developer's
reference.
What do you think?
-Adrian
