parid0298 | Sat, 01 Mar 2003 16:30:41
The name of the TM Application must be specified. Care should be taken to select a name that is unlikely to be used as the name of any other TM Application, including other versions and/or conformance levels of an evolving or configurable TM Application. (Each version, conformance level, or other configuration must be regarded as a distinct TM Application for purposes of naming.) This name must be used as the first field of all of the property names that it defines. The name must not include the "name field separator" symbol shared by all TM Applications whose definitions conform to this RM4TM. (See parid0442 Ed.Note 55.)
The name of the TM Application must be specified.
Paragraph conflates serveral requirement that might be easier to
discern if written separately. See suggested additonal text below.
—pdurusau@emory.edu
parid0298 | Sat, 01 Mar 2003 16:30:41
The name of a TM Application must meet the following requirements:
(add)
Beginning of a section with a list of name requirements for TM
Application names
—pdurusau@emory.edu
parid0298 | Sat, 01 Mar 2003 16:30:41
The name of a TM Application must be unique among known TM Applications.
(add)
Explained  by the following note.
—pdurusau@emory.edu
parid0298 | Sat, 01 Mar 2003 16:30:41
Note: Ideally, TM Applications should have universally unique names. That being a practical impossibility, designers of TM Applications are constrained to use names that do not conflict with any known TM Applications. The risk of name conflicts can be minimized by use of URIs for Internet domains controlled by the TM Application designer or registered TM Application namespaces of public organizations such as OASIS, W3C, IDEAlliance, OCLC, Library of Congress or other similar bodies.
(add)
Explanation of requirement and added material from parid0302.
—pdurusau@emory.edu