Hi Ismael,
On 27.06.2017 14:13, Isma Rodríguez wrote:
Dear Sebastian,
thank you very much. You can find the Github repository on
https://github.com/dbpedia/mappings-ui
<https://github.com/dbpedia/mappings-ui>
Currently, all the goals of the first deliverable have been reached.
The first deliverable consisted of adapting the Aqua Framework to the
part of the project requirements related to user management,
permissions, groups, and editable help pages. In addition, a
continuous integration pipeline with Travis and Heroku has been created.
Now that I feel more confident with DBpedia and the needed programming
tools, we are looking into how we can implement the ontology and
mappings edition.
Regarding the ontology edition, we have checked multiple options and
the best one seems to be to connect the new UI with an instance of
WebProtege, as it is a very complete ontology edition tool. One of its
features is that it keeps a change log of the ontology edits and has
history functionalities.
Of course the idea is that the ontology is moved outside. Although
WebProtege works with the ontology in an internal database, we were
thinking about automatically pushing the ontology to a Github
repository whenever a change is made. This would enable to do any type
of check and integration system with a hook.
I guess the choice here will be made by the lack of alternatives. I
think, Google's GWT is fine for frontend development, however, the great
drawback is that all the javascript and web service calls are compiled
into a very difficult API, so doing anything except fronted might be
difficult, e.g. I am not sure whether webprotege provides a REST web
service for Ontology Export. Otherwise you would need to go deep into
the MongoDB? in the backend. While you can write a webprotege graphical
extension, I am not sure, you can do SHACL/SPARQL with OWLAPI which is
in the webprotege backend.
I recently discovered Dart:
https://www.dartlang.org/faq#q-why-isnt-dart-more-like-haskell--smalltalk--python--scala--other-language
and http://www.dockspawn.com/#
But of course it is out of scope to start from scratch when developing a
graphical OWL editor.
If necessary, we can of course host an own instance of webprotege on a
DBepdia server.
I will ask around though for alternatives. There is also
http://aksw.org/Projects/Xturtle.html which has syntax validation and
vocab autocompletion, if you like editing ontologies as turtle in github.
Did you look for other OWL editors yet?
In regards with RDFUnit and SHACL, I will comment it with my mentors
on our Skype call on Thursday. However, if we move the ontology to a
Github repository, it would be much easier to do any type of checks.
For editing the mappings, we have still to figure out how to do it, we
were considering integrating RML Editor but still requires thinking
and discussion.
If you have any suggestions or you notice that something would be
better in any other way, please feel free to comment. We are in a very
active discussion to determine the best way to create the UI, so any
idea is very welcomed.
More ideas for extensions, e.g. we can also keep mappings to other
ontologies/datasets later and use RML for RDF2RDF.
Cheers,
Sebastian
If you have any question, please ask me or my mentors.
Glad to work with DBpedia.
Best regards,
Ismael Rodríguez.
On 27 Jun 2017 12:28 pm, "Sebastian Hellmann"
<hellm...@informatik.uni-leipzig.de
<mailto:hellm...@informatik.uni-leipzig.de>> wrote:
Hi Ismael, all,
we were brainstorming for a while now and your Google Summer of
Code project looks promising: http://mappings-ui.herokuapp.com/
<http://mappings-ui.herokuapp.com/>
Overall, we really need to move away from the mappings wiki. I was
wondering what state your project is in at the moment. Is there a
Github repository?
Are you planning on integrating RDFUnit (http://rdfunit.aksw.org)
into the UI?
The main reason why I am asking is:
- If we move the ontology out of the Wiki, we can start to use
SHACL to drive the ontology clean up that is quite necessary.
- If this can be integrated, we would probably try to encode
guidelines into SHACL/RDFUnit and then build a continuous
integration system, e.g. as Github hook.
The main feature that we would need however is a good change log
of ontology edits done, which might be out of scope of your project.
--
All the best,
Sebastian Hellmann
Director of Knowledge Integration and Linked Data Technologies
(KILT) Competence Center
at the Institute for Applied Informatics (InfAI) at Leipzig University
Executive Director of the DBpedia Association
Projects: http://dbpedia.org, http://nlp2rdf.org,
http://linguistics.okfn.org, https://www.w3.org/community/ld4lt
<http://www.w3.org/community/ld4lt>
Homepage: http://aksw.org/SebastianHellmann
<http://aksw.org/SebastianHellmann>
Research Group: http://aksw.org
--
All the best,
Sebastian Hellmann
Director of Knowledge Integration and Linked Data Technologies (KILT)
Competence Center
at the Institute for Applied Informatics (InfAI) at Leipzig University
Executive Director of the DBpedia Association
Projects: http://dbpedia.org, http://nlp2rdf.org,
http://linguistics.okfn.org, https://www.w3.org/community/ld4lt
<http://www.w3.org/community/ld4lt>
Homepage: http://aksw.org/SebastianHellmann
Research Group: http://aksw.org
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
DBpedia-discussion mailing list
DBpedia-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
