This HTML5 document contains 7 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/
n9http://dbkwik.webdatacommons.org/resource/BLsLvQpub-rXjFniZqHsrA==
n8http://dbkwik.webdatacommons.org/resource/1GB42jsAhUygiGKcatE5VQ==
n5http://dbkwik.webdatacommons.org/resource/BJZKw6_MUi-nG7vmEM94qw==
n2http://dbkwik.webdatacommons.org/resource/khb6dIfebBZpQReivDUSfg==
rdfshttp://www.w3.org/2000/01/rdf-schema#
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n7http://dbkwik.webdatacommons.org/resource/foQK8pZrhnm7vzzyDxPg3A==
xsdhhttp://www.w3.org/2001/XMLSchema#
Subject Item
n2:
rdfs:label
Is Wikianswers a search engine
rdfs:comment
No, depending how you use it, it could be better than a search engine because the response you get is always from a human person who mostly researches the question to find the best answer and post it here. It is true that some things call for a search engine, but when it comes to direct questions, and answers from a real live person this is the way to go.
dcterms:subject
n5: n7: n8: n9:
n6:abstract
No, depending how you use it, it could be better than a search engine because the response you get is always from a human person who mostly researches the question to find the best answer and post it here. It is true that some things call for a search engine, but when it comes to direct questions, and answers from a real live person this is the way to go.