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

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

PrefixNamespace IRI
n4http://dbkwik.webdatacommons.org/ontology/
n6http://dbkwik.webdatacommons.org/resource/K13CHN0f3-Y92MtFUcbkAQ==
n2http://dbkwik.webdatacommons.org/resource/3onr1qGwAtQKpQSWipAh3Q==
n5http://dbkwik.webdatacommons.org/avatar/property/
n8http://dbkwik.webdatacommons.org/resource/vh5CELhUKYhchE01MHyOMw==
rdfshttp://www.w3.org/2000/01/rdf-schema#
n7http://dbkwik.webdatacommons.org/resource/GAKiAE0oHlIknFYdTGY0_Q==
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
xsdhhttp://www.w3.org/2001/XMLSchema#
Subject Item
n2:
rdfs:label
Avatar Wiki:War Room/Future Industries category
rdfs:comment
__NOWYSIWYG__ Taking into account the people, locations, and objects associated with Future Industries; I would say we have enough articles to create a category for the organization. What do you guys think? BenignSpirit 23:33, November 11, 2017 (UTC)
n5:wikiPageUsesTemplate
n6: n7: n8:
n4:abstract
__NOWYSIWYG__ Taking into account the people, locations, and objects associated with Future Industries; I would say we have enough articles to create a category for the organization. What do you guys think? BenignSpirit 23:33, November 11, 2017 (UTC) Hmm, to be honest, I don’t really see the added informational and navigational value of such a category. 08:35, November 12, 2017 (UTC) Well, seeing as we already have categories for other organizations, why not? Just as a general note, the reason why new categories need community consensus is to try to only have relevant and useful categories on our pages, and we don't really operate according to a "because we can" and "we have A, so why not B"-type of reasoning. 19:47, November 13, 2017 (UTC)