- From: Andrea Perego via GitHub <sysbot+gh@w3.org>
- Date: Thu, 04 Jul 2019 20:32:15 +0000
- To: public-dxwg-wg@w3.org
I'm also not sure. One reason to keep it is that, in DCAT2, w3cgeo is the only option to specify point coordinates separately, which may be relevant for some use cases - the other properties use WKT as a recommended encoding. I'm also unsure about recommending against the use of w3cgeo. It is indeed used a lot - LOV reports 48 incoming links: https://lov.linkeddata.es/dataset/lov/vocabs/geo I remember when @danbri was explaining how w3cgeo was developed. It is true that it is no longer maintained, and it didn't have wide review, but the fact that is being used so much, and for such a long time, to me means that it is fit for purpose (at least for the vocabularies re-using it). Also, schema.org uses an equivalent representation for points, and since schema.org is under a continuous review, I wonder whether the option of deprecating those properties was discussed and, in such a case, why the decision was not to deprecate it. -- GitHub Notification of comment by andrea-perego Please view or discuss this issue at https://github.com/w3c/dxwg/issues/970#issuecomment-508571696 using your GitHub account
Received on Thursday, 4 July 2019 20:32:18 UTC