Fwd: [EXTERNAL] Follow-up on DCAT from D3

Some great feedback from folks I met at a recent workshop...

> Begin forwarded message:
> 
> From: "Aur, Katherine Anderson" <kaaur@sandia.gov>
> Subject: Re: [EXTERNAL] Re: Follow-up on DCAT from D3
> Date: October 28, 2020 at 10:29:11 AM PDT
> To: Annette Greiner <amgreiner@lbl.gov>
> Cc: "Aur, Katherine Anderson" <kaaur@sandia.gov>
> 
> Annette, 
> 
> Sure that’d be great. 
> 
> Thanks! 
> 
> Kale 
> 
> Kale Aur 
> R&D Geosciences Engineer 
> Sandia National Labs 
> 
> 
>> On Oct 28, 2020, at 11:08 AM, Annette Greiner <amgreiner@lbl.gov> wrote:
>> 
>>  Kale,
>> Thanks very much; this is wonderful feedback! Do you mind if I post it to the dataset exchange working group’s public email list and cc you? The editors may want to follow up directly.
>> -Annette
>> 
>>> On Oct 28, 2020, at 9:10 AM, Aur, Katherine Anderson <kaaur@sandia.gov <mailto:kaaur@sandia.gov>> wrote:
>>> 
>>> Annette,
>>>  
>>> We have a few comments on DCAT that might be of use to the committee:
>>>  
>>> We added schema:version into the Resource, Dataset and Catalog Classes for versioning information. Might be better to have a DCAT term for this.
>>>  
>>> We are using dct:relation, dct:replaces, prov:wasGeneratedBy to show how Resources are related and their provenance.
>>> The official DCATv2 documentation could be more explicit with how to handle these types of situations. We had a few confusing discussions around these terms.
>>>  
>>> We found the schema.org <http://schema.org/> vocabulary to be more comprehensive for our purposes than the FOAF vocab for People/Organizations.
>>>  
>>> We used more schema.org <http://schema.org/> vocabulary for publications (datePublished, author, publisher, numberOfPages, etc…). These seemed to fit our needs better than the recommended dcat and dct terms for this.
>>>  
>>> Consider adding some DCATv2 terms for Software. We used a mix of our own terms and schema.org <http://schema.org/> terms for this.
>>>  
>>> I think in general the documentation for DCATv2 could use some more detailed implementation examples to help people better understand the use cases for the different vocab terms.
>>>  
>>> We added Documentation and Software classes to describe new Resource that we needed that were not a Dataset or a DataService. We followed the advice on the DCAT pretty well and found this note to be helpful: ‘It is strongly recommended to use a more specific sub-class. When describing a resource which is not a dcat:Dataset or dcat:DataService, it is recommended to create a suitable sub-class of dcat:Resource, or use dcat:Resource with the dct:type property to indicate the specific type.’
>>>  
>>>  
>>> Let me know if you have any further questions on any of the items mentioned above.
>>>  
>>> Thanks,
>>> Kale
>>>  
>>>  
>>> Kale Aur
>>> R&D Geosciences Engineer
>>> Sandia National Laboratories
>>