This proposal illustrates one of the major problems with the DBpedia ontology - triples check in but they never check out.
Many of the problems with the DBpedia ontology require changes. Other problems have to do with the expressivity of the ontology. I don't think that changes here can be effected just by adding and removing bits of the ontology. Other problems have to do with the philosophy of the ontology. peter On Apr 11, 2014, at 5:27 AM, Kingsley Idehen <kide...@openlinksw.com> wrote: > On 4/11/14 5:47 AM, Magnus Knuth wrote: >> Hello Peter, >> >> thank you very much for your inputs. The state of the DBpedia ontology is >> certainly an issue. >> You can register at [1], ask for editing rights, and go on and make your >> changes. I'd also feel not quite well performing major changes or removing >> classes without some discussion, since it is the effort of others and it is >> not always clear, if somebody actually uses it. >> >> Maybe, we could organize an ontology enhancement and guidelines workshop at >> the next DBpedia Community Meeting in Leipzig [2]. >> >> [1]http://mappings.dbpedia.org/index.php?title=Special:UserLogin >> [2]http://wiki.dbpedia.org/meetings/Leipzig2014 > How about the following procedure: > > [1] Triples relating to fixes and new relations are first created in an RDF > document that 's WWW accessible > [2] The documents are announced here as an "invite to examine" request etc.. > [3] If acceptable, the Triples are added to the project > [4] If unacceptable, for any reason, then in the very worst case (re. > deadlocks) the Triples end up where they are on in a specific named graph in > the Virtuoso instance . > > The real beauty of AWWW, as exemplified by Linked Data, is the ability to > "agree to disagree" without creating inertia. Virtuoso can handle many Linked > Data scenarios, and "agreeing to disagree" lies at the core of its design > (like AWWW). > > Peter: we would all gladly welcome your input and contributions. The steps > above will make this smooth and ultimately enlightening :-) > > -- > > Regards, > > Kingsley Idehen > Founder & CEO > OpenLink Software > Company Web: http://www.openlinksw.com > Personal Weblog: http://www.openlinksw.com/blog/~kidehen > Twitter Profile: https://twitter.com/kidehen > Google+ Profile: https://plus.google.com/+KingsleyIdehen/about > LinkedIn Profile: http://www.linkedin.com/in/kidehen > > > > > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees_______________________________________________ > Dbpedia-discussion mailing list > Dbpedia-discussion@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ Dbpedia-discussion mailing list Dbpedia-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
