Re: [foaf-dev] Birth/death dates and places in the Bio vocab
Dan Brickley <[email protected]>
| Newsgroups | gmane.comp.web.rdfweb |
|---|---|
| Message-ID | <[email protected]> |
On 4 Oct 2010, at 09:43, Alexandre Passant <[email protected]> wrote: > > On 3 Oct 2010, at 16:03, Bob Ferris wrote: > >> Am 03.10.2010 15:46, schrieb Alexandre Passant: >>> >>> On 3 Oct 2010, at 14:44, Bob Ferris wrote: >>> >>>> Am 01.10.2010 15:23, schrieb Alexandre Passant: >>>>> Hi Ian, all >>>>> >>>>> While the Bio vocabulary [1] provides classes for main life events, from where we can use dc:created / geonames:locatedIn to model dates and places it happened, I'd find useful to get simple properties for: >>>>> >>>>> - birthDate >>>>> - deathDate >>>>> - birthPlace >>>>> - deathPlace >>>>> >>>>> 2 first ones would be datatype properties, last one object property. >>>>> There are similar ones in DBpedia exports of persons, but I'd rather having them in this bio-related vocab. >>>>> >>>>> Any opinion on this ? >>>> >>>> What's the problem with bio:Birth[1], e.g. >>>> >>>> _:e a bio:Birth >>>> ; dc:date "1879-03-14" >>>> ; bio:place<http://dbpedia.org/resource/Ulm> # or event:place >>>> . >>>> >>>> and bio:Death[2], e.g. >>>> >>>> _:e a bio:Death >>>> ; dc:date "1955-04-18" >>>> ; bio:place<http://dbpedia.org/resource/Princeton,_New_Jersey> # >>>> or event:place >>>> . >>>> >>> >>> There is no problem per se, I'm just looking for a way to model that without reification. >> >> Well, it's sometimes useful to have for every relationship a "shortcut relation" available. However, I think, when two or more properties are related to one event (which is the case here), then it might be good to use a first class event concept to model it a bit more elegant, or? > > It's probably more elegant conceptually, indeed, and I'm not saying that these reification should not exist. > >> >> What are the real benefits of using the proposed "shortcut relations" instead of a better extendable event concept (okay, everything can always be optional, but that shouldn't really matter here, or?)? > > Having a direct link, i.e. asking my triple store "where that guy was born" rather than "what is the date of the birth event of that guy" Also consider the complexity, readibility and maintainability of RDFa markup. Try adding semantics in long vs short form to 'Dan Brickley was born in Croydon, UK in 1972.' (this also suggests birthYear etc might have value) >> >> The disadvantage of using two or more properties that should associate to one event is, that you do not really associate the properties explicitly to each other? How should a machine know that birthDate and birthPlace belong together to the event birth? > > In that case, you should have only one Birth / Date associated to you. > Yup, this makes a nice and easily missed difference Dan > Alex. > >> If one use a first class event concept instead, this might then be possible, or? >> >> Cheers, >> >> >> Bob > > -- > Dr. Alexandre Passant > Digital Enterprise Research Institute > National University of Ireland, Galway > :me owl:sameAs <http://apassant.net/alex> . > > > > > > > _______________________________________________ > foaf-dev mailing list > foaf-dev-RyYwo1q5J+qsOXdr9/[email protected] > http://lists.foaf-project.org/mailman/listinfo/foaf-dev