Re: vCard issues

Hi Mikael, community,

I would like to generalize your question a bit: Linked Data
practitioners regularly run into issues like the ones you are
reporting for VCARD (e.g., I've found similar issues with DCAT, VoID,
GoeSPARQL, and WGS84.  Is there a Github/Redmine/something issues page
where such shortcomings can be reported?  Vocabulary design is never
really 'done', but is a continuous process with updates every so many
years.

---
Cheers,
Wouter.

On Tue, May 22, 2018 at 11:31 AM, Mikael Pesonen
<mikael.pesonen@lingsoft.fi> wrote:
>
> Hi,
>
> there are some issues with vCard RDF schema
> (http://www.w3.org/TR/vcard-rdf/)
>
> For example
>
> - vcard:hasEmail property has range vcard:Email but vcard:Email is
> marked as deprecated
> - no main classes for contact resources: you have to assume that contact
> resource with type vcard:Voice is a telephone number and others might be
> email addresses
> - no range defined for vcard:hasGender even though there is clearly
> defined super class vcard:Gender and male/female/etc classes as sub classes
>
> So my question is is there maybe a patch available to this schema? Or if
> not, would the most obvious solution be recommended: make a patch our
> selves?
>
> Thank you.
>
> --
> Lingsoft - 30 years of Leading Language Management
>
> www.lingsoft.fi
>
> Speech Applications - Language Management - Translation - Reader's and Writer's Tools - Text Tools - E-books and M-books
>
> Mikael Pesonen
> System Engineer
>
> e-mail: mikael.pesonen@lingsoft.fi
> Tel. +358 2 279 3300
>
> Time zone: GMT+2
>
> Helsinki Office
> Eteläranta 10
> FI-00130 Helsinki
> FINLAND
>
> Turku Office
> Kauppiaskatu 5 A
> FI-20100 Turku
> FINLAND
>
>

Received on Tuesday, 22 May 2018 10:53:14 UTC