[sc34wg3] TMCL 6.7 Overlap Declaration

[Steve Pepper]

* Lars Marius Garshol
| 
| * Steve Pepper
| >
| > The point to be made is that if this kind of overlap is the most
| > common, then the mechanism provided by TMCL for overriding the
| > default is suboptimal. The reason for this is that TMCL requires
| > every pair of non-disjoint types to be specified separately.
| 
| Actually, it doesn't, although you need to read the draft very
| carefully to see it. The template uses only two overlaps associations,
| but there's nothing to stop you from putting in more. Indeed, the
| schema says:
| 
| tmcl:overlap-declaration isa tmcl:topic-type;
|    # ...
|    plays-role(tmcl:allows, tmcl:overlaps, 2, *);
|    # ...
| 
| The global validation rule in 6.7 has been written in such a way that
| it works for any number (greater than 1) of overlaps associations on
| the same declaration.

So, in the case I cited, I would need to:

(1) define a new template that allows 20 overlaps associations
(2) call that template and specify all 20 subtypes of Instrumentalist

Correct?

If this is true, it is clearly better than having to specify 20! pairs of topic
types. But it is still too much work when creating a TMCL schema (especially
since there may well be multiple types whose subtypes are not disjoint).