<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Quintin,<br>
<br>
<div class="moz-cite-prefix">On 08/19/2012 07:10 AM, Quintin Siebers
wrote:<br>
</div>
<blockquote cite="mid:AD6FE4A3-1376-4AEB-A4EE-F4E8864D2006@mssm.nl"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div>Hey,</div>
<div><br>
</div>
<div>We've been working on such a system for a few years now, and
our current version is open to have a look at:</div>
<div><br>
</div>
<div><a moz-do-not-send="true"
href="http://en.mssm.nl/software/kamala-in-the-cloud/">http://en.mssm.nl/software/kamala-in-the-cloud/</a></div>
<br>
</blockquote>
<br>
Good point but Kamala requires (as any topic map application does)
that you establish what subjects you want to talk about, their
identifies, relationships, etc. Having said that, you can fill it
with whatever content you like. <br>
<br>
My objection to Sebastian's needs/features is their universal
nature.<br>
<br>
If I were writing a topic map for business expenses, it would be
very unlikely to include the rules for receipts written in cuneiform
(the earliest business document is a receipt for beer at an inn).
Not that topic maps can't do that, but most clients are unlikely to
be interested. For that matter, of the thousands of natural
languages in existence, most clients are going to be interested in
only one (1). Topic maps can do more but again, probably not a
requirement. <br>
<br>
You can see where this is going. <br>
<br>
I think topic maps shine brightest meeting the semantic requirements
of actual customers. <br>
<br>
That someone, somewhere, off the Net most likely, is not best served
by my topic map is quite likely. <br>
<br>
But, I am not arrogant enough to presume to act in their best
interest, never having asked what they want, much less their
permission. <br>
<br>
Is the "digital divide"
(<a class="moz-txt-link-freetext" href="http://en.wikipedia.org/wiki/Digital_divide">http://en.wikipedia.org/wiki/Digital_divide</a>) the new "white man's
burden? (<a class="moz-txt-link-freetext" href="http://en.wikipedia.org/wiki/White_Man%27s_Burden">http://en.wikipedia.org/wiki/White_Man%27s_Burden</a>)" <br>
<br>
Hope you are having a great weekend!<br>
<br>
Patrick<br>
<br>
<br>
<blockquote cite="mid:AD6FE4A3-1376-4AEB-A4EE-F4E8864D2006@mssm.nl"
type="cite">
<div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate;
border-spacing: 0px; "><span class="Apple-style-span"
style="border-collapse: separate; color: rgb(0, 0, 0);
font-family: Calibri; font-size: 13px; font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: 2; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px;
-webkit-border-vertical-spacing: 0px;
-webkit-text-decorations-in-effect: none;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width:
0px; ">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space; ">
<div>Quintin Siebers</div>
<div><br>
</div>
<div>--</div>
<div><a moz-do-not-send="true"
href="mailto:q.siebers@mssm.nl">q.siebers@mssm.nl</a></div>
<div>(+31) (0)6 - 11 06 16 27</div>
<div><span class="Apple-style-span" style="font-size:
medium; "><br>
</span></div>
</div>
</span>
<div><br>
</div>
<div>Morpheus Kennistechnologie BV<br>
</div>
<URL: <a moz-do-not-send="true" href="http://www.mssm.nl">http://www.mssm.nl</a> ><br>
postbus 69<br>
3500 CD Utrecht<br>
KVK 30 26 04 30</span>
</div>
<br>
<div>
<div>On 19 aug. 2012, at 13:03, Alexander Johannesen <<a
moz-do-not-send="true"
href="mailto:alexander.johannesen@gmail.com">alexander.johannesen@gmail.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">Hola,<br>
<br>
On Sun, Aug 19, 2012 at 8:52 PM, adasal <<a
moz-do-not-send="true" href="mailto:adam.saltiel@gmail.com">adam.saltiel@gmail.com</a>>
wrote:<br>
<blockquote type="cite">Is what you are proposing really
possible from the ground up? I wonder if<br>
even getting an architecture is possible from the ground up,
i.e. without<br>
starting with real world compromises dictated by the job in
hand.<br>
</blockquote>
<br>
Not sure if what's proposed is possible from the ground up,
but I know<br>
it's certainly possible to create an ontology-based complete
system,<br>
however I doubt "from the ground up" has been defined enough
at this<br>
point. I've worked on creating full-stack application and
systems<br>
delivery framework based on ontologies / Topic Maps, both in
terms of<br>
integration but also as a development tool, and as a way to
infer<br>
capabilities of services based on their entity / resource
rather than<br>
clumsy API's.<br>
<br>
I'm fairly confident that it's the way of the future, but as
you<br>
probably allude to as well, it's still a bit way off, mostly
because<br>
whomever comes up with it first or already doing it, are doing
it in<br>
solitary, much like the TM community watching the spectacle of
RDF<br>
from the side-lines.<br>
<br>
<br>
Regards,<br>
<br>
Alex<br>
-- <br>
Project Wrangler, SOA, Information Alchemist, UX, RESTafarian,
Topic Maps<br>
--- <a moz-do-not-send="true" href="http://shelter.nu/blog/">http://shelter.nu/blog/</a>
----------------------------------------------<br>
------------------ <a moz-do-not-send="true"
href="http://www.google.com/profiles/alexander.johannesen">http://www.google.com/profiles/alexander.johannesen</a>
---<br>
_______________________________________________<br>
topicmapmail mailing list<br>
<a moz-do-not-send="true"
href="mailto:topicmapmail@infoloom.com">topicmapmail@infoloom.com</a><br>
<a class="moz-txt-link-freetext" href="http://www.infoloom.com/mailman/listinfo/topicmapmail">http://www.infoloom.com/mailman/listinfo/topicmapmail</a><br>
</blockquote>
</div>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
topicmapmail mailing list
<a class="moz-txt-link-abbreviated" href="mailto:topicmapmail@infoloom.com">topicmapmail@infoloom.com</a>
<a class="moz-txt-link-freetext" href="http://www.infoloom.com/mailman/listinfo/topicmapmail">http://www.infoloom.com/mailman/listinfo/topicmapmail</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Patrick Durusau
<a class="moz-txt-link-abbreviated" href="mailto:patrick@durusau.net">patrick@durusau.net</a>
Former Chair, V1 - US TAG to JTC 1/SC 34
Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)
Another Word For It (blog): <a class="moz-txt-link-freetext" href="http://tm.durusau.net">http://tm.durusau.net</a>
Homepage: <a class="moz-txt-link-freetext" href="http://www.durusau.net">http://www.durusau.net</a>
Twitter: patrickDurusau </pre>
</body>
</html>