RE : Side question : mapping OWL classes to SKOS concepts Re: SKOS Guide and owl:sameAs

Hello,

Sorry for breaking in late in the conversation, and perhaps answering in the wrong direction. But what do you think of the solution that would consist of specifying the correspondences between Bernard's OWL hotel ontology and SKOS Accomodation thesaurus using OWL restrictions, which is possible in the example Bernard gave (the following can be a third RDF file, or a specification included in the hotel OWL ontology)

<rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
    xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
    xmlns:owl="http://www.w3.org/2002/07/owl#"
	xmlns:skos="http://www.w3.org/2004/02/skos/core#"
    xmlns="http://www.owl-ontologies.com/unnamed.owl#"
  xml:base="http://www.owl-ontologies.com/unnamed.owl">
  <owl:Ontology rdf:about="#correspondencesBetweenHotelsAndAccomodation"/>
  <owl:Class rdf:about="http://www.bernard.com/HotelOntology#ThreeStars">
    <rdfs:subClassOf>
      <owl:Restriction>
        <owl:someValuesFrom>
          <owl:Class>
            <owl:oneOf rdf:parseType="Collection">
              <skos:Concept rdf:about="http://www.bernard.com/AccomodationConceptScheme#standardAccomodation"/>
            </owl:oneOf>
          </owl:Class>
        </owl:someValuesFrom>
        <owl:onProperty>
          <owl:ObjectProperty rdf:about="http://www.w3.org/2004/02/skos/core#subject"/>
        </owl:onProperty>
      </owl:Restriction>
    </rdfs:subClassOf>
  </owl:Class>
</rdf:RDF>

As Mark said there are two orthogonal problems, but having everything represented in RDF/OWL allow to solve that in a declarative way (well, a declarative way using RDF) and at runtime if Bernard wishes that (provided he uses an OWL reasoner) 

Cheers,

Antoine


-------- Message d'origine--------
De: public-esw-thes-request@w3.org de la part de Bernard Vatant
Date: ven. 03/11/2006 11:24
À: Mark van Assem
Cc: public-esw-thes@w3.org
Objet : Re: Side question : mapping OWL classes to SKOS concepts Re: SKOS   Guide and owl:sameAs
 

Hi Mark

Mark van Assem a écrit :
>> Well I'm not sure what you mean exactly by an "off-line conversion of 
>> the ontology to SKOS", and as said above, I'm not even sure if such an 
> > expression makes sense at all. First it sounds like you're thinking
> > there is a single and systematic way to convert OWL to SKOS, and I hope
>
> No, that's not what I meant.
I was pretty sure of that. Just pointed that the way you put it could be 
misunderstood - at least by me :-)
>
>> it's not the case. Second, it would lead folks to think that SKOS and 
>> OWL are just two languages to model the same things differently, 
>> which IMO is plainly wrong. Actually I hope the ongoing SKOS 
>> standardization 
>
> The problem you are having is twofold:
>
> 1- two different ways to model the world (backoffice/front: one in 
> terms of stars, another in terms of hotel quality)
>
> 2- two different languages to describe domain models (OWL/SKOS: one as 
> a formal class hierarchy, another in loose broader/narrower hierarchy)
Agreed
>
> I am suggesting that problem 1 has nothing to do with problem 2; they 
> are orthogonal. To solve problem 1, you need domain specific rules to 
> convert information from one domain model to the other (from stars to 
> quality). You can:
> - specify rules in some programming language that convert at runtime
> - specify rules in RDF that get interpreted at runtime
So far there is nothing done at runtime even for problem 1, the back 
office content is exported as "publication files", which are indexed by 
the taxonomy engine, along with Web content.
> To solve problem 2 you probably can use some static rules but like you 
> suggest might need some specific ones like you seem to be doing 
> (relating a SKOS concept to specific classes, instances,...)
>
> With my "offline" remark I was suggesting that whatever solutions to 1 
> and 2 you have in place now, you can do the conversions from the OWL 
> data (backend) to the SKOS model (frontend) at "design time" (e.g. 
> once a day on your server), not at "runtime" (e.g. each time a query 
> about a Hotel comes in).
OK, understood. That's indeed what we do in this case where the workflow 
is quite slow.
>
> Hope I'm still making sense...
Sure, you are :-)


*Bernard Vatant
*Knowledge Engineering
----------------------------------------------------
*Mondeca**
*3, cité Nollez 75018 Paris France
Web:    www.mondeca.com <http://www.mondeca.com>
----------------------------------------------------
Tel:       +33 (0) 871 488 459
Mail:     bernard.vatant@mondeca.com <mailto:bernard.vatant@mondeca.com>
Blog:    Leçons de Choses <http://mondeca.wordpress.com/>