[topicmapmail] scope or query?

Martin Schouten mfpschou@students.cs.uu.nl
Tue, 9 Nov 2004 14:37:46 +0100


This is a multi-part message in MIME format.

------=_NextPart_000_000F_01C4C669.AE9395F0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Dear readers,

 

I'm (still) looking at ways to effectively customize topic maps to certain
situations. Luckily, I'm making progress after reading a lot of articles on
topic maps and ontology's :-). I basically found two way to customize the
way the TM will look (that is, what topics will be included and excluded).
One way of doing this would be by using a query language (such as TMQL) to
'create' topic maps based on queries such as "show me all topics,
associations and occurrences that are related to project 1" (if possible in
TMQL). The other way of accomplishing this would be by using the
scope-construct in which you define the topics, associations and occurrences
to belong to e.g. "project 1".

 

Assuming this does not sound completely ridiculous, which one of these would
you choose and why?

 

Assuming that this DOES sound like pretty bad reasoning, what alternatives
are there apart from scoping and querying? 

 

Cheers,

 

Martin

 


------=_NextPart_000_000F_01C4C669.AE9395F0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.E-mailStijl17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Dear readers,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I&#8217;m (still) looking at ways to effectively =
customize
topic maps to certain situations. Luckily, I&#8217;m making progress =
after
reading a lot of articles on topic maps and ontology&#8217;s =
</span></font><font
size=3D2 face=3DWingdings><span =
style=3D'font-size:10.0pt;font-family:Wingdings'>J</span></font><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>. I
basically found two way to customize the way the TM will look (that is, =
what
topics will be included and excluded). One way of doing this would be by =
using
a query language (such as TMQL) to &#8216;create&#8217; topic maps based =
on
queries such as &#8220;show me all topics, associations and occurrences =
that
are related to project 1&#8221; (if possible in TMQL). The other way of =
accomplishing
this would be by using the scope-construct in which you define the =
topics,
associations and occurrences to belong to e.g. &#8220;project =
1&#8221;.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Assuming this does not sound completely ridiculous, =
which
one of these would you choose and why?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Assuming that this DOES sound like pretty bad =
reasoning, what
alternatives are there apart from scoping and querying? =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Cheers,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Martin<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_000F_01C4C669.AE9395F0--