[sc34wg3] Almost arbitrary markup in resourceData

Mason, James David (MXM) sc34wg3@isotopicmaps.org
Thu, 20 Nov 2003 08:12:33 -0500

Maybe so, but I'm having to deliver TMs to my customers on the basis of what
we have standardized and for what there's support today.


-----Original Message-----
From: Kal Ahmed [mailto:kal@techquila.com] 
Sent: Thursday, November 20, 2003 4:33 AM
To: sc34wg3@isotopicmaps.org
Subject: RE: [sc34wg3] Almost arbitrary markup in resourceData

On Wed, 2003-11-19 at 21:14, Michel Biezunski wrote:
> On Wed, 2003-11-19 at 11:41, Mason, James David (MXM) wrote:
> Oops. I wanted to answer Jim's mail and I just sent it as it was. 
> Sorry about that.
> I wanted to what Jim and Eric said another requirement I have for 
> names. In the topic map application I am currently working on, topics 
> have several names, and they don't play the same role. One is a 
> "privileged name" and the other ones are treated as synonyms.
> From the pure topic map point of view, nothing distinguishes them, and 
> I can't use scope because of the name-based merging rule (because in 
> my case I want them to merge). I can't use topic types because it has 
> nothing to do with names. I don't want to use variants because it 
> doesn't correspond to what I need.

Could you use the proposed [type] property of the topic name information
item (i.e. an <instanceOf> inside a <baseName> element) ? Perhaps you could
have names of type "synonym" to distinguish them from the "privileged" name.

Just a thought...


Kal Ahmed, Techquila
Standards-based Information Management
e: kal@techquila.com
w: www.techquila.com
p: +44 7968 529531

sc34wg3 mailing list