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
n7http://dbkwik.webdatacommons.org/ontology/
dctermshttp://purl.org/dc/terms/
n6http://dbkwik.webdatacommons.org/resource/cWh7df2PB31Ux04UFMIEgg==
n5http://dbkwik.webdatacommons.org/doom/property/
rdfshttp://www.w3.org/2000/01/rdf-schema#
n2http://dbkwik.webdatacommons.org/resource/Ovou8Hy8I-SkHX-MI5DyeQ==
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n4http://dbkwik.webdatacommons.org/resource/EdBeQ_w-WUEV8wFQ5sn6Qg==
xsdhhttp://www.w3.org/2001/XMLSchema#
Subject Item
n2:
rdfs:label
Seg
rdfs:comment
SEGS (an abbreviation for segments) is the name of a WAD lump which is a component of a level. It is normally generated automatically from other data for the level using a node builder tool. Segs are segments of linedefs, and describe the portion of a linedef that borders the subsector that the seg belongs to.
dcterms:subject
n4:
n5:wikiPageUsesTemplate
n6:
n7:abstract
SEGS (an abbreviation for segments) is the name of a WAD lump which is a component of a level. It is normally generated automatically from other data for the level using a node builder tool. Segs are segments of linedefs, and describe the portion of a linedef that borders the subsector that the seg belongs to. Initially, one seg is created for each one-sided linedef, and two segs are created for each two-sided linedef (one for each side). If the area that a seg borders is later divided into two different subsectors, then a new vertex is created at the division point and the seg is split into two at that vertex. The segs are stored in sequential order corresponding to subsector number. The seg entries are referenced from the subsector entries, which are referenced from the nodes lump.