RE: [xtm-wg] Re: XTM-ISS Important XLink difference in DTDs

["Dale Hunscher" <dale@supportability.com>]

This is an excellent categorization, based on practical experience. We'll
have to see whether there is a general concern, or if the consensus is that
this kind of detail is beyond the scope of what Topic Maps are intended to
provide. I find myself leaning in the latter direction at the moment; we may
need a separate spec to follow XTM to handle more specialized requirements.

<aside>I have learned a lot reading the posts on this forum--about ontology,
metadata and knowledge management, among other important topics. I have
especially enjoyed being introduced to situation theory by Ann Wrightson's
comments; and also Andrius' work on sequences, hierarchies, and networks,
which has influenced the papers I will be giving at XML Devcon Fall 2000 and
XML 2000. Thanks to all for the many insights being shared freely
here.</aside>

==================================
Dale Hunscher, CEO and Principal Consultant
South Wind Design, Inc. - http://www.swdi.com
A Connectex Consulting Partner - http://www.connectex.com
Publishing Systems and Document Management Solutions
1 (734) 821-0036 voice
1 (734) 821-0037 fax
1 (734) 678-5178 cel
============================
Come hear my talks at
XML DevCon 2000 Fall in San Jose-
http://www.xmldevcon2000.com/session.cfm?page=w21
XML 2000 in Washington DC-
http://www.gca.org/attend/2000_conferences/XML_2000/schedule.htm#wednesday
=========================


-----Original Message-----
From: Ronald Poell [mailto:rapoell@notionsystem.com]
Sent: Wednesday, September 27, 2000 4:19 AM
To: xtm-wg@egroups.com
Subject: [xtm-wg] Re: XTM-ISS Important XLink difference in DTDs


<dale>
I would like to second Graham's concern, or raise one of my own if  I
am not echoing his concern correctly. There is a feeling when reading
all the material on topic Maps that it is a great benefit that
everything is a topic, and on one level that is true. On another
level, though, if everything is a topic, but there are many different
flavors of topics, processing of topics will rightfully ignore their
topic-ness and focus on their flavors. Sometimes it is better to have
different entities for different purposes, even though they may *also*
have some part of their nature in common.
</dale>

I would like to express my practical experience that completely
follows Dale's ideas.
In Notion System it seemed "logical" to distinguish the following
types of entities which are structurally (implementation technically)
all, in terms of TM, topics:
	Topics: general contents entities
	Classes of topics: allowing a grouping of similar topics (e.g.
man)
	Superclasses of topics: allowing grouping of classes (e.g.
person)
	Associations: meaning and content bearing entities (e.g. is
born: to a place and with date and time)
	Languages: Because they play a particular role in specifying
the names of topics
	Language families: allowing grouping of languages
	Messages: General text based entities used in interface
localization
	Metadata: Used for maintenance aspects of the essential
information
This specialization is naturally grown from practical use and the need
to be able to execute a particular action on blocks of topics,
associations, etc.

===================
Ronald Poell
Consultant Knowledge Management
TNO-FEL
Oude Waalsdorperweg 63
P.O. Box 96864
NL-2509 JG The Hague
Netherlands

T: +31 70 374 02 00
F: +31 70 374 06 52
Email: poell@fel.tno.nl

Notion System: www.notionsystem.com
Email: rapoell@notionsystem.com




To Post a message, send it to:   xtm-wg@eGroups.com

To Unsubscribe, send a blank message to: xtm-wg-unsubscribe@eGroups.com


-------------------------- eGroups Sponsor -------------------------~-~>
Radiohead:  I never thought I could feel this way about a RF front end.
Bit-banger:  I know what you mean.  That baby's a beaut!
YOU ARE NOT ALONE.  CONNECT WITH PEOPLE IN YOUR INDUSTRY
http://click.egroups.com/1/9274/4/_/337252/_/970067882/
---------------------------------------------------------------------_->

To Post a message, send it to:   xtm-wg@eGroups.com

To Unsubscribe, send a blank message to: xtm-wg-unsubscribe@eGroups.com