foaf:name
foaf:title
spe:jobTitle no FOAF term
spe:role no FOAF term
dc:type
dc:subject
spe:expertise no FOAF term
foaf:interest
spe:hasPublication URI of a Publication resource, but foaf:publications is a foaf:Document, not specific enough
spe:currentProject URI of a Project resource, but foaf:currentProject is a owl:thing, not specific enough
spe:pastProject URI of a Project resource, but foaf:pastProject is a owl:thing, not specific enough
foaf:fundedBy
spe:inGroup URI of a Group resource, no foaf term
spe:inOrganization no foaf term
spe:workContact a blank node for work contact info like address and phone #; but foaf does not have these basic contact info
spe:altwebpage URL of any web page that is about this person; could use foaf:homepage
AJ
On 9/13/06, Ivan Herman <[EMAIL PROTECTED]> wrote:
AJ,
thanks for this answer. Would it be possible to elaborate a little bit
on what problems you have hit wen trying to use vCard (or FOAF)? It
would certainly help us in understanding the issues...
Thanks
Ivan
AJ Chen wrote:
> In developing SPE ontology, I have tried to re-use FOAF and vCard, but
> unfortunately found little can can be re-used. One main reason is that,
> although they may have the terms, the definitions of these terms usually
> don't match what's required by the Person class in SPE ontology. The
> problem mostly comes from the "range" of a ObjectProperty or DataProperty.
>
> I wish there was a Person class defined in RDF or OWL that can be
> re-used in any application and easily extended to include special
> properties in specific domains. Hope the next attempt by W3C will create
> just that.
>
> AJ
>
> On 9/12/06, *kei cheung* < [EMAIL PROTECTED]
> <mailto: [EMAIL PROTECTED]>> wrote:
>
>
> Hi Ivan et al.,
>
> Based on my limited experience, a person in the life science and
> healthcare context can be considered as a subject or patient (which can
> be a subclass of person). Of course, there are other roles a person can
> play (e.g., doctors, researchers, and authors). For genetic studies, a
> group of subjects/indviduals may be a family/pedigree. In this case,
> relationships among these family members may include Father_of,
> Mother_of, Child_of, etc. Other types of relationships can be inferred
> (e.g., uncle, sibling, etc). For popualtion genetics, we need to know,
> for example, the ethnicity of the subjects and the geographical
> information about the population to which the subjects belong. There can
> be mutliple types of ID's (e.g., patient id, cell line id, etc)
> associated with a person (whether the person is a subject or patient).
> Sometimes a dummy person (not a real person) is needed to fill in the
> missing data ( e.g., in linkage data analysis). I am not exactly clear
> how these specific HCLS use cases of persons would impact the generic
> modeling of person. Maybe this is something we all need to think more
> about. This is just my 2-cent thought.
>
> Best,
>
> -Kei
>
>
> Ivan Herman wrote:
>
> >Dear all,
> >
> >we would need some feedback...
> >
> >There were some brainstorming on what vocabularies to use for the
> simple
> >notion of 'Person' in various settings. There is old W3C note for
> an RDF
> >version of vCard[1], but another version was created by Norm Walsh a
> >while ago[2]. And, of course, there is FOAF.
> >
> >The issue came up because some people would like us to update the old
> >[1] note but, if we want to do that seriously, it is not necessarily
> >that easy (the vCard spec itself is not soooo o.k.).
> >
> >Hence the question as a feedback: what does the HCLS community use for
> >something like 'Person'?
> >
> >Thanks for the feedback
> >
> >Ivan
> >
> >
> >[1] http://www.w3.org/TR/vcard-rdf
> >[2] http://norman.walsh.name/2005/12/12/vcard
> < http://norman.walsh.name/2005/12/12/vcard>
> >
> >
>
>
>
>
>
>
> --
> AJ Chen, PhD
> http://web2express.org
--
Ivan Herman, W3C Semantic Web Activity Lead
URL: http://www.w3.org/People/Ivan/
PGP Key: http://www.cwi.nl/%7Eivan/AboutMe/pgpkey.html
FOAF: http://www.ivan-herman.net/foaf.rdf#Me
--
AJ Chen, PhD
http://web2express.org