DWBP - Implementation Form - DBpedia
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
$
%
123
 
 
 
 
 
 
 
 
 
 
 
 
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Contact Information
2
Name:
3
EmailPlease, be aware of filling the Evidence URL by replacing the <Evidence URL> with the link of the resource / dataset.

Feel free to provide one or more datasets as DWBP evidences.
4
5
Publisher's information
6
Publisher / Organisation:
7
Site:
8
<Evidence URL> - Fill in <> with the link of the resource / dataset <Evidence URL> - Fill in <> with the link of the resource / dataset
9
PassFailPartially CommentPassFailPartially Comment
10
Best Practice 1: Provide metadata
11
Best Practice 2: Provide descriptive metadata
12
Best Practice 3: Provide structural metadata
13
Best Practice 4: Provide data license information
14
Best Practice 5: Provide data provenance information
15
Best Practice 6: Provide data quality information
16
Best Practice 7: Provide a version indicator
17
Best Practice 8: Provide version history
18
Best Practice 9: Use persistent URIs as identifiers of datasets
19
Best Practice 10: Use persistent URIs as identifiers within datasets
20
Best Practice 11: Assign URIs to dataset versions and series
21
Best Practice 12: Use machine-readable standardized data formats
22
Best Practice 13: Use locale-neutral data representations
23
Best Practice 14: Provide data in multiple formats
24
Best Practice 15: Reuse vocabularies, preferably standardized ones
25
Best Practice 16: Choose the right formalization level
26
Best Practice 17: Provide bulk download
27
Best Practice 18: Provide Subsets for Large Datasets
28
Best Practice 19: Use content negotiation for serving data available in multiple formats
29
Best Practice 20: Provide real-time access
30
Best Practice 21: Provide data up to date
31
Best Practice 22: Provide an explanation for data that is not available
32
Best Practice 23: Make data available through an API
33
Best Practice 24: Use Web Standards as the foundation of APIs
34
Best Practice 25: Provide complete documentation for your API
35
Best Practice 26: Avoid Breaking Changes to Your API
36
Best Practice 27: Preserve identifiers
37
Best Practice 28: Assess dataset coverage
38
Best Practice 29: Gather feedback from data consumers
39
Best Practice 30: Make feedback available
40
Best Practice 31: Enrich data by generating new data
41
Best Practice 32: Provide Complementary Presentations
42
Best Practice 33: Provide Feedback to the Original Publisher
43
Best Practice 34: Follow Licensing Terms
44
Best Practice 35: Cite the Original Publication
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
Loading...
Main menu