I agree generally, but dcat has been really easy to implement. There’s really only 10-20 required fields and they are all pretty useful and you already know the

I agree generally, but dcat has been really easy to implement. There’s really only 10-20 required fields and they are all pretty useful and you already know them anyway. Someone did a good job, I think, in setting this up to be functional and address the main issues that government catalogs should accomplish- what data that the people paid for are available? It’s also understandable through the json scheme if you’d like to skip the pretty easy to understand web site, https://resources.data.gov/standards/catalog/dcat-us/ https://resources.data.gov/standards/catalog/dcat-us/ My biggest fear with us-dcat3 was that it would be incompatible with 1.1. And this page says it won’t be, so I’m staying optimistic until I review.