This HTML5 document contains 5 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

PrefixNamespace IRI
n6http://dbkwik.webdatacommons.org/ontology/
dctermshttp://purl.org/dc/terms/
n5http://dbkwik.webdatacommons.org/resource/ncmifiwkT7UiuMJV4A-eeg==
rdfshttp://www.w3.org/2000/01/rdf-schema#
n2http://dbkwik.webdatacommons.org/resource/V8ABN2rjFH9-gV6xX3VHlw==
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
xsdhhttp://www.w3.org/2001/XMLSchema#
n8http://dbkwik.webdatacommons.org/resource/X-ypOT2MXdWQ816hdBgCSg==
n7http://dbkwik.webdatacommons.org/bejeweled/property/
Subject Item
n2:
rdfs:label
Bejeweled Wiki:Candidates for speedy deletion
rdfs:comment
There are a few, limited, cases where pages may be deleted speedily. Non-admins can ask for an admin to delete such a page simply by adding a {{delete}} tag. A list of pages to be deleted can be found at . When deleting, check the page history first to see if you can revert to an older version instead of deleting the entire page. You can consider turning problematic pages into relevant redirects as an alternative to deletion.
dcterms:subject
n5:
n7:wikiPageUsesTemplate
n8:
n6:abstract
There are a few, limited, cases where pages may be deleted speedily. Non-admins can ask for an admin to delete such a page simply by adding a {{delete}} tag. A list of pages to be deleted can be found at . When deleting, check the page history first to see if you can revert to an older version instead of deleting the entire page. You can consider turning problematic pages into relevant redirects as an alternative to deletion. Ideally, when an admin deletes a test page or other page with no useful content, it is a good idea to put a note on the author's talk page explaining things, and preserving the deleted content, pointing them to the sandbox in cases of tests.