dcmi / dctap

DC Tabular Application Profile

Home Page:https://dcmi.github.io/dctap/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

DCAT example has no theme

philbarker opened this issue · comments

Dataset should have a property dcat:theme, instead it has dcat:themeTaxonomy (with label Theme). I think there also needs to be a Concept shape for the value of the theme property.

ps: there are a few other properties that should have skos:Concepts for their values (dct:type, adms:status, adms:availability), you have Literal and IRI (with no constraint) for these. I think I recall Karen mentioning that she wasn't sure how to deal with Concepts in this example, so perhaps we need to discuss this.

Thanks, Phil, yes, DCAT:Catalog has themetaxonomy, and Dataset has theme. I bet that was the spreadsheet program being helpful.

I need to do a full review of the DCAT-AP and I'll look back at the full DCAT-AP with your comments in mind. The documentation doesn't show those properties having skos:Concept values, but maybe that information is buried in the document in a way that it isn't obvious. That DCAT-AP TAP is also missing the connecting arcs between shapes, and I'm still not sure where those take place, but I'm getting a better idea working on a TAP based on some actual DCAT data, not the DCAT-AP specs. In the actual data the thing listed as the Class actually represents a locally identified thing of that class, and that locally identified thing has the outgoing arcs. At least, I think it works that way, and will try that out when I get back to the big DCAT-AP. The small data example (from Eurostat) is making more sense to me so I'll complete that, since it is in fact an AP of the DCAT-AP and quite a bit smaller. I think this TAP will illustrate the utility of being able to define data based on DCAT-AP.

There is an update to the DCAT-AP in progress. This is not yet done so there may still be changes. The previous release folder shows what may accompany it.

DCAT-AP TAP example fixed.