a
Onderwerp: Re: [DBpedia-discussion] Purpose of the DBpedia Ontology was Re:
Call for Ontology Editor demos for DBpedia
There was a suggestion to eliminate all or most of the subclasses of Person
from the DBpedia ontology. What happens then?
The current DBpedia ontology has a large number of class
There was a suggestion to eliminate all or most of the subclasses of Person
from the DBpedia ontology. What happens then?
The current DBpedia ontology has a large number of classes under Person.
Many of these classes are related to occupations, such as Architect, Artist,
and Athlete. Under many
Hello,
The problem of the proper ontology occures, if you think, what kind of
users do you have, who query your dataset. If you think there are aliens,
then you have to define the whole world with your ontology whathever your
dataset represents.
If you make for me an ontology for dbpedia-
Jaccoud Amaral
PETROBRAS
=
De: "Peter F. Patel-Schneider"
Para: Sebastian Hellmann ,
jacc...@petrobras.com.br, Paul Houle
Cc: DBpedia
Data: 2017-07-17 09:55
Assunto: Re: [DBpedia-discussion] Purpose of the DBpedia Ontology
was Re: Call fo
---
From: "Peter F. Patel-Schneider"
To: "Sebastian Hellmann" ;
jacc...@petrobras.com.br; "Paul Houle"
Cc: "DBpedia"
Sent: 7/17/2017 8:55:04 AM
Subject: Re: [DBpedia-discussion] Purpose of the DBpedia Ontology was
Re: Call for Ontology Editor demos for D
Roles? (Actor / Role pattern in OOP). I call it 'metaclasses' using the
'kind' abstraction of type inference by aggregation of common properties
and their values. RDF allows for a class to be instance (not subclass) of
another class. Also OWL restrictions could be used to model roles.
Regards,
Seb
One reason to have a subclass structure under Person (but also under any
natural kind) is to support generalizations for subcategories. Many of the
subclasses of Person in DBpedia are for occupations, e.g., Architect, Athlete,
NascarDriver, Politician, and Senator. If these subclasses of Person a
> to doctrine, etc.
>
> It is definitely not an area you will get complete agreement on!
>
> -- Original Message --
> From: "Peter F. Patel-Schneider"
> To: "Sebastian Hellmann"
> Cc: "DBpedia"
> Sent: 7/14/2017 12:31:40 PM
> Sub
Original Message --
From: "Peter F. Patel-Schneider"
To: "Sebastian Hellmann"
Cc: "DBpedia"
Sent: 7/14/2017 12:31:40 PM
Subject: Re: [DBpedia-discussion] Purpose of the DBpedia Ontology was
Re: Call for Ontology Editor demos for DBpedia
On 07/11/20
On 07/11/2017 03:10 PM, Sebastian Hellmann wrote:
> Hi all,
>
> DBpedia has always had a firm founding in engineering and we should see the
> whole thing as an "information machine". From this perspective the purpose of
> the DBpedia Ontology becomes quite clear:
>
> - Usability for queries - dri
I must admit I find this discussion fascinating.
As far as I understand, Sebastian H. proposes NOT to materialize the types
in the DB.
So (what I call) service implementors (or call them SPARQL authors, if you
want) will specialize their query by first matching a set of qualifying
properties that
Regarding typing by the properties of aggregated subjects / objects: domain
/ range having these properties or values for those properties (meta-types,
I call them 'kinds') I see no trouble in inferring inheritance hierarchies
being sub-classes a superset of the properties of parent classes
propert
Once again, I will give you my opinion, as the service implementor of
search.datao.net.
search.datao.net is a lookup service where you type the label of a
resource, retrieve from an internal DB all the resources of the
LinkedData with such a label (+their type and endpoint), and then
lookup all t
Sebastian Hellmann wrote on
2017-07-11 19:10:03:
> By the way, is there actually any sensible class that can be
> subclass of Person? As far as I see, the only essential distinction
> that lasts lifelong is fictious/non-fictious . We are thinking about
> disallowing subclasses of Person, unless
Hi all,
DBpedia has always had a firm founding in engineering and we should see
the whole thing as an "information machine". From this perspective the
purpose of the DBpedia Ontology becomes quite clear:
- Usability for queries - driven by the question, what do our users want
to retrieve?
15 matches
Mail list logo
