<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
> 4. conversion of the wiki into OWL, so that the rules and
relations of the OSM are documented formally.<br>
see also<br>
<a class="moz-txt-link-freetext" href="http://wiki.openstreetmap.org/wiki/Machine-readable_Map_Feature_list/OWL_Semantic_Wiki_and_more">http://wiki.openstreetmap.org/wiki/Machine-readable_Map_Feature_list/OWL_Semantic_Wiki_and_more</a><br>
<a class="moz-txt-link-freetext" href="http://wiki.openstreetmap.org/wiki/Machine-readable_Map_Feature_list">http://wiki.openstreetmap.org/wiki/Machine-readable_Map_Feature_list</a><br>
an attempt to maintain and harvest a machine-readable list of map
features on and from the OSM wiki using <br>
OWL, RDF, SemanticMediaWiki.<br>
<br>
Note that this is more than a year old, and no progress has been made.
JOSMs tageditor plugin now adopted<br>
a more pragmatic approach. I manually maintain a list of
machine-readable map features (yet another list, in <br>
addition to JOSM presets, and other lists).<br>
<br>
> 4. conversion of the wiki into OWL, so that the rules and
relations of the OSM are documented formally.<br>
That's the key issue. And the most difficult part. SemanticMediaWiki
could help here, because people working<br>
with the wiki and its templates today would still work with the very
same wiki and the more or less same<br>
templates. We had a prototype up and running a year ago. Emphasis on
"prototype", though. Unfortunately, it never <br>
made into the production wiki (lack of hardware ressources at the time,
also lack of interest in general).<br>
<br>
"so that the rules and relations of the OSM are documented formally"
describes the major obstacle here: a significant<br>
share (if not the majority) of OSM contributors doesn't see value in
raising the level of formality<br>
<br>
Regards<br>
Karl <br>
<br>
Am 11.03.2010 23:39, schrieb <a class="moz-txt-link-abbreviated" href="mailto:jamesmikedupont@googlemail.com:">jamesmikedupont@googlemail.com:</a>
<blockquote
cite="mid:ee9cc731003111439rd9d79cbr8e730f4179971011@mail.gmail.com"
type="cite">Description :<br>
<br>
Integration of the java swoop ontology editor into JOSM. A JOSM
ontology plugin.<br>
<br>
Work :<br>
<br>
1. create a live mapping from OSM into RDF , so that the swoop can
access the data in OSM without conversion.<br>
2. be able to have the changes in the rdf be reflected back into the
OSM.<br>
4. conversion of the wiki into OWL, so that the rules and relations of
the OSM are documented formally.<br>
5. running of the pellet inference engine and all the other reasoning
tools from swoop to infer new facts and validate the data.<br>
6. encoding of the rules of the JOSM validator into OWL rules, maybe we
will have to include new derived geometric things like if two ways
intersect and also ways to only process data in a certain radius.<br>
<br>
mike<br>
<br>
<div class="gmail_quote">On Thu, Mar 11, 2010 at 11:16 PM, Graham
Jones <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:grahamjones139@googlemail.com">grahamjones139@googlemail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br>
I agree that improving documentation would be a really useful
contribution to OSM, but Google are quite explicit that this is outside
of the scope of GSoC (<a moz-do-not-send="true"
href="http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#doc_proposals"
target="_blank">http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#doc_proposals</a>).<br>
<br>
A project along the lines of 'context sensitive help in OSM editors'
could be a possibility though. I have never worked on one of the main
editors, so I have no idea how hard this would be from that point of
view. The Artifical Intelligence aspects are quite difficult in
themselves though - it would have to try to guess what you would like
to do from what you have just done - quite a challenge, but please add
it to the list if you can manage to describe it!<br>
<br>
Regards<br>
<font color="#888888"><br>
<br>
Graham.</font>
<div>
<div class="h5"><br>
<br>
<div class="gmail_quote">On 11 March 2010 10:59, <a
moz-do-not-send="true" href="mailto:jamesmikedupont@googlemail.com"
target="_blank">jamesmikedupont@googlemail.com</a> <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:jamesmikedupont@googlemail.com"
target="_blank">jamesmikedupont@googlemail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">lets
put it in a different perspective :<br>
<br>
Make the documentation as part of the program!<br>
<br>
I would like to see for example a help system that is integrated to the
wiki,<br>
Click on a tag, have it pull up the wiki entry, be able to add new
unknown tags or rename them.<br>
We could even have an OWL Ontology created with a reasoning engine to
specify rules for tagging.<br>
<br>
Really, the software should be so good that you dont need docs or
videos. <br>
<br>
mike
<div>
<div><br>
<br>
<div class="gmail_quote">On Thu, Mar 11, 2010 at 11:49 AM,
Peteris Krisjanis <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:pecisk@gmail.com" target="_blank">pecisk@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>> GSoc<br>
> student pool is a very talented one - it would be good to use them
for more<br>
> critical things. Of course, OSM unlike other projects is basically
a<br>
> collection of tools maintained by various people, so difficult to
achieve a<br>
> consensus.<br>
>><br>
<br>
</div>
Having one place of knowhow of mapping is quite critical for project<br>
like OSM. And believe me, creating good documentation requires quite a<br>
skill and isn't easiest job in IT world as we would like to see.<br>
<br>
Cheers,<br>
Peter.<br>
<div>
<div><br>
_______________________________________________<br>
talk mailing list<br>
<a moz-do-not-send="true" href="mailto:talk@openstreetmap.org"
target="_blank">talk@openstreetmap.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openstreetmap.org/listinfo/talk" target="_blank">http://lists.openstreetmap.org/listinfo/talk</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
_______________________________________________<br>
talk mailing list<br>
<a moz-do-not-send="true" href="mailto:talk@openstreetmap.org"
target="_blank">talk@openstreetmap.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openstreetmap.org/listinfo/talk" target="_blank">http://lists.openstreetmap.org/listinfo/talk</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
</div>
</div>
<div>
<div class="h5">-- <br>
Dr. Graham Jones<br>
Hartlepool, UK<br>
email: <a moz-do-not-send="true" href="mailto:grahamjones139@gmail.com"
target="_blank">grahamjones139@gmail.com</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
talk mailing list
<a class="moz-txt-link-abbreviated" href="mailto:talk@openstreetmap.org">talk@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstreetmap.org/listinfo/talk">http://lists.openstreetmap.org/listinfo/talk</a>
</pre>
</blockquote>
</body>
</html>