Hi Dimitris ,
----- Mail original -----
> De: "Dimitris Kontokostas" <jimk...@gmail.com>
> À: "Julien Cojan" <julien.co...@inria.fr>
> Cc: dbpedia-discussion@lists.sourceforge.net
> Envoyé: Lundi 10 Décembre 2012 11:57:14
> Objet: Re: [Dbpedia-discussion] Ontology maintenance
> Hi Julien,
> I created a similar example some time ago for this case with
> officeholder to distinguish time periods
> (look at the end of
> http://mappings.dbpedia.org/index.php/Mapping_en:Infobox_officeholder
> )
Thanks for the example.
I didn't know this "nodeURI" option.
> I see your point here but this information is already extracted witth
> the reverse property in the first case
> isn't the second triple reduntant?
It would ease the navigation.
As I see from rdf:type relation, redundancy doen't seem to be a problem.
> BTW, I dont know if we can extract a triple this way...
> The ConstantMapping could be an option but I don't think it's
> supported as-is
> Best,
> Dimitris
I have another concern about what class to use.
There is an "Award" class, but it is used for things lie "Nobel Price", .
That's different than an award given to somebody, does it make sense to
introduce a "GivenAward" class ?
There similar problem with event, like "The_Championships,_Wimbledon" vs
"2012_Wimbledon_Championships" ...
> On Mon, Dec 10, 2012 at 12:09 PM, Julien Cojan <
> julien.co...@inria.fr > wrote:
> > Hi,
>
> > I have a concern also with the relation WorldChampion : which
> > domain
> > is SnookerChamp and range xsd:gYear !!
>
> > I believe the right thing to do here would be to introduce an
> > intermediate node of some class "CompetitionTitle" with a property
> > date.
>
> > Is there some good practice for intermediate nodes ?
>
> > - Should we use the same types that for resources that are subject
> > of
> > wikipedia articles ?
>
> > - Should we also keep direct properties (without intermediate
> > node),
> > for instance rename the "worldChampion" relation here in
> > "worldChampionIn" ?
>
> > - Is there a way to give the reverse property to
> > "correspondingProperty" in the IntermediateNodeMapping ?
>
> > For instance as we have now
>
> > > dbpedia:Joe_Davis dbpedia-owl:worldChampion "1927"
> >
>
> > With the IntermediateNodeMapping we can get :
>
> > > dbpedia:Joe_Davis dbpedia-owl:title dbpedia:Joe_Davis_1
> >
>
> > > dbpedia:Joe_Davis_1 rdf:type dbpedia-owl:CompetitionTitle
> >
>
> > How can we also generate :
>
> > > dbpedia:Joe_Davis_1 dbpedia-owl:person dbpedia:Joe_Davis
> >
>
> > Cheers,
>
> > Julien
>
> > > De: "Pablo N. Mendes" < pablomen...@gmail.com >
> >
>
> > > À: rol...@metamatter.nl
> >
>
> > > Cc: dbpedia-discussion@lists.sourceforge.net
> >
>
> > > Envoyé: Samedi 1 Décembre 2012 10:51:12
> >
>
> > > Objet: Re: [Dbpedia-discussion] Ontology maintenance
> >
>
> > > Hi Roland,
> >
>
> > > Thanks for looking into this. We do need more people doing
> > > quality
> > > checks. I wouldn't say that the overlap in infobox fields proves
> > > that they are equivalent. It only shows evidence that they are
> > > related. In this particular case, isn't writer a subproperty of
> > > author? Authors of songs could be writers, composers, etc.? But
> > > authors of (textual) books are writers?
> >
>
> > > I do not know the best way to handle this (Jona?), because I
> > > imagine
> > > that before merging two properties in the ontology we need to
> > > make
> > > sure that all infobox fields in all languages will still make
> > > sense
> > > after the merge. Perhaps we need to flag every affected mapping
> > > (via
> > > discussion page?) & alert the chapters to the change, which then
> > > need to give an ok at the discussion page? Any better ideas?
> >
>
> > > Also, in this particular case it may be safer to "merge up" from
> > > the
> > > more specific to the more generic, at the cost of losing
> > > information
> > > (specificity).
> >
>
> > > Cheers
> >
>
> > > Pablo
> >
>
> > > On Nov 30, 2012 9:35 PM, "Roland Cornelissen" <
> > > metamatter...@gmail.com > wrote:
> >
>
> > > > Hi,
> > >
> >
>
> > > > There are two distinct ObjectProperties mentioned in the
> > > > DBpedia
> > > > ontology that (imho) declare the same thing, those are:
> > >
> >
>
> > > > {{ObjectProperty
> > >
> >
>
> > > > | labels =
> > >
> >
>
> > > > {{label|en|author}}
> > >
> >
>
> > > > {{label|nl|auteur}}
> > >
> >
>
> > > > | rdfs:domain = Work
> > >
> >
>
> > > > | rdfs:range = Person
> > >
> >
>
> > > > | owl:equivalentProperty = schema:author
> > >
> >
>
> > > > }}
> > >
> >
>
> > > > and
> > >
> >
>
> > > > {{ObjectProperty
> > >
> >
>
> > > > | rdfs:label@en = writer
> > >
> >
>
> > > > | rdfs:label@el = σεναριογράφος
> > >
> >
>
> > > > | rdfs:domain = Work
> > >
> >
>
> > > > | rdfs:range = Person
> > >
> >
>
> > > > }}
> > >
> >
>
> > > > In a mapping [1] where both properties are found, they are
> > > > mapped
> > > > each to the same infobox-field. Which proves they are the same.
> > > > Not
> > > > sure if that always holds, but I would say that these
> > > > properties
> > > > need to be merged somehow.
> > >
> >
>
> > > > What would be the correct or best way to handle this?
> > >
> >
>
> > > > Any advice would be appreciated.
> > >
> >
>
> > > > Thanks
> > >
> >
>
> > > > Roland
> > >
> >
>
> > > > [1]
> > > > http://mappings.dbpedia.org/index.php?title=Mapping_nl:Infobox_film&action=edit
> > >
> >
>
> > > > On 11/20/2012 12:23 AM, Roland Cornelissen wrote:
> > >
> >
>
> > > > > Hi,
> > > >
> > >
> >
>
> > > > > I am adding Dutch labels to the ontology and in the process
> > > > > I'm
> > > > > changing
> > > >
> > >
> >
>
> > > > > the old notations to the new coding style.
> > > >
> > >
> >
>
> > > > > While working my way through a lot of properties i run into
> > > > > stuff
> > > > > like this:
> > > >
> > >
> >
>
> > > > > {{ObjectProperty
> > > >
> > >
> >
>
> > > > > | labels =
> > > >
> > >
> >
>
> > > > > {{label|en|person function}}
> > > >
> > >
> >
>
> > > > > {{label|nl|persoon functie}}
> > > >
> > >
> >
>
> > > > > | rdfs:range = PersonFunction
> > > >
> > >
> >
>
> > > > > }}
> > > >
> > >
> >
>
> > > > > In my opinion it would be more complete/precise if the
> > > > > rdfs:domain
> > > > > is
> > > >
> > >
> >
>
> > > > > declared (Person), because obviously this property is
> > > > > intended
> > > > > to
> > > >
> > >
> >
>
> > > > > connect Person to PersonFunction.
> > > >
> > >
> >
>
> > > > > I am tempted to add it to improve the ontology.
> > > >
> > >
> >
>
> > > > > What do you think; how to proceed in a situation like this?
> > > >
> > >
> >
>
> > > > > Thanks,
> > > >
> > >
> >
>
> > > > > Roland
> > > >
> > >
> >
>
> > > > > ------------------------------------------------------------------------------
> > > >
> > >
> >
>
> > > > > Monitor your physical, virtual and cloud infrastructure from
> > > > > a
> > > > > single
> > > >
> > >
> >
>
> > > > > web console. Get in-depth insight into apps, servers,
> > > > > databases,
> > > > > vmware,
> > > >
> > >
> >
>
> > > > > SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> > > >
> > >
> >
>
> > > > > Pricing starts from $795 for 25 servers or applications!
> > > > > http://p.sf.net/sfu/zoho_dev2dev_nov
> > > > > _______________________________________________
> > > >
> > >
> >
>
> > > > > Dbpedia-discussion mailing list
> > > > > Dbpedia-discussion@lists.sourceforge.net
> > > > > https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
> > > >
> > >
> >
>
> > > > --
> > >
> >
>
> > > > metamatter | Drs. Roland Cornelissen | Weersterweg 12 | 9832TE
> > > > |
> > > > Den
> > > > Horn | T +31 (0)50 5515369 | M +31 (0)6 14797518 |
> > > > www.metamatter.nl
> > >
> >
>
> > > > ------------------------------------------------------------------------------
> > >
> >
>
> > > > Keep yourself connected to Go Parallel:
> > >
> >
>
> > > > TUNE You got it built. Now make it sing. Tune shows you how.
> > >
> >
>
> > > > http://goparallel.sourceforge.net
> > >
> >
>
> > > > _______________________________________________
> > >
> >
>
> > > > Dbpedia-discussion mailing list
> > >
> >
>
> > > > Dbpedia-discussion@lists.sourceforge.net
> > >
> >
>
> > > > https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
> > >
> >
>
> > > ------------------------------------------------------------------------------
> >
>
> > > Keep yourself connected to Go Parallel:
> >
>
> > > INSIGHTS What's next for parallel hardware, programming and
> > > related
> > > areas?
> >
>
> > > Interviews and blogs by thought leaders keep you ahead of the
> > > curve.
> >
>
> > > http://goparallel.sourceforge.net
> >
>
> > > _______________________________________________
> >
>
> > > Dbpedia-discussion mailing list
> >
>
> > > Dbpedia-discussion@lists.sourceforge.net
> >
>
> > > https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
> >
>
> > ------------------------------------------------------------------------------
>
> > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>
> > Remotely access PCs and mobile devices and provide instant support
>
> > Improve your efficiency, and focus on delivering more value-add
> > services
>
> > Discover what IT Professionals Know. Rescue delivers
>
> > http://p.sf.net/sfu/logmein_12329d2d
>
> > _______________________________________________
>
> > Dbpedia-discussion mailing list
>
> > Dbpedia-discussion@lists.sourceforge.net
>
> > https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
>
> --
> Kontokostas Dimitris
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Dbpedia-discussion mailing list
Dbpedia-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
