KERML — validateSpecificationSpecificNotConjugated Typo and over Constraint

Constraints section
2nd sentence:
"The specific Type of a Generalization cannot be a conjugated Type."
1st issue, typo: Replace Generalization with Specialization

2nd issue, serious: This prevents Conjugated Types from specializing the Conjugated Types of their originalTypes more general Types.

We probably should allow Specialization between Conjugated Types if their originalTypes have the a Specialization relationship (in the same direction). Or maybe it's implied?

Merge with KERML-96

The editorial issue has already been reported in KERML-96.

On the more serious point, it was decided during the language design of the conjugation relationship that it would be semantically cleanest not to mix conjugation and specialization. Conjugated types are intended to provide an essentially syntactic simplification for matching inputs and outputs across connectors, not to introduce a different classification hierarchy from that modeled with the non-conjugated original types.

So, the intent is specifically that a conjugated type not specialize any conjugated types of its original types. Conjugation happens independently at each level of the a classification hierarchy, as desired by the modeler.