Re: DCAT and GeoSPARQL issues. was - RE: vCard issues

Simon,

Good point on the template - I am making a revision now and will be sure to add this info. “This info” being the only bug and requirement tracking system that we currently have: the Standards Tracker (http://ogc.standardstracker.org/ <http://ogc.standardstracker.org/>). We have discussed an OGC-run forum or list, but have generally been relying on Stack Overflow and a few other sites.

Best Regards,
Scott

> On May 22, 2018, at 4:53 PM, <Simon.Cox@csiro.au> <Simon.Cox@csiro.au> wrote:
> 
> 1. for DCAT use public-dxwg-comments@w3.org or https://github.com/w3c/dxwg/issues 
> 2. for GeoSPARQL probably use requests@lists.opengeospatial.org 
> 
> Scott - The OGC document template needs a standard link for feedback and bug-reports related to published standards! 
> Does OGC have a list for non-members to post to? 
> 
> Simon 
> 
> -----Original Message-----
> From: Wouter Beek [mailto:w.g.j.beek@vu.nl] 
> Sent: Tuesday, 22 May, 2018 20:52
> To: Mikael Pesonen <mikael.pesonen@lingsoft.fi>
> Cc: semantic-web@w3.org
> Subject: 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
>> 
>> 
>