Re: gender: Why does vCard Ontology define class hierarchy instead of skos:Concept resources ?

Renato Iannella:
> The vCard Ontology is a mapping of RFC6350 (not a bespoke new vocabulary).
> Hence the "semantics" are normatively defined in that specification, such as for gender values [1].
> 
> [1] http://tools.ietf.org/html/rfc6350#page-32

Some of the example values are funny or interesting: "F;grrrl" and
";it's complicated".

The second component ("grrrl" and "it's complicated") does not seem to
be mapped in the vCard ontology and the first component is missing in
the second example (which probably has the same semantic as "U" for
unknown). But I do not want to start a discussion if something is
missing here.

> However, in many cases, the vCard Ontology properties (such as
> hasGender) are defined as object properties, so other options are
> supported beyond the RFC6350 specification. In this case, other URIs
> can be used for gender values.

My question was not about creating something beyond RFC6350 but about a
different mapping. But I agree: using skos:Concept values is possible
even though the values are not specified in the vCard ontology.

Cheers,
Andreas

Received on Thursday, 5 June 2014 11:33:48 UTC