[topicmapmail] Occurrence resource naming
ROBERTS, Alastair
ROBERALA@BUPA.com
Tue, 7 Dec 2004 09:55:02 -0000
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C4DC42.D1F8FE88
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Thanks - that makes a lot more sense now - somehow I managed to miss that
paragraph from the omnigator guide. Doh
-----Original Message-----
From: Steve Pepper [mailto:steve@ontopia.net]=20
Sent: 06 December 2004 18:58
To: TopicMapMail
Cc: Knud M=F6ller; ROBERTS, Alastair
Subject: RE: [topicmapmail] Occurrence resource naming
Hi Knud and Alastair,
* Knud M=F6ller:
| I havn't done much topic mapping lately,
Shame on you ;-)
| but can you not reify the
| occurrence and tell your application to display that topic's basename=20
| instead? Something along the following lines:
|=20
| <topic id=3D"reifiedOccurrence">
| <subjectIdentity>
| <resourceRef xlink:href=3D"#googleStressSearch"/>
| </subjectIdentity>
| <baseName>
| <baseNameString>'Stress' from Google</baseNameString>
| </baseName>
| </topic>
This is an alternative to the method I suggested, but the semantics are
subtly different.
When you reify an occurrence you are creating a topic that represents the
*relationship* between the topic and the resource, not a topic that
represents the resource itself.
There are some situations where this makes sense, but in my opinion,
Alastair's use case is not one of them. This is because the name of a
resource does not usually change depending on what topic it is an occurrence
of.
In other words, the name is a property of the resource itself, not of the
relationship between the resource and the topic that it is "about".
| As far as I can see the XTM specification doesn't allow to specify
| basenames for occurences directly.
That is correct. We could have introduced a syntactic shortcut for this, but
decided against it on the grounds that "forcing" users to create an explicit
topic would help ensure that people understood what they were doing.
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)
=20
Visit http://www.bupa.com or call 0800 00 10 10 and find out what BUPA can =
do for you.
=20
BUPA, the health and care people
=20
=20
BUPA House 15-19 Bloomsbury Way London WC1A 2BA
=20
Internet communications are not secure and therefore BUPA does
not accept legal responsibility for the contents of this message. Any=20
views or opinions presented are solely those of the author and do=20
not necessarily represent those of BUPA.
------_=_NextPart_001_01C4DC42.D1F8FE88
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-8859-=
1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2658.2">
<TITLE>RE: [topicmapmail] Occurrence resource naming</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Thanks - that makes a lot more sense now - somehow I mana=
ged to miss that paragraph from the omnigator guide. Doh</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Steve Pepper [<A HREF=3D"mailto:steve@ontopia.net"=
>mailto:steve@ontopia.net</A>] </FONT>
<BR><FONT SIZE=3D2>Sent: 06 December 2004 18:58</FONT>
<BR><FONT SIZE=3D2>To: TopicMapMail</FONT>
<BR><FONT SIZE=3D2>Cc: Knud M=F6ller; ROBERTS, Alastair</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [topicmapmail] Occurrence resource naming</=
FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Hi Knud and Alastair,</FONT>
</P>
<P><FONT SIZE=3D2>* Knud M=F6ller:</FONT>
</P>
<P><FONT SIZE=3D2>| I havn't done much topic mapping lately,</FONT>
</P>
<P><FONT SIZE=3D2>Shame on you ;-)</FONT>
</P>
<P><FONT SIZE=3D2>| but can you not reify the</FONT>
<BR><FONT SIZE=3D2>| occurrence and tell your application to display that t=
opic's basename </FONT>
<BR><FONT SIZE=3D2>| instead? Something along the following lines:</FONT>
<BR><FONT SIZE=3D2>| </FONT>
<BR><FONT SIZE=3D2>| <topic id=3D"reifiedOccurrence"></FONT>
<BR><FONT SIZE=3D2>| <subjectIdentity>=
</FONT>
<BR><FONT SIZE=3D2>|  =
; <resourceRef xlink:href=3D"#googleStressSearch&=
quot;/></FONT>
<BR><FONT SIZE=3D2>| </subjectIdentity>=
;</FONT>
<BR><FONT SIZE=3D2>| <baseName></FONT>
<BR><FONT SIZE=3D2>|  =
; <baseNameString>'Stress' from Google</baseName=
String></FONT>
<BR><FONT SIZE=3D2>| </baseName></FONT>
<BR><FONT SIZE=3D2>| </topic></FONT>
</P>
<P><FONT SIZE=3D2>This is an alternative to the method I suggested, but the=
semantics are subtly different.</FONT>
</P>
<P><FONT SIZE=3D2>When you reify an occurrence you are creating a topic tha=
t represents the *relationship* between the topic and the resource, not a t=
opic that represents the resource itself.</FONT></P>
<P><FONT SIZE=3D2>There are some situations where this makes sense, but in =
my opinion, Alastair's use case is not one of them. This is because the nam=
e of a resource does not usually change depending on what topic it is an oc=
currence of.</FONT></P>
<P><FONT SIZE=3D2>In other words, the name is a property of the resource it=
self, not of the relationship between the resource and the topic that it is=
"about".</FONT></P>
<P><FONT SIZE=3D2>| As far as I can see the XTM specification doesn't allow=
to specify</FONT>
<BR><FONT SIZE=3D2>| basenames for occurences directly.</FONT>
</P>
<P><FONT SIZE=3D2>That is correct. We could have introduced a syntactic sho=
rtcut for this, but decided against it on the grounds that "forcing&qu=
ot; users to create an explicit topic would help ensure that people underst=
ood what they were doing.</FONT></P>
<P><FONT SIZE=3D2>Steve</FONT>
</P>
<P><FONT SIZE=3D2>--</FONT>
<BR><FONT SIZE=3D2>Steve Pepper <pepper@ontopia.net></FONT>
<BR><FONT SIZE=3D2>Chief Strategy Officer, Ontopia</FONT>
<BR><FONT SIZE=3D2>Convenor, ISO/IEC JTC 1/SC 34/WG 3</FONT>
<BR><FONT SIZE=3D2>Editor, XTM (XML Topic Maps 1.0)</FONT>
<BR><FONT SIZE=3D2> </FONT>
</P>
<FONT SIZE=3D3><BR>
<BR>
Visit http://www.bupa.com or call 0800 00 10 10 and find out what BUPA can =
do for you.<BR>
<BR>
BUPA, the health and care people<BR>
<BR>
<BR>
BUPA House 15-19 Bloomsbury Way London WC1A 2BA<BR>
<BR>
Internet communications are not secure and therefore BUPA does<BR>
not accept legal responsibility for the contents of this message. Any <BR>
views or opinions presented are solely those of the author and do <BR>
not necessarily represent those of BUPA.<BR>
</FONT>
</BODY>
</HTML>
------_=_NextPart_001_01C4DC42.D1F8FE88--