-
Notifications
You must be signed in to change notification settings - Fork 1
issue taggging
We're using https://github.com/timrdf/lodcloud/issues to track issues in the LOD Cloud.
This page describes the tagging convention used for https://github.com/timrdf/lodcloud/issues. We're developing the tagging scheme to better understand the broader themes that Linked Data consumers and produces face in real-world practice.
"of" tags indicate the kind of problem spotted, while "was" is a qualifier of the problem.
For example, an issue tagged of ckan metadata namespace and was missing, as opposed to an issue tagged of ckan metadata namespace and was malformed.
"faced" tags indicate the kind of "sub-issue" that was faced when attempting to resolve the original problem ("of" tags).
For example, when trying to resolve an issue tagged of ckan metadata namespace and was missing, the maintainer faced ckan login forgotten.
"assistance" tags indicate whether or not the maintainer asked the reporter for help to fix the indicated problem ("of" tags). Either assistance needed or assistance not needed.
"also" tags indicate additional problems that were spotted and fixed while attempting to resolve the original problem ("of" tags). For example, a maintainer added a link to a SPARQL endpoint (also ckan metadata sparql) when notified of a instance namespace problem (of ckan metadata namespace and was missing). In this real example, the maintainer also needed help to enter the SPARQL endpoint into the CKAN entry (assistance needed).
Used if the person finding the error fixed it themselves.