[topicmapmail] external resources reifying

[Jan Algermissen]

> Olivier Lamborelle wrote:
> 
> Hello,

Hello Olivier--

> 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.
> 
> 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). 

This seems the right way to do it (with XTM), although I am not clear about what you mean
by "have occurrences pointing to these topics". I think you mean

<topic id="a-document">
  <subjectIdentity>
    <resourceRef xlink:href="http://foo/doc1.xml" />
  </subjectIdentity>
  <!-- meta data goes here as occs -->
</topic>

<topic id="valve16">
  <occurrence>
    <resourceRef xlink:href="http://foo/doc1.xml" />
  </ocurrence>
</topic>

I personally favor a combination of XTM and RDF+DublinCore, because using RDF
is much less painful for expressing resource metadata than XTM. Of course this
depends on the capabilities of the TM software you use but I thought I'd
mention it anyway.


These two concepts are synthesized in post scriptum.
> 
> 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.


Yes.

> 
> On the other hand, a piece of text could be seen differently depending on the topic from which it is an occurrence. 

Why?  Can you give an example of what you have in mind?

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.
> 
> 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  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.

Hmm...I think I don;t really understand what you mean by 'internal' and 'external' resource. Can
you explain these terms.

> 
> 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...

I think what you do is correct, but a snippet of the topic map or an example showing
your approach would be really helpful.


Is the topic map the primary storage for all the information or is it an intermediary
format between some database and your information system?


> 
> Thanks...
> 
> Olivier Lamborelle
> 
> PS: additional information:
> 
> Principles of the reification of the external resources:
> - each piece of external resource is reified by 1 topic: T(R);
> - the type of the topic T(R) indicates that it reifies an external resource: T(R) type = external;

Isn't it sufficient that the topic has a subject address? Why do you need an additional type?

> - the scope of the topic T(R) is not used (at this time);

Huh? Topics don't have scope...what do you mean?

> - an occurrence of type external for this topic provides the link to the external resource;
> - other occurrences of type internal provide metadata about the external resource like: language, size, origin, date of last update...;

Hmm...if you use the type of an occurrence for internal/external....how do you express that it
is size,origin, date etc...?

> 
> Principles of the occurrences for the other topics of the topic map:
> - any topic T can include one or several occurrences to external resources
> - each of these occurrences actually refers to a topic reifying the external resource (as mentioned above)
> - the type of these occurrences indicates that it points to an external resource: external (or more exactly to a topic reifying an external
> resource)
> - 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..
> - of course, the topic can also include internal occurrences, directly containing data about the topic subject itself

Jan



> 
> --
> O. Lamborelle
> System & Operations Engineer
> 
> Space Applications Services NV
> Leuvensesteenweg 325
> B-1932 Zaventem
> BELGIUM
> 
> Tel: +32 2 721 15 81
> Fax: +32 2 721 54 44
> URL: http://www.spaceapplications.com
> _______________________________________________ topicmapmail mailing list topicmapmail@infoloom.com
> http://www.infoloom.com/mailman/listinfo/topicmapmail

-- 
Jan Algermissen                           http://www.topicmapping.com
Consultant & Programmer	                  http://www.gooseworks.org