The sources for topic map patterns I mentioned yesterday use a variety of modeling languages:
Data Model Patterns: Conventions of Thought by David C. Hay. (Uses CASE*Method™ (Baker’s Notation))
Domain-Driven Design: Tackling Complexity in the Heart of Software by Eric Evans. (Uses UML (Unified Modeling Language))
Developing High Quality Data Models by Matthew West. (Uses EXPRESS (EXPRESS-G is for information models))
The TMDM and Kal’s Design Patterns both use UML notation.
Although constraints will be expressed in TMCL, visually it looks to me like UML should be the notation of choice.
Will require transposition from non-UML notation but seems worthwhile to have a uniform notation.
Any strong reasons to use another notation?