Alternative to using DCAT Distribution in GeoBlacklight records
DCAT is pretty complex, and I'm wondering if it perhaps is overkill for GeoBlacklight records. If we aren't planning to use the full DCAT standard (and, no, I'm not suggesting that we do), is it really that helpful to use just the DCAT distribution?
The following is an attempt to present
downloads as simply as possible, with a top-level property for each of those groupings. These groupings will make it easier to automatically render a list of metadata options, or download options, or webservices options, on the GeoBlacklight page.
Each grouping contains an array of objects which typically have just a
type and a
url. I've tried to keep the
type values as simple as possible. The
type value could be used as button or link labels in GeoBlacklight, but this could be overridden by the optional
label value, which would be especially useful to distinguish multiple entries of the having the same basic `t