[topicmapmail] external resources reifying

Wed, 11 Feb 2004 18:43:59 +0100

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body>
Hello,<br>
<br>
I am currently trying to create a topic map about some hardware and software
system. The topic map is mainly based on technical documentation about the
design, the functionalities, of the system.<br>
<br>
The approach I have at this time is the following: the topic map contains
"normal" topics (T) as well as topics reifying the resources (T(R)), the
bunch of documents of the technical documentation mentioned above. Then the
"normal" topics have occurrences pointing to these topics T(R) (and can also
have short internal occurrences). These two concepts are synthesized in post
scriptum.<br>
<br>
In my approach, resource metadata (facet.. ?) are implemented by the use
of internal occurrences in the T(R). The metadata provide information that
are properties of the external resource, and do not change whatever the application
or the use of the resources ( a graphic file is always a graphic file, a
text always has the same language, and so on). this seems coherent.<br>
<br>
On the other hand, a piece of text could be seen differently depending on
the topic from which it is an occurrence. I guess this should be implemented
by use of scope or type of the occurrence, in the topic T. In my case, I
would use scope since I would limit the use of type of occurrence to indicate
if internal or external.<br>
<br>
But what botters me is that this information would be part of the "normal"
topic map, and would be lost if we only keep the external resources and the
associated topics that reifies them. I imagine that the external resources
could be used elsewhere. In that case, one could receive the associated reifying&nbsp;
topics, in order not to do the work again. One can imagine that the various
points of view on a resource are also kind of metadata of the resource.<br>
<br>
Does anybody have a comment or clue on the approach of reifying each piece
of resource with a dedicated topic, the implementation of the resource metadata...<br>
<br>
Thanks...<br>
<br>
Olivier Lamborelle<br>
<br>
<br>
<br>
PS: additional information:<br>
<br>
Principles of the reification of the external resources:<br>
 - each piece of external resource is reified by 1 topic: T(R);<br>
 - the type of the topic T(R) indicates that it reifies an external resource:
T(R) type = external;<br>
 - the scope of the topic T(R) is not used (at this time);<br>
 - an occurrence of type external for this topic provides the link to the
external resource;<br>
 - other occurrences of type internal provide metadata about the external 
resource like: language, size, origin, date of last update&#8230;;<br>
 <br>
 Principles of the occurrences for the other topics of the topic map:<br>
 - any topic T can include one or several occurrences to external resources<br>
 - each of these occurrences actually refers to a topic reifying the external
resource (as mentioned above)<br>
 - the type of these occurrences indicates that it points to an external
resource: external (or more exactly to a topic reifying an external resource)<br>
 - the scope of these occurrences is used to specify the role of the occurrence, 
i.e. the kind of information the external resource will provide: design information, 
functional description, biography, block diagram..<br>
 - of course, the topic can also include internal occurrences, directly containing
data about the topic subject itself<br>
<br>
<br>
<div class="moz-signature">-- <br>
O. Lamborelle<br>
 System &amp; Operations Engineer<br>
 <br>
 <b>Space Applications Services NV</b><br>
 Leuvensesteenweg 325<br>
 B-1932 Zaventem<br>
 BELGIUM<br>
 <br>
 <br>
 Tel: +32 2 721 15 81<br>
 Fax: +32 2 721 54 44<br>
 URL: <a href="http://www.spaceapplications.com" target="blank">http://www.spaceapplications.com</a><br>
 </div>
</body>
</html>