Re: [dxwg] Best practice for a loosely-structured catalog

@makxdekkers, some responses: 

1. The repository that these examples come from does not assign external identifiers to the files/elements. Download access is mediated by a form. So this identification method was the best I could come up with. 

2. Correct. As explained in the (revised) commentary above, these files are representations of parts of the dataset. Representations are usually modeled as `dcat:Distribution`. My sense is that a `dct:hasPart` relationship should be between `dcat:Datasets`. So I tried to respect these various issues using blank nodes for the notional (undescribed) datasets which have distributions that are the actual files.  

3. These are real examples from CSIRO's Data Access Portal (DAP). The DCAT descriptions are, however, manually constructed by me. In the first description for each one I have not use any information that is not already in the metadata in the DAP. It is not perfectly aligned with DCAT, but is a real repository. The goal of this issue is to propose that we develop guidelines for such imperfect 'legacy' repositories. 

The landing page URLs do work, so you can inspect the sources for yourself. 

-- 
GitHub Notification of comment by dr-shorthair
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/253#issuecomment-403332220 using your GitHub account

Received on Monday, 9 July 2018 01:00:58 UTC