Kadaster - Data on the Web Best Practices

	A	B	C	D	E	F
1	Data on the Web Best Practices
2	W3C Recommendation 31 January 2017			A-dienst is BAG, BRT, BRK, etc.	B-dienst was gemeente eindhoven, mussels/oysters, etc.
3	https://www.w3.org/TR/dwbp/			So, datasets Kadaster owns.	So, non-Kadaster datasets without any SLA
4
5	Title	Frontend / backend	Todo	Implemented A-dienst	Implemented B-dienst	Explanation
6	Best Practice 1: Provide metadata	backend & frontend		Yes	Yes	Basic human- and machine-readable metadata is provided
7	Best Practice 2: Provide descriptive metadata	backend		Yes	Yes
8	Best Practice 3: Provide structural metadata	backend		Yes	No	Structural metadata is provided for Kadaster datasets, but not for the external datasets
9	Best Practice 4: Provide data license information	backend & frontend	licentie tonen op detail pagina	No	No
10	Best Practice 5: Provide data provenance information	backend & frontend	link naar metadata toevoegen	No	No
11	Best Practice 6: Provide data quality information	backend		No	No
12	Best Practice 7: Provide a version indicator	backend & frontend		Yes	No
13	Best Practice 8: Provide version history	backend		No	No
14	Best Practice 9: Use persistent URIs as identifiers of datasets	backend		Yes	Yes
15	Best Practice 10: Use persistent URIs as identifiers within datasets	backend		Yes	No	URIs in B-dienst datasets are based on incremental numbers assigned during transformation to RDF, unclear if they are persistent
16	Best Practice 11: Assign URIs to dataset versions and series	backend		No	No
17	Best Practice 12: Use machine-readable standardized data formats	backend		Yes	Yes
18	Best Practice 13: Use locale-neutral data representations	backend		Yes	Yes
19	Best Practice 14: Provide data in multiple formats	backend		Yes	Yes
20	Best Practice 15: Reuse vocabularies, preferably standardized ones	backend		No	No	vocabularies are reused where available, but with limited coverage
21	Best Practice 16: Choose the right formalization level	backend & frontend	Meenemen in HTML uitwerken	Yes	No	modeling of temporal validity of BAG is complex. B-dienst datasets are just a direct conversion from WFS
22	Best Practice 17: Provide bulk download	backend & frontend	Nog uitwerken zie (https://www.pdok.nl/nl/producten/pdok-downloads/basisregistratie-topografie/topnl/topnl-actueel/top50nl & https://www.pdok.nl/nl/producten/pdok-downloads/atomfeeds)	No	No
23	Best Practice 18: Provide Subsets for Large Datasets	backend & frontend	Nog uitwerken zie (https://www.pdok.nl/nl/producten/pdok-downloads/basisregistratie-topografie/topnl/topnl-actueel/top50nl)	No	No
24	Best Practice 19: Use content negotiation for serving data available in multiple formats	backend		Yes	Yes
25	Best Practice 20: Provide real-time access	backend		-	-
26	Best Practice 21: Provide data up to date	backend		No	No	Whilst A-diest datasets are regularly updated, the update frequency is not clear
27	Best Practice 22: Provide an explanation for data that is not available	backend		No	No
28	Best Practice 23: Make data available through an API	backend		Yes	Yes
29	Best Practice 24: Use Web Standards as the foundation of APIs	backend		Yes	Yes
30	Best Practice 25: Provide complete documentation for your API	backend		Yes	Yes
31	Best Practice 26: Avoid Breaking Changes to Your API	backend		Yes	Yes
32	Best Practice 27: Preserve identifiers	backend		No	No	deleted resources give a 404 response rather than 410 or 303
33	Best Practice 28: Assess dataset coverage	backend		Yes	No	Kadaster vocabularies are available next to the data, so presumably would be archived alongside, or as part of, the dataset
34	Best Practice 29: Gather feedback from data consumers	backend & frontend		Yes	No	Feedback handled via the forum, but only for the A-dienst datasets
35	Best Practice 30: Make feedback available	backend & frontend		Yes	No	Comments on specific resources could be published in machine readable format
36	Best Practice 31: Enrich data by generating new data	backend		No	No	Limited enrichment was done to generate rdfs:label, but very rudimentary. Linksets are not yet published.
37	Best Practice 32: Provide Complementary Presentations	backend & frontend		Yes	No
38	Best Practice 33: Provide Feedback to the Original Publisher	backend & frontend	dataverbeteren functie opnemen in designs	-	-	Relevant for the new datasets (re)published on labs environment
39	Best Practice 34: Follow Licensing Terms	backend		-	-	Relevant for the new datasets (re)published on labs environment
40	Best Practice 35: Cite the Original Publication	backend		-	-	Relevant for the new datasets (re)published on labs environment
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100