[sc34wg3] Unique names in Draft Reference Model

[Anthony B. Coates]

In the RM draft, why are property names, assertion types, and role types forced
to share the same per-application namespace?

====
4.5 Names of properties of nodes
Each property has a name that is unique, within the TM Application, among all
the names of the properties, assertion types, and role types defined by the TM
Application. In a topic map graph, however, property names may be defined by
multiple TM Applications, so different TM Applications may define the same
property name. Therefore, each property name consists of two fields, separated
by the field separator symbol defined in 4.5. The first field is the name of the
TM Application itself, and the second field is the property name which is
unique within the TM Application.
====

Why are these things lumped in together?

	Cheers,
		Tony.
(hope you all had a great Christmas season holiday)
====
Anthony B. Coates, Information & Software Architect
mailto:abcoates@TheOffice.net
MDDL Editor (Market Data Definition Language)
http://www.mddl.org/
FpML AWG Member (Financial Products Markup Language)
http://www.fpml.org/