Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Collecting implementation evidence for DCAT-2 #767
I started preparing a spreadsheet to collect implementation evidence, based on the table in the DCAT 2014 implementation report:
You can find it here:
In the spreadsheet I added all the classes now in DCAT-2, along all the properties explicitly or implicitly associated with them. I also marked with a gray background those classes/properties which are a legacy from DCAT 2014 - and for which I guess we don't need to provide implementation evidence. Finally, I used other formatting for specifying the new classes / properties, "recommended" properties, those inherited from
Please be aware that I used it in the spreadsheet to report implementation evidence from the European Data Portal.
I suspect this issue is not for the milestone DCAT CR.
That is what I have understood following the discussion during last plenary, and in particular,
and also reading the Candidate rec section in the W3C consortium Process Document.
I might be mistaken, but what is necessary at this stage is to document how adequate implementation experience will be demonstrated by indicating the way we want to follow in the section Status of this document.
For example, in the first candidate REC of the Data on the Web Best Practices, the DWBP group wrote:
DWBP developed a dedicate set of forms, but I guess that we might as well prepare a github wiki page where to provide instruction for implementers considering as possible ways one or more among the following possibilities
The preliminary collection of implementations started by @andrea-perego and @dr-shorthair are in any case useful preparing the CR, they might be precious to identify DCAT features/ terms which might be at risk. In fact, according to the Candidate rec section, the Working Group to publish a Candidate Recommendation
Yes, that was my understanding too. This issue had ended up in the CR milestone simply because I renamed the milestone we were using. I have now created a different milestone and moved this issue there. Thanks.
referenced this issue
Mar 14, 2019
https://docs.google.com/spreadsheets/d/10-UIgM1xLQXNsaSgU6xRsPlsYo3jABreVNwjzciGPKM/edit?usp=sharing is the spreadsheet of @andrea-perego with dcat:DataDistributionService info removed and preds merged with dcat:DataService