Hi Dimitris, all,

there are some slides about this here: https://www.slideshare.net/RalphSchaefermeier/d-bpedia-meeting-2015-ralph-schaefermeier-aood

Meanwhile, I was thinking to use Google Spreadsheets as Ontology Editor, i.e. have one row for each class and property. There are some plus sides:

 * Collaborative Editing
 * Good overview and fast interface
 * Custom functions for validation
 * JS extensions possible
 * can link fields in tables
 * fast editing and tool is known by most of the people
 * good filtering
 * revisioning, but not so restrictive
 * easy to add additional information (make another column or tab)
 * chat

I don't see many negative sides that can not be tackled easily:

 * OWL Export -> I guess we can use one of the thousand available CSV
   to RDF tools
 * Visualisation -> e.g. http://visualdataweb.de/webvowl/#
 * Axiom diff between versions: not sure about this
 * we can still export the ontology and do a git commit with extra
   validation and changelog

Also I created a prototype in 20 minutes:

https://docs.google.com/spreadsheets/d/1BYLBVtddrIz5XKKy1HEpPopxEjqd7eVLlLYG7nsYkp8/edit?usp=sharing

Note that for example subclassof Person I linked the field to =A3 for Agent

All the best,
Sebastian

On 28.06.2017 11:57, Dimitris Kontokostas wrote:
Hi Everyone,

[some background info]
Ralf and Alexandru from fu-berlin developed some prototypes some time ago for maintaining the DBpedia ontology with git / gitlab. It was accompanied with some mapping tools but we decided to move away from the DBpedia specific mapping syntax and go for RML at that time.
We could probably reuse the ontology part solution.

@Ralf, Alexandru, can you share your experience and suggestions here?
iirc you already evaluated WebProtege and tried to integrate with the mappings wiki (WebProtege for ontology / mediawiki for mappings) but it didn't work out well (due to media wiki) right?

Cheers,
Dimitris

On Wed, Jun 28, 2017 at 11:19 AM, Anastasia Dimou <natadi...@gmail.com <mailto:natadi...@gmail.com>> wrote:

    Dear Adam,

    thank you for providing more alternatives for ontology editing!

    I guess we do not necessarily need to go for a single solution but
    there should be at least one! :) I mean there might be
    alternatives and users might choose their preferred. We mainly
    thought of checking the stability of the tools, how good they
    handle the DBpedia ontology and how easy it is to maintain them
    long term.

    So far, Web Protege seems to be the best solution as Ismael
    mentioned. We will discuss in more details on Thursday though, but
    VocBench seems promising too! I'd suggest that you drop an(other)
    e-mail once VB3 is released to notify us. Then we can further
    investigate this alternative too.

    Kind regards,
    Anastasia



        Hi Ismael and Sebastian

        I am not sure if you had a look at Vitro and VocBench.

        " Vitro is a general-purpose web-based ontology and instance
        editor
        with customizable public browsing. Vitro is a Java web application
        that runs in a Tomcat servlet container.". This is the link

        http://vitro.mannlib.cornell.edu/
        <http://vitro.mannlib.cornell.edu/>

        "VocBench is a web-based, multilingual, collaborative development
        platform for managing OWL ontologies, SKOS(XL) thesauri and
        generic
        RDF datasets.

        VocBench 2, developed in the context of a collaboration
        between the
        Food and Agriculture Organization of the United Nations (FAO)
        and the
        ART Group of the University of Rome Tor Vergata, offers a web
        environment for maintaining thesauri, code lists and authority
        resources, providing advanced collaboration features such as
        history,
        validation and a publication workflow, and multi-user
        management with
        role-based access control.

        VocBench 3 (or, simply, VB3), still under development, will
        offer a
        powerful editing environment, with facilities for management
        of OWL
        ontologies and SKOS/SKOS-XL thesauri. It aims to set new
        standards for
        flexibility, openness and expressive power as a free and open
        source
        RDF modelling platform. Its final delivery is planned by the
        end of
        July 2017." . This is the link

        http://vocbench.uniroma2.it/

        Regards,

        Adam

        On Tue, Jun 27, 2017 at 3:49 PM, Sebastian Hellmann
        <hellm...@informatik.uni-leipzig.de
        <mailto:hellm...@informatik.uni-leipzig.de>> wrote:

            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
            
<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
            <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
            <https://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
            <https://www.w3.org/community/ld4lt>
            Homepage: http://aksw.org/SebastianHellmann
            <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
            <mailto:DBpedia-discussion@lists.sourceforge.net>
            https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
            <https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion>




    
------------------------------------------------------------------------------
    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
    <mailto:DBpedia-discussion@lists.sourceforge.net>
    https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
    <https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion>




--
Kontokostas Dimitris


------------------------------------------------------------------------------
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

--
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

Reply via email to