[topicmapmail] Occurrence resource naming
Steve Pepper
steve@ontopia.net
Mon, 6 Dec 2004 19:37:56 +0100
This is a multi-part message in MIME format.
------=_NextPart_000_0360_01C4DBCB.1620AA20
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Occurrence resource naming[I sent this a few hours ago and then realized
that I
sent it from an email account that is not currently
recognized by TopicMapMail. Steve]
Hi Alastair,
Basically, if you want to make *any* assertion about a
resource (except that it is an occurrence of a certain
topic), you have to create a topic to represent the
resource. That's the basis of the whole Topic Maps
paradigm. Giving a resource a name requires making an
assertion about it (as does adding other metadata, such
as 'creation date' or 'author').
So what you need is a topic that represents the resource.
Here it is (modulo possible typos):
<topic id="googleStressSearchTopic">
<subjectIdentity>
<resourceRef
xlink:href="http://www.google.com?q=stress+workplace"/>
</subjectIdentity>
<baseName>
<baseNameString>'Stress' from Google</baseNameString>
</baseName>
</topic>
Note that the *subject locator* (<subjectIdentity> with a
<resourceRef> subelement rather than a <subjectIndicatorRef>
subelement) is the *same URI* as the locator used for the
occurrence. This is enough in XTM to tell a conforming Topic
Maps processor that you are talking about the same resource.
If you are using the Omnigator you will notice that it is
smart enough to display the name of the topic instead of the
URI, as you want (along with an icon, in case the user wants
to go straight to the resource rather than to the topic that
represents it).
This, by the way, is one of the many, MANY features of the
Omnigator that most people don't discover because they don't
RTFM :-) It is documented in the Omnigator User Guide in
the final paragraph of section 4.6:
http://www.ontopia.net/omnigator/docs/navigator/userguide.html#using-PSIs
Hope this helps.
Steve
--
Steve Pepper <pepper@ontopia.net>
Chief Strategy Officer, Ontopia
Convenor, ISO/IEC JTC 1/SC 34/WG 3
Editor, XTM (XML Topic Maps 1.0)
-----Original Message-----
From: topicmapmail-admin@infoloom.com
[mailto:topicmapmail-admin@infoloom.com]On Behalf Of ROBERTS, Alastair
Sent: 6. desember 2004 16:15
To: 'topicmapmail@infoloom.com'
Subject: [topicmapmail] Occurrence resource naming
Hi guys,
I was wondering if there is a simple way of expessing a baseName for an
occurrence? At the moment I might have something like :-
<topic id="webPage">
<baseName>
<baseNameString>Web Page</baseNameString>
</baseName>
</topic>
<topic id="stressInTheWorkplace">
<baseName>
<baseNameString>Stress (In the
Workplace)</baseNameString>
</baseName>
<occurrence id="googleStressSearch">
<instanceOf>
<topicRef
xlink:href="#webPage"></topicRef>
</instanceOf>
<resourceRef
xlink:href="http://www.google.com?q=stress+workplace"></resourceRef>
</occurrence>
</topic>
Which is all very well producing the occurrence
Web Page
a.. http://www.google.com?q=stress+workplace
Whereas what I actually want to pass is something along the lines of :-
Web Page
a.. 'Stress' from google
Normally you could express this with xlink via a show attribute :-
<resourceRef
xlink:href="http://www.google.com?q=stress+workplace"
xlink:show="Stress search from google">
</resourceRef>
But the XML Topic Maps (XTM) 1.0 standard only supports type and href :
<!ATTLIST resourceRef
id ID #IMPLIED
xlink:type NMTOKEN #FIXED 'simple'
xlink:href CDATA #REQUIRED
>
Any ideas?
Visit http://www.bupa.com or call 0800 00 10 10 and find out what BUPA can
do for you.
BUPA, the health and care people
BUPA House 15-19 Bloomsbury Way London WC1A 2BA
Internet communications are not secure and therefore BUPA does
not accept legal responsibility for the contents of this message. Any
views or opinions presented are solely those of the author and do
not necessarily represent those of BUPA.
------=_NextPart_000_0360_01C4DBCB.1620AA20
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Occurrence resource naming</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2523" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>[I sent this=20
a few hours ago and then realized that I</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>sent it from=20
an email account that is not currently</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>recognized=20
by TopicMapMail. Steve]</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New"=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>Hi=20
Alastair,</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New"=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>Basically,=20
if you want to make *any* assertion about a</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>resource=20
(except that it is an occurrence of a certain</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>topic), you=20
have to create a topic to represent the</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>resource.=20
That's the basis of the whole Topic Maps</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>paradigm.=20
Giving a resource a name requires making an</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>assertion=20
about it (as does adding other metadata, </FONT></SPAN><SPAN=20
class=3D982315915-06122004><FONT face=3D"Courier New"=20
size=3D2>such</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>as 'creation=20
date' or 'author').</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New"=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>So what you=20
need is a topic that represents the resource.</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>Here it is=20
(modulo possible typos):</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New"=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2><topic=20
id=3D"googleStressSearchTopic"></FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2> =20
<subjectIdentity></FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New"=20
size=3D2> <resourceRef </FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New"=20
size=3D2> xlink:href=3D"<A=20
href=3D"http://www.google.com/?q=3Dstress+workplace"=20
target=3D_blank>http://www.google.com?q=3Dstress+workplace</A>"/></FON=
T></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New"=20
size=3D2> </subjectIdentity></FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2> =20
<baseName></FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New"=20
size=3D2> <baseNameString>'Stress' from=20
Google</baseNameString></FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2> =20
</baseName></FONT></SPAN></DIV>
<DIV><SPAN=20
class=3D982315915-06122004></topic></SPAN></DIV></FONT></SPAN></DIV=
>
<DIV><FONT face=3D"Courier New" size=3D2></FONT> </DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN =
class=3D982315915-06122004>Note that=20
the *subject locator* (<subjectIdentity> with =
a</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN=20
class=3D982315915-06122004><resourceRef> subelement rather than a=20
<subjectIndicatorRef></SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN =
class=3D982315915-06122004>subelement)=20
is the *same URI* as the locator used for the</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN =
class=3D982315915-06122004>occurrence.=20
This is enough in XTM to tell a conforming =
Topic</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN =
class=3D982315915-06122004>Maps=20
</SPAN></FONT><FONT face=3D"Courier New" size=3D2><SPAN=20
class=3D982315915-06122004>processor that you are talking about the same =
resource.</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2></FONT> </DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>If you are=20
using the Omnigator you will notice that it is</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>smart enough=20
to display the name of the topic instead of </FONT></SPAN><SPAN=20
class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>the</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>URI, as you=20
want (along with an icon, in case the user =
wants</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>to go=20
straight </FONT></SPAN><SPAN class=3D982315915-06122004><FONT =
face=3D"Courier New"=20
size=3D2>to the resource rather than to the topic =
that</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>represents=20
it).</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New"=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>This, by the=20
way, is one of the many, MANY features of =
the</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>Omnigator=20
</FONT></SPAN><SPAN class=3D982315915-06122004><FONT face=3D"Courier =
New"=20
size=3D2>that most people don't discover because they =
don't</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>RTFM :-)=20
</FONT></SPAN><SPAN class=3D982315915-06122004><FONT face=3D"Courier =
New" size=3D2>It=20
is documented in the </FONT></SPAN><SPAN =
class=3D982315915-06122004><FONT=20
face=3D"Courier New" size=3D2>Omnigator User Guide =
in</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>the final=20
</FONT></SPAN><SPAN class=3D982315915-06122004><FONT face=3D"Courier =
New"=20
size=3D2>paragraph of section 4.6:</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2><A=20
href=3D"http://www.ontopia.net/omnigator/docs/navigator/userguide.html#us=
ing-PSIs">http://www.ontopia.net/omnigator/docs/navigator/userguide.html#=
using-PSIs</A></FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New"=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New" =
size=3D2>Hope this=20
helps.</FONT></SPAN></DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New"=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D982315915-06122004><FONT face=3D"Courier New"=20
size=3D2>Steve</FONT></SPAN></DIV>
<P><FONT size=3D2><FONT face=3D"Courier New">--<BR>Steve Pepper=20
<pepper@ontopia.net><BR>Chief Strategy Officer, =
Ontopia<BR>Convenor,=20
ISO/IEC JTC 1/SC 34/WG 3<BR>Editor, XTM (XML Topic Maps =
1.0)</FONT></FONT><FONT=20
size=3D2><FONT face=3D"Courier New"><BR></FONT> </FONT> </P>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B>=20
topicmapmail-admin@infoloom.com =
[mailto:topicmapmail-admin@infoloom.com]<B>On=20
Behalf Of </B>ROBERTS, Alastair<BR><B>Sent:</B> 6. desember 2004=20
16:15<BR><B>To:</B> 'topicmapmail@infoloom.com'<BR><B>Subject:</B>=20
[topicmapmail] Occurrence resource naming<BR><BR></FONT></DIV><BR>
<P><FONT face=3DArial size=3D2>Hi guys,</FONT> </P>
<P><FONT face=3DArial size=3D2>I was wondering if there is a simple =
way of=20
expessing a baseName for an occurrence? At the moment I might have =
something=20
like :-</FONT></P><BR>
<P> <FONT face=3D"Courier =
New"=20
size=3D2><topic id=3D"webPage"></FONT>=20
<BR> =20
<FONT face=3D"Courier New"=20
size=3D2><baseName></FONT> <BR><FONT face=3D"Courier New"=20
size=3D2> =20
=20
<baseNameString>Web=20
Page</baseNameString></FONT>=20
<BR> <FONT face=3D"Courier =
New"=20
size=3D2> =
</baseName></FONT>=20
<BR> <FONT face=3D"Courier =
New"=20
size=3D2></topic></FONT> =
<BR> =20
<FONT face=3D"Courier New" size=3D2><topic =
id=3D"stressInTheWorkplace"></FONT>=20
<BR><FONT face=3D"Courier New" =
size=3D2> =20
<baseName></FONT> =
<BR><FONT=20
face=3D"Courier New" size=3D2> =20
=20
=
<baseNameString>Stress (In=20
the Workplace)</baseNameString></FONT>=20
<BR> <FONT =
face=3D"Courier New"=20
size=3D2> =
</baseName></FONT>=20
<BR><FONT face=3D"Courier New" =
size=3D2> =20
<occurrence=20
id=3D"googleStressSearch"></FONT> <BR><FONT face=3D"Courier New" =
size=3D2> =20
=
=20
<instanceOf></FONT>=20
<BR> <FONT =
face=3D"Courier New"=20
size=3D2> =20
=20
<topicRef=20
xlink:href=3D"#webPage"></topicRef></FONT>=20
<BR> =20
=20
<FONT face=3D"Courier New"=20
size=3D2></instanceOf></FONT>=20
<BR> =20
=20
<FONT face=3D"Courier New"=20
size=3D2><resourceRef xlink:href=3D"<A=20
href=3D"http://www.google.com?q=3Dstress+workplace"=20
=
target=3D_blank>http://www.google.com?q=3Dstress+workplace</A>"></r=
esourceRef></FONT>=20
<BR> <FONT =
face=3D"Courier New"=20
size=3D2> =
</occurrence></FONT>=20
<BR> <FONT face=3D"Courier =
New"=20
size=3D2></topic></FONT> </P>
<P><FONT face=3DArial size=3D2>Which is all very well producing the=20
occurrence</FONT> </P>
<P><FONT face=3DArial size=3D2>Web=20
Page </FONT>=20
<UL>
<UL>
<LI><A =
href=3D"http://www.google.com?q=3Dstress+workplace"><U><FONT=20
face=3D"Times New Roman"=20
=
color=3D#0000ff>http://www.google.com?q=3Dstress+workplace</FONT></U></A>=
<FONT=20
face=3D"Times New Roman"> </FONT><BR><BR></LI></UL></UL>
<P><FONT face=3DArial size=3D2>Whereas what I actually want to pass is =
something=20
along the lines of :-</FONT> </P>
<P><FONT face=3DArial size=3D2>Web Page</FONT>=20
<UL>
<UL>
<LI><U><FONT face=3D"Times New Roman" color=3D#0000ff>'Stress' =
from=20
google</FONT></U> <BR></LI></UL></UL>
<P><FONT face=3D"Times New Roman">Normally you could express this with =
xlink via=20
a show attribute :-</FONT> </P>
<P> <FONT face=3D"Courier =
New"=20
size=3D2><resourceRef =20
</FONT><BR> =20
<FONT face=3D"Courier New"=20
size=3D2>xlink:href=3D"<A =
href=3D"http://www.google.com?q=3Dstress+workplace"=20
target=3D_blank>http://www.google.com?q=3Dstress+workplace</A>"</FONT> =
<BR> =20
<FONT face=3D"Courier New"=20
size=3D2>xlink:show=3D"Stress search from google"></FONT>=20
<BR> <FONT face=3D"Courier =
New"=20
size=3D2></resourceRef></FONT> </P>
<P><FONT face=3DArial size=3D2>But the</FONT> <FONT face=3D"Times New =
Roman">XML=20
Topic Maps (XTM) 1.0 standard only supports type and href</FONT> <FONT =
face=3DArial size=3D2>:</FONT> </P>
<P><FONT face=3D"Courier New" size=3D2><!ATTLIST resourceRef=20
</FONT><BR> <FONT =
face=3D"Courier New"=20
size=3D2>id =
=20
ID =
#IMPLIED </FONT><BR> <FONT=20
face=3D"Courier New" size=3D2>xlink:type =
NMTOKEN=20
#FIXED 'simple'=20
</FONT><BR> <FONT =
face=3D"Courier New"=20
size=3D2>xlink:href CDATA =
#REQUIRED</FONT>=20
<BR><FONT face=3D"Courier New" size=3D2>></FONT> <BR><FONT=20
face=3D"Times New Roman">Any ideas?</FONT> </P><FONT =
size=3D3><BR><BR>Visit=20
http://www.bupa.com or call 0800 00 10 10 and find out what BUPA can =
do for=20
you.<BR><BR>BUPA, the health and care people<BR><BR><BR>BUPA House =
15-19=20
Bloomsbury Way London WC1A 2BA<BR><BR>Internet communications are not =
secure=20
and therefore BUPA does<BR>not accept legal responsibility for the =
contents of=20
this message. Any <BR>views or opinions presented are solely those of =
the=20
author and do <BR>not necessarily represent those of=20
BUPA.<BR></BLOCKQUOTE></FONT></BODY></HTML>
------=_NextPart_000_0360_01C4DBCB.1620AA20--