[rdfweb-dev] Describing FOAF using OWL: enumerating allowed

Dan Brickley danbri at w3.org
Sun Jun 22 17:27:17 UTC 2003


* Danny Ayers <danny666 at virgilio.it> [2003-06-22 19:08+0200]
> 
> > However, OWL steps in the for rescue here, making it possible to make
> > these statements even when using literals (I think this should be
> > the correct syntax, please correct me if not):
> >
> > <owl:Class>
> > 	<rdfs:label>ENTP-person</rdfs:label>
> > 	<rdfs:comment>...</rdfs:comment>
> > 	<rdfs:subClassOf rdf:resource="&foaf;Person"/>
> > 	<rdfs:subClassOf>
> > 		<owl:Restriction>
> > 			<owl:onProperty rdf:resource="&foaf;myersBriggs"/>
> > 			<owl:hasValue
> > rdf:datatype="&xsd;string">ENTP</owl:hasValue>
> > 		</owl:Restriction>
> > 	</rdfs:subClassOf>
> > </owl:Class>
> >
> > This (hopefully) states, that a foaf:Person that has a foaf:myersBriggs
> > of "ENTP" is a member of the class labeled "ENTP-person", which could be
> > given an ID/URI and/or have more statements made about it, statements
> > that would then apply to the foaf:Person in question.
> 
> I'm not sure I understand, isn't this just moving the problem (controlled
> list of literals) to the ENTP-person class? Where would you express the
> Alt-like options ENTP | INTP | (whatever else there is)?

We use the mechanism I outlined before, to control the literals. Morten is 
showing us how to use OWL to make generalisations about all those things 
that have some specified myersBriggs property value. Which is pretty cool.

Dan



More information about the foaf-dev mailing list