- From: Karen Coyle via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Dec 2021 18:28:47 +0000
- To: public-dxwg-wg@w3.org
Hmmm. In DCAP-AP `dcat:accessURL` is **mandatory**, and defined as: > This property contains a URL that gives access to a Distribution of the > Dataset. The resource at the access URL may contain information > about how to get the Dataset. `dcat:downloadURL` is optional, and is defined as: > This property contains a URL that is a direct link to a downloadable file in a given format. Given that there are two properties, it makes sense that they would have different semantics. It appears that DCAT-AP has blurred that. The general "rule" (if there is one) for APs is that they may not expand the definition of the properties that they are reusing, but may narrow definitions if the original property has minimal semantic commitment. The usage in the AP must be compatible with the defined semantics in the original vocabulary. Had DCAT-AP used the original definition of `dcat:accessURL` that would have made the difference between them clear. However, it would seem that the constraint on these two properties would have been that *one or the other* is mandatory, whichever fits the specific case, and if both are used they would have different IRIs as their subjects. This does not solve @jakubklimek's problem with existing data that uses the two properties. The dilemma is: change and invalidate existing data, or don't change and continue to create data with this ambiguity. That said, in the work we're doing on [tabular application profiles](https://github.com/dcmi/dctap) in Dublin Core we still have not come up with a good way to say "A or B" as a property constraint. It's a common need and I would very much like to be able to provide that option without greatly complicating what is now a simple table format. I began (and need to finish!) a transformation of [DCAT-AP to DC TAP](https://github.com/dcmi/dctap/blob/main/examples/dcat-ap/dcat-ap.csv) and it works well, but it would not accommodate the either/or that this requires. -- GitHub Notification of comment by kcoyle Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1437#issuecomment-1002725284 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 29 December 2021 18:28:49 UTC