[topicmapmail] [ANN] Topic Map Explorer Version 1.0
Jason.Markos@empolis.com
Jason.Markos@empolis.com
Tue, 7 Sep 2004 14:12:20 +0200
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_01C494D3.EF3F5BAD
Content-Type: text/plain;
charset="iso-8859-1"
Hi
I watch this newsgroup as I am interested in the advancement of extended
meta-data technology, of which TopicMaps is one such example. It is of
particular interest to myself as I have spent some time with the R&D team at
empolis who have spent considerable time working in this arena - first with
x2x, it's xlink server, then with k42, it's 100% compliant TopicMap server
and, more recently, with it's knowledge management platform. In addition I
have spent some time on the XTM committee helping with marketing.
This mail seems to be at odds with itself. On the one had it discusses the
interest and validity in the idea of having a personal desktop application
whilst on the other hand, it criticises the applications lack of end user
support for TopicMap specific constructs such as roles, scope and typing.
In my limited experience of working with TopicMaps the real challenge has
been how to make it accessible and useable by average computer users - which
this particular application seems to be aimed at. (The documentation
provides an interpretation of TopicMaps making it useful and accessible.)
In which case, surely the question should be - does it help users in their
day to day life? It would appear that the application may not have specific
TopicMap constructs visible to the end user - but it certainly seems to
allow me to define topics, relationships, link them to content and to build
network based structures as opposed to linear/hierarchical structures - all
TopicMap principles. Without requiring me to be a TopicMap expert - which
many of you can confirm I am not!
If XTM is to become pervasive as a standard, it will need applications such
as TMExplorer that make it accessible. You only have to look at HyTime to
see what happens to standards that are inaccessible.
Jason
rick coope wrote:
>
> Semantic Web Technologies announce the release of Topic Map Explorer - the
> next generation of personal knowledge management software.
I have downloaded this application and tried it out for all of ten
minutes. I am disappointed to report the following -
1) This is not a production quality release, event though it is styled
"verson 1.0". I got numerous exceptions (which were at least
recoverable) and many anomalies, including a mislabled dialog component.
2) This is not a topic map application in any way, shape, or form. It
does not export or import any recognized topic map format. Instead it
exports rdf! But it does not import general rdf. Or rather, on the
simple rdf files I tried, it claimed success, but the display showed
nothing.
The designer appears not to understand the basics of topic maps. There
is no way to indicate the subject of a topic. There are no scopes.
There are only binary relations. The only display is a tree view.
There are no PSIs. I was unable to delete a relation I had created. I
could not find a way to change a relationship type once one had been
created. You are supposed to be able to designate the "type" of a
topic, but that didn't work. You can't relate property types to each other.
I was also able to (unintentionaly) create an loop between two topics I
tried to relate, so that the tree view display kept unfolding the same
two topics ad infinitum (if I had wanted to keep expanding the tree).
Of course, the fact that there was no documentation probably didn't
help. Still, it is *inexcusable* to call this a "topic map explorer"
and not have a *single* characteristic that disinguishes topic maps and
makes them rich and valuable.
Setting aside the issue of whether this application has anything to do
with topic maps per se, could it be useful in and of itself? Setting
aside current bugs and questionable interface features - which are
numerous - in my view, not with just a tree view, and not with the
apparent limitations of the internal model. I say "apparent
limitations", because it is possible that the internal model is richer
than the app exposes (maybe there can be a hierarachy of association
types, for examples), but one could not know by the current interface.
What really bothers me is that this app could give topic maps a bad
name, or at the least mislead people into thinking that topic maps are
very limited and don't do anything that hasn't been seen in many apps
before.
I almost feel like I should apologize to the developer of this product
for my strong words, but I mean them all. Whoever you are, this product
would have to go a long way before I would even consider trying another
evaluation copy. I don't even feel like encouraging you to try to
modify and extend it, because the current starting point is so weak.
I hope I am wrong about my last statement, because I would really like
to see a modestly priced, easy to use topic map application.
Regretfully yours
Tom P
--
Thomas B. Passin
Jason Markos
Director
--------------------------------------------------------
empolis UK
part of arvato: a Bertelsmann company
Unit B
The Dorcan Complex,
Faraday Road,
Swindon,
Wiltshire,
SN3 5HQ
<http://www.empolis.co.uk/> http://www.empolis.co.uk
E. <mailto:jsm@empolis.co.uk> jason.markos@empolis.com
T. +44 (0) 1793 - 485465
F. +44 (0) 1793 - 485451
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorised. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in reliance
on it, is prohibited and may be unlawful. If you have received this
communication in error please return it to the sender, then delete and
destroy any copies of it.
------_=_NextPart_001_01C494D3.EF3F5BAD
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 =
6.5.7232.7">
<TITLE>Re: [topicmapmail] [ANN] Topic Map Explorer Version 1.0 =
</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial">Hi</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Arial">I =
watch this newsgroup as I am interested in the advancement of extended =
meta-data technology, of which TopicMaps is one such example. It =
is of particular interest to myself as I have spent some time with the =
R&D team at empolis who have spent considerable time working in =
this arena - first with x2x, it's xlink server, then with k42, it's =
100% compliant TopicMap server and, more recently, with it's knowledge =
management platform. In addition I have spent some time on the =
XTM committee helping with marketing.</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial">This</FONT></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Arial"> mail seems to be at odds =
with itself. On the one had</FONT></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"> <FONT SIZE=3D2 =
FACE=3D"Arial">it</FONT></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"en-gb"> <FONT SIZE=3D2 =
FACE=3D"Arial">discuss</FONT></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Arial">es</FONT></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial"> the interest and validity in the idea of having a =
personal desktop application whilst on the other =
hand,</FONT></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"> =
<FONT SIZE=3D2 FACE=3D"Arial">it</FONT></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"> <FONT SIZE=3D2 =
FACE=3D"Arial">criticise</FONT></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Arial">s</FONT></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial"> the applications lack of end user support for TopicMap =
specific constructs such as</FONT></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"> <FONT SIZE=3D2 =
FACE=3D"Arial">roles</FONT></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Arial">, scope and typing. =
In my limited experience of working with TopicMaps the real challenge =
has been how to make it accessible and useable by average computer =
users - which this particular application seems to be aimed at. =
(The documentation provides an interpretation of TopicMaps making it =
useful and accessible.) In which case, surely the question should =
be - does it help users in their day to day life? It would appear =
that the application may not have specific TopicMap constructs visible =
to the end user - but it certainly seems to allow me to define topics, =
re</FONT></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"><FONT =
SIZE=3D2 FACE=3D"Arial">l</FONT></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial">ationships, link them to content and to build =
ne</FONT></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"><FONT =
SIZE=3D2 FACE=3D"Arial">t</FONT></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial">work based structures as opposed to linear/hierarchical =
structures</FONT></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Arial"> – all TopicMap =
principles</FONT></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Arial">. Without requiring =
me to be a TopicMap expert - which many of you can confirm I am =
not!</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Arial">If =
XTM is to become pervasive as a standard, it will need applications =
such as TMExplorer</FONT></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Arial"> that make it =
accessible</FONT></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Arial">.</FONT></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial"> You only have to look at HyTime to see what =
happens to standards that are</FONT></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"> <FONT SIZE=3D2 =
FACE=3D"Arial">in</FONT></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial">accessible.</FONT></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial">Jason</FONT></SPAN></P>
<BR>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">rick coope wrote:</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">></FONT></SPAN><SPAN LANG=3D"en-gb"><I><FONT SIZE=3D2 =
FACE=3D"Courier New"> </FONT></I></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">></FONT></SPAN><SPAN LANG=3D"en-gb"><I><FONT SIZE=3D2 =
FACE=3D"Courier New"> Semantic Web Technologies announce the release of =
Topic Map Explorer - the</FONT></I></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">></FONT></SPAN><SPAN LANG=3D"en-gb"><I><FONT SIZE=3D2 =
FACE=3D"Courier New"> next generation of personal knowledge management =
software.</FONT></I></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">I have downloaded this application and tried it out for all of ten =
</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">minutes. I am disappointed to report the following =
-</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">1) This is not a production quality release, event though it is =
styled </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">"verson 1.0". I got numerous exceptions (which =
were at least </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">recoverable) and many anomalies, including a mislabled dialog =
component.</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">2) This is not a topic map application in any way, shape, or =
form. It </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">does not export or import any recognized topic map format. =
Instead it </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">exports rdf! But it does not import general rdf. Or =
rather, on the </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">simple rdf files I tried, it claimed success, but the =
display showed </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">nothing.</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">The designer appears not to understand the basics of topic =
maps. There </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">is no way to indicate the subject of a topic. There are no =
scopes. </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">There are only binary relations. The only display is a tree =
view. </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">There are no PSIs. I was unable to delete a relation I had =
created. I </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">could not find a way to change a relationship type once one had =
been </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">created. You are supposed to be able to designate the =
"type" of a </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">topic, but that didn't work. You can't relate property types =
to each other.</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">I was also able to (unintentionaly) create an loop between two =
topics I </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">tried to relate, so that the tree view display kept unfolding the =
same </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">two topics ad infinitum (if I had wanted to keep expanding the =
tree).</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">Of course, the fact that there was no documentation probably =
didn't </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">help. Still, it is *inexcusable* to call this a "topic =
map explorer" </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">and not have a *single* characteristic that disinguishes topic =
maps and </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">makes them rich and valuable.</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">Setting aside the issue of whether this application has anything =
to do </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">with topic maps per se, could it be useful in and of itself? =
Setting </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">aside current bugs and questionable interface features - which are =
</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">numerous - in my view, not with just a tree view, and not with the =
</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">apparent limitations of the internal model. I say =
"apparent </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">limitations", because it is possible that the internal model =
is richer </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">than the app exposes (maybe there can be a hierarachy of =
association </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">types, for examples), but one could not know by the current =
interface.</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">What really bothers me is that this app could give topic maps a =
bad </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">name, or at the least mislead people into thinking that topic maps =
are </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">very limited and don't do anything that hasn't been seen in many =
apps </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">before.</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">I almost feel like I should apologize to the developer of this =
product </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">for my strong words, but I mean them all. Whoever you are, =
this product </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">would have to go a long way before I would even consider trying =
another </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">evaluation copy. I don't even feel like encouraging you to =
try to </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">modify and extend it, because the current starting point is so =
weak.</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">I hope I am wrong about my last statement, because I would really =
like </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">to see a modestly priced, easy to use topic map =
application.</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">Regretfully yours</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">Tom P</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">-- </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Courier =
New">Thomas B. Passin</FONT></SPAN></P>
<BR>
<BR>
<P ALIGN=3DLEFT><SPAN LANG=3D"de-de"></SPAN><A NAME=3D""><SPAN =
LANG=3D"de-de"></SPAN></A></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"de-de"><FONT =
FACE=3D"Tahoma"> </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"de-de"><FONT COLOR=3D"#292526" SIZE=3D2 =
FACE=3D"Tahoma">Jason Markos</FONT></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"de-de"></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"de-de"><FONT COLOR=3D"#292526" SIZE=3D2 =
FACE=3D"Tahoma">Director</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"de-de"><FONT COLOR=3D"#292526" SIZE=3D2 =
FACE=3D"Tahoma">--------------------------------------------------------=
</FONT></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"de-de"></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"de-de"><FONT COLOR=3D"#292526" SIZE=3D2 =
FACE=3D"Tahoma">empolis UK</FONT></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"de-de"></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"de-de"><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Tahoma">part of arvato: a Bertelsmann company</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"de-de"><FONT COLOR=3D"#292526" SIZE=3D2 =
FACE=3D"Tahoma">Unit B</FONT></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"de-de"></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"de-de"><FONT COLOR=3D"#292526" SIZE=3D2 =
FACE=3D"Tahoma">The Dorcan Complex,</FONT></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"de-de"></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"de-de"><FONT COLOR=3D"#292526" SIZE=3D2 =
FACE=3D"Tahoma">Faraday Road,</FONT></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"de-de"></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"de-de"><FONT COLOR=3D"#292526" SIZE=3D2 =
FACE=3D"Tahoma">Swindon,</FONT></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"de-de"></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"de-de"><FONT COLOR=3D"#292526" SIZE=3D2 =
FACE=3D"Tahoma">Wiltshire,</FONT></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"de-de"></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"de-de"><FONT COLOR=3D"#292526" SIZE=3D2 =
FACE=3D"Tahoma">SN3 5HQ</FONT></SPAN><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"de-de"></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"></SPAN><A =
HREF=3D"http://www.empolis.co.uk/"><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"en-gb"><U></U></SPAN><U><SPAN LANG=3D"de-de"><FONT =
COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Tahoma">http://www.empolis.co.uk</FONT></SPAN></U><SPAN =
LANG=3D"en-gb"></SPAN></A><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"de-de"></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"de-de"><FONT SIZE=3D2 =
FACE=3D"Tahoma">E.</FONT></SPAN><SPAN LANG=3D"en-gb"> </SPAN><A =
HREF=3D"mailto:jsm@empolis.co.uk"><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"en-gb"><U></U></SPAN><U><SPAN LANG=3D"de-de"><FONT =
COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Tahoma">jason.markos@empolis.com</FONT></SPAN></U><SPAN =
LANG=3D"en-gb"></SPAN></A><SPAN LANG=3D"en-gb"></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"de-de"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"de-de"><FONT COLOR=3D"#292526" SIZE=3D2 =
FACE=3D"Tahoma">T. +44 (0) 1793 - 485465</FONT></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"de-de"></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"de-de"><FONT COLOR=3D"#292526" SIZE=3D2 =
FACE=3D"Tahoma">F. +44 (0) 1793 - 485451</FONT></SPAN><SPAN =
LANG=3D"en-gb"></SPAN><SPAN LANG=3D"de-de"></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"de-de"><FONT SIZE=3D2 FACE=3D"Tahoma">The =
information in this email is confidential and may be legally =
privileged. It is intended solely for the addressee. Access to this =
email by anyone else is unauthorised. If you are not the intended =
recipient, any disclosure, copying, distribution or any action taken or =
omitted to be taken in reliance on it, is prohibited and may be =
unlawful. If you have received this communication in error please =
return it to the sender, then delete and destroy any copies of =
it.</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"de-de"><FONT =
FACE=3D"Tahoma"> </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"de-de"><FONT =
FACE=3D"Tahoma"> </FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-gb"></SPAN></P>
</BODY>
</HTML>
------_=_NextPart_001_01C494D3.EF3F5BAD--