- From: JoepvanGenuchten via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Aug 2021 09:44:09 +0000
- To: public-dxwg-wg@w3.org
@andrea-perego thank you for the links to the other discussions. About "why its in here": I see a lot of clarifying arguments, especially in issue 83. I agree with the formal arguments about why you might want a separate object property to describe this particular usecase. But I maintain it should be handled by a geospatially oriented vocabulary and not by one aimed at data cataloging. I would say it makes the catalogging vocabulary cluttered/bulky/bloated with concepts that are/should be handled in different domains. Having said that: i get the sense that decision about this issue has been made and I might disagree with the outcome, but perhaps I should lay that to rest ;-) My suggested description would be: for dcat:bbox: "Represents the physical space the dcterms:Location occupies" for dcat:centroid: "Represents the centerpoint of the dcterms:Location" I appreciate the time you guys take to work through this. -- GitHub Notification of comment by JoepvanGenuchten Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1392#issuecomment-906255448 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 August 2021 09:44:11 UTC