Hi,
Jens Lehmann suggested to move the ontology editing to webProtege [1].
It will save a lot of effort trying to support more owl axioms (defining
new wiki syntax, parsing it properly etc.)
This solves many problems but creates a few more, like integration with the
core module and syncing with the mappings definitions (server module).
However, this has some good potential.
Taking this a little further we could also use web protege for the mappings
DB. I haven't looked at it in too detail but we can define custom editing
forms [2] which also solves the mappings web editor problem.
The plus to that is that we have the mappings directly in RDF and if we
publish the server statistics in rdf too, we can have many cool
visualizations & reports through SPARQL.
(This also creates some syncing problems with Live but we can probably
overcome them with some effort)
WDYT?
[1] http://protegewiki.stanford.edu/wiki/WebProtege
[2] http://protegewiki.stanford.edu/wiki/WebProtegeLayoutConfig
--
Dimitris Kontokostas
Department of Computer Science, University of Leipzig
Research Group: http://aksw.org
Homepage:http://aksw.org/DimitrisKontokostas
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Dbpedia-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dbpedia-developers
