W3C home > Mailing lists > Public > public-esw-thes@w3.org > April 2014

Re: TGN place types (broader/narrower spanning ConceptSchemes)

From: Richard Light <richard@light.demon.co.uk>
Date: Tue, 01 Apr 2014 08:58:54 +0100
Message-ID: <533A71BE.3090500@light.demon.co.uk>
To: public-esw-thes@w3.org

On 01/04/2014 07:07, Osma Suominen wrote:
> On 30/03/14 11:15, Christophe Dupriez wrote:
>> In this precise case, I would model whatever is needed using the most
>> suitable vocabularies available if any.
>> And I would add (automatically if possible) SKOS relations to guide the
>> documentary retrieval engine.
>> I.e. I would model without constraints something ontologically "rock
>> solid" and then derive a "publishing" structure using SKOS.
> +1 for this approach from me too.
Yes, I'd agree with that approach too.  What would be /really/ helpful 
for end-users would be if the various historically-aware place 
authorities (SAPO, TGN, Pelagios, PastPlace, ...) all used the /same 
/ontological structure to express statements about places in time.  
Possibly something CIDOC CRM-based?


> This is what we are doing with the Finnish Spatio-Temporal Ontology 
> SAPO [1]. The ontology itself is modelled using OWL, and has two main 
> classes, time-bound places (similar in spirit to "Crimea after Russian 
> annexation in 2014") and time-independent places (e.g. "Crimea", 
> "Ukraine"). The relations between time-independent and time-dependent 
> places are modelled separately - the current idea is to use the CHANGE 
> vocabulary [2] to model the events (establishment, merge, split etc) 
> that form the time series, but other representations for the 
> representation including a simple part-of/includes property have been 
> used in the past.
> For publishing purposes, a SKOS representation is derived, simply by 
> defining rdfs:subClassOf and rdfs:subPropertyOf relationships that map 
> the classes and properties of the ontology to a simplified SKOS view. 
> The conversion itself is implemented using the Skosify tool [3]. Of 
> course, SPARQL construct queries could have been used here as well, 
> though Skosify does some additional validation and enrichment on the 
> conversion result.
> -Osma
> [1] http://www.seco.tkk.fi/ontologies/sapo/
> [2] http://www.linkedearth.org/change/ns/
> [3] http://code.google.com/p/skosify/

*Richard Light*
Received on Tuesday, 1 April 2014 07:59:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:46:36 UTC