[sc34wg3] parid0361

[Sam Hunting]

REF: parid0349
TXT:  A set of role types must be specified, each member of which will
always be represented in all instances of the assertion type in the topic
map graph, regardless of whether they have role players.

FIX: The definition must specify a set of roles, each element of which
will always be represented in all instances of the assertion type in the
topic map graph, whether it is played, or not.

COM: Prefer "element" over "member" to avoid confusion with "asociation
members." 
END

REF: parid0347
TXT:  For each assertion type, a name that is unique among all the names
of assertion types, role types, and properties defined by the TM
Application must be specified.

FIX: The definition must specify, for each assertion type, a name that is
unique among all the names of assertion types, role types, and properties
defined by the TM Application
END

REF: parid0354
TXT:  For each role type, a name which is unique among all the names of
assertion types, role types, and properties defined by the TM Application
must be specified.

FIX: The definition must specify, for each role type, a name which is
unique among all the names of assertion types, role types, and properties
defined by the TM Application
END

REF: parid0450
TXT:  In all conforming TM Applications, two assertions are merged to
become a single assertion when their respective a-nodes are deemed to
represent the same subject. All TM Applications are required to define
merging rules that apply uniformly to all assertions, such that they will
always be merged during the process of converting a well-formed topic map
graph into a fully merged topic map graph under the conditions described
in the following subclauses, and such that they will be automatically
merged under no other conditions and on no other basis:
FIX: In all conforming TM Applications, two assertions are merged to
become a single assertion when their respective a-nodes are deemed to
represent the same subject, i.e. when:
END

REF: parid0377
TXT: If neither assertion specifies its assertion type, it cannot be
assumed that the lack of an assertion type itself constitutes a specific
assertion type which is the same for both.
FIX: Untyped assertions never merge.
END

REF: parid0378
TXT: or both have no role players
FIX: both roles are unplayed
COM: "have" is vague
END


Sam Hunting
eTopicality, Inc.

---------------------------------------------------------------------------
Co-Editor, ISO Reference Model for Topic Maps 

Topic map consulting and training: www.etopicality.com
Free open source topic map tools:  www.gooseworks.org

XML Topic Maps: Creating and Using Topic Maps for the Web.
Addison-Wesley, ISBN 0-201-74960-2.
---------------------------------------------------------------------------