Sven and Ontologists --
One approach to closing the gap between medical* professionals and ontologists is to provide a Wiki for executable English content.
Our approach to this is in the system that is online at the site below.
A hopefully relevant example is
www.reengineeringllc.com/demo_agents/MedMine2.agent
You can view, run and change that example, and others, by pointing a browser to the site.
Apologies to folks who have seen this before, and thanks for comments.
-- Adrian
* and specialists in other professions
Internet Business Logic
A Wiki and SOA Endpoint for Executable Open Vocabulary English over SQL
Online at www.reengineeringllc.com Shared use is free
Adrian Walker
Reengineering
On Tue, Apr 22, 2008 at 8:47 AM, Sven Van Poucke < svanpoucke@xxxxxxxxxxxxx> wrote:
Dear Peter,
I thank you for your honest reply. I appreciate your efforts and
interventions at ontolog (while driving to the hospital I am working as
anaesthetist and listening to the previous podcasts). From a
not-even-novice-in-ontology scientific point of view, the need for
ontologies to increase efficiency and efficacy in data management and
communication is clear. However, the ontolog(y) community should be aware
that tools, pathways and protocols are urgently needed to bridge the gap
between the knowledge available in communities of practice and the
preparation of this knowledge for ontology engineers. Practically this could
be translated in tools where consensus could be reached on definitions and
words used during professional life. Use a wiki or something similar seems
not a good answer considering the realistic lack of computer and ict
knowledge by most professionals in their highly professional environment
(such as nurses on intensive care). I really hope some constructive
solutions can be developed for this 'neglected problem'.
Cheers
SvenVanPoucke
Co-ordinator Woundontology Consortium
-----Oorspronkelijk bericht-----
Van: peter.yim@xxxxxxxxx [mailto:peter.yim@xxxxxxxxx] Namens Peter Yim
Verzonden: dinsdag 22 april 2008 14:01
Aan: Sven Van Poucke
Onderwerp: Re: Invitation to connect on LinkedIn
Thank you for the invitation, Sven.
Please allow me to take a rain check. For fear of not being able to be
adequately responsive, I have, up to this point, shied away from
getting connected into any social networks (other than being
subscribed to communities that I have already been involved in.)
Your invitation is valued and appreciated nonetheless. Do feel free to
contact me via email any time, though.
Thanks & regards. =ppy
--
On Tue, Apr 22, 2008 at 12:30 AM, Sven Van Poucke
<svanpoucke@xxxxxxxxxxxxx> wrote:
>
>
>
> LinkedIn
>
>
> Peter,
>
> I'd like to add you to my professional network on LinkedIn.
>
> -Sven
>
> PS: Here is the link:
> https://www.linkedin.com/e/isd/252896708/WKv8iljZ/
>
> It is free to join and takes less than 60 seconds to sign up.
>
> This is an exclusive invitation from Sven Van Poucke to Peter Yim. For
> security reasons, please do not forward this invitation.
>
> (c) 2008, LinkedIn Corporation
No virus found in this incoming message.
Checked by AVG.
Version: 7.5.524 / Virus Database: 269.23.3/1390 - Release Date: 21-4-2008
16:23
No virus found in this outgoing message.
Checked by AVG.
Version: 7.5.524 / Virus Database: 269.23.3/1390 - Release Date: 21-4-2008
16:23
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx (01)
|