Hello,
Regarding class usage, the Dutch chapter does a great job already and
Magnus' query returns no results;) [1]
This means that all classes are needed at the moment.
Regarding the changes, I am also in favor to move forward and fix all
inconsistencies. Let's start already with the obvious ones and discuss any
major changes in the DBpedia meeting.
Changing PopulatedPlace for instance will break many applications but if
this is the way to go I am also in
Cheers,
Dimitris
[1] http://nl.dbpedia.org/sparql?default-graph-uri=http%3A%2F%2Fnl.dbpedia
.org&query=SELECT+DISTINCT+%3Ftype+WHERE+%7B%3Ftype+a+owl%3AClass.+FILTER+NOT+EXISTS+%7B%3Fsubject+a%2Frdfs%3AsubClassOf*+%3Ftype.%7D+%7D%0D%0A&format=text%2Fhtml&timeout=0&debug=on
On Sat, Apr 12, 2014 at 3:58 AM, Kingsley Idehen <kide...@openlinksw.com>wrote:
> On 4/11/14 2:12 PM, Patel-Schneider, Peter wrote:
>
>> This proposal illustrates one of the major problems with the DBpedia
>> ontology - triples check in but they never check out.
>>
>
> Sorta, because of the misconception that SPARQL is steal Read-Only. I
> spend a good chunk of my day writing SPARQL 1.1 using INSERT, DELETE, and
> UPDATE (via INSERT and DELETE combos) to massage data, across many data
> spaces.
>
>
>
>> Many of the problems with the DBpedia ontology require changes.
>>
>
> Change is good. And it will work. Remember, DBpedia deploys Linked Data
> using a Quad Store, so the re-write rules and SPARQL queries used to
> perform the name->address indirection are extremely flexible. For instance,
> you can actually set the named graph URI scope for these SPARQL queries
> explicitly or via our NOT FROM NAMED GRAPH extension re., negation etc..
>
> You can have a list of Named Graphs or excluded Named Graphs when
> generating the description of a DBpedia Entity URI's referent.
>
>
>> Other problems have to do with the expressivity of the ontology.
>>
>
> Again, its just triples to which SPARQL 1.1 patterns can be applied. In
> short, this is the way to truly appreciate the power of SPARQL and Linked
> Data.
>
>
> I don't think that changes here can be effected just by adding and
>> removing bits of the ontology.
>>
>
> You can variants of the Ontology, an alternative Ontology, it doesn't
> matter, the Linked Data deployment will be unaffected.
>
>
> Other problems have to do with the philosophy of the ontology.
>>
>
> The philosophy of the Ontology cannot change, that's a world view of the
> ontology creators. That doesn't stop another ontology existing as an
> alternative set of "context lenses" into the same data.
>
> I encourage you to make your changes, or make a new ontology, whichever
> path you take, the end product will be useful and a showcase for
> perspectives sometimes overlooked due to blurred and blurry perspectives :-)
>
> We can do this, its the next stage in the natural evolution of DBpedia and
> the broader Linked Open Data Cloud.
>
> Note: there is zero speculation in my response. I've already done (and
> continue to do) a lot of this (hands on fashion) over the years, following
> LOD cloud initial bootstrap.
>
>
> BTW -- This mail was easy to write as I've just completed (literally
> minutes ago) a marathon session on SPARQL 1.1 which amounted to an ACL
> (data access policy and access control list) debugging session.
>
> Kingsley.
>
>
>> 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
>>>
>>
>>
>>
>
> --
>
> 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
>
>
--
Kontokostas Dimitris
------------------------------------------------------------------------------
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
