[foaf-dev] New FOAF properties
zazi at smiy.org
Mon Sep 12 11:49:41 CEST 2011
the Cognitive Characteristics Ontology (CCO) can not be seen as an
ontology for describing an entire CV/Resume, although experience and
parts of the education can be described with the help of terms of CCO
(see also the cco:CharacteristicDynamics  modelling option for this
issue). Furthermore, projects can be related with FOAF terms
(foaf:pastProject , foaf:currentProject ).
DOAC looks very promising for describing an entire CV/Resume. It claims
compatibility to Europass (see ). The problem with DOAC is at least
at the moment that the ontology specification information resource 
doesn't resolve. I found a further example at schemapedia (see ).
AFAIK I reviewed DOAC as well before I started modelling CCO.
Unfortunately, I cannot remember my decision against utilising this
vocabulary for my use case :\
While browsing the LOV repository  for DOAC, I discovered the Whois
Vocabulary , which also seems to be quite promising for modelling an
On 9/12/2011 6:29 AM, Bruce Whealton wrote:
> That's interesting. So, would you use this ontology for specifying an
> entire CV/Resume in RDF/OWL? I see the option for specifying skills but
> what about experience/employment and education?
> -----Original Message----- From: Bob Ferris
> Sent: Sunday, September 11, 2011 8:10 AM
> To: foaf-dev at lists.foaf-project.org
> Subject: Re: [foaf-dev] New FOAF properties
> Hi Bruce,
> On 9/10/2011 9:28 AM, Bruce Whealton wrote:
>> That was very detailed and very helpful. Thanks.
>> IMHO, I think we do need something for expressing resume type
>> It is good to have a foaf:interest but one also likes to express one's
> Yes, this is exactly the domain you can describe with the help of the
> Cognitive Characteristics Ontology , i.e., this vocabulary includes
> terms to describe cognitive patterns in a short way with the help of
> binary relations by utilising sub properties of
> cco:cognitive_characteristics , e.g., cco:skill . If you like to
> describe cognitive characteristics more in detail, you can utilise the
> cco:CognitiveCharacteristics concept. Please have a look at the examples
> section  of the CCO documentation, e.g., the cognitive patterns
> example .
>> I agree with what Bob was saying about CV that the skills,
>> experience and etc. should be related to a foaf:Person. A person has
>> certain skills and experience, not the document about them.
> Cool! ;)
>> I found DOAC - description of a career but that wasn't used too often
>> and was a bit awkward.
>> The only other thing I was thinking about on the foaf:interest is that a
>> dc:title should be included to provide a readable result for SPARQL
> Yep, this is always a good knowledge representation practise (to locally
> include a human-readable label of an utilised, external information
>> Many profiles, that I've seen do use the dc:title attribute, though.
>> I don't know why CV references FOAF at the bottom of it's description
>> but does not ever use any foaf classes or properties.
>> I was reading a recent book on SPARQL and the author uses foaf often
>> for an
>> address book. I guess that is a good idea for using foaf. I thought it
>> would be helpful to keep track of all the different places where I have
>> accounts, blogs, wikis, etc. etc.
>  http://purl.org/ontology/cco/core#
>  http://purl.org/ontology/cco/core#cognitive_characteristic
>  http://purl.org/ontology/cco/core#skill
>  http://purl.org/ontology/cco/core#CognitiveCharacteristic
>  http://purl.org/ontology/cco/cognitivecharacteristics.html#sec-example
More information about the foaf-dev