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
n2http://dbkwik.webdatacommons.org/resource/7SaFfmeWY91c6xgm-ZoPjw==
dctermshttp://purl.org/dc/terms/
n9http://dbkwik.webdatacommons.org/ontology/
n4http://dbkwik.webdatacommons.org/resource/kP8KClggoB1Mmap_DuqCbQ==
n8http://dbkwik.webdatacommons.org/resource/Qb3W_PC9ZM3vnGoPQiXorQ==
rdfshttp://www.w3.org/2000/01/rdf-schema#
n3http://dbkwik.webdatacommons.org/memory-alpha/property/
n6http://dbkwik.webdatacommons.org/resource/aTAk5EIyZIYKGn9o_V7kzg==
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
xsdhhttp://www.w3.org/2001/XMLSchema#
Subject Item
n2:
rdfs:label
Memory Alpha:Explain jargon
rdfs:comment
The simplest way to explain jargon is to create a link to a separate article where that term is explained. For example, rather than explaining what an ODN relay is, link to it instead. This way, many articles can all use the same terms and each link to the same single article where that term is explained.
dcterms:subject
n6:
n3:wikiPageUsesTemplate
n4: n8:
n9:abstract
The simplest way to explain jargon is to create a link to a separate article where that term is explained. For example, rather than explaining what an ODN relay is, link to it instead. This way, many articles can all use the same terms and each link to the same single article where that term is explained. (It would be great if you could also explain the jargon you use to explain the jargon, but that might be pushing it a bit. Memory Alpha assumes that visitors are at least familiar with the basic technology and settings of the various series, so it's not essential that all jargon be explained.)