- From: Karen Coyle via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Feb 2022 14:27:51 +0000
- To: public-dxwg-wg@w3.org
@agreiner What you describe is something I mentioned before, which it seems that downloadURL is a more specific property whose value could be included in accessURL, which I would define as a property/subproperty relationship. I don't know if it works this way, but perhaps in that case downloadURL would be considered an accessURL for the purposes of searching. I'm thinking of an analogy to the way that SPARQL manages retrieval using class relationships. In any case, I think that making a specific relationship between them would clarify their semantics. It also would provide an opening for other subproperties if those are desired. This then brings up the issue that one of the options in accessURL is "service" yet service is defined elsewhere in DCAT with its own endpointURL. So I won't comment further, because it is just getting more messy in my head. I suspect that the answer is to leave DCAT-AP as is, since people seem to have found a comfortable way to make use of it. -- GitHub Notification of comment by kcoyle Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1437#issuecomment-1029044852 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 February 2022 14:27:53 UTC