parid2001 | Mon, 03 Mar 2003 09:28:20
1. A name that is different from the name of any known TM Application.
2. Definitions of the properties of subjects and their value types. Such
definitions must indicate which property values are to be used to
distinguish subjects and which are not.
3. If there are any constraints on the values of the properties of
subjects, those must be stated.
4. Definition of properties that subjects obtain by virtue of their
participation in an assertion, if any, other than as a role player in
the assertion.
5. Definition of the types of assertions that can be made about
subjects, including the roles in each assertion, constraints on when
such assertions may be made, and any property values obtained by
subjects that are role players in such assertions.
6. For properties that are used to distinguish subjects, one for the
other, any rules for determining the consistency of property values of
any subject.
7. For predefined subjects, those required to be in any TM instance, the
subject and any property values that it possesses.
8. Rules for when subjects will be deemed to be the same subject on the
basis of properties used to distinguish one subject from another.
9. Rules for combining properties of predefined subjects, if desired,
during merging of subjects.
10. For each defined interchange syntax, a mapping of the syntax to
appropriate topic map graph constructs to facilitate comparison to these
What I am thinking is that this allows us to fairly succiently and
compellingly, state the requirements for any TM Application.