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

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

Subject Item

n2:

rdf:type

n24:

rdfs:label

Capa 'Turum's Covenant

rdfs:comment

When the Great Schism began, the Covenant as it was known was shattered into pieces. With the betrayal of the San'Shyuum and their Jiralhanae servants, the Sangheili were forced to band together in order to better defend themselves against any outside threats. As one of the few High Councilors that survived the Brute Onslaught, Capa was in a unique position to gather support under himself. During the battle of High Charity, Capa and his followers managed to board and capture a large number of ships and equipment before High Charity was fully consumed by the Flood. After escaping the Flood and Loyalist Covenant forces, they want into hiding in a distance part of Covenant space in order to build up and recruit far flung commanders.

n15:

Post-Covenant War conflicts

dcterms:subject

n13: n32:

n20:

Supreme Commander

n3:wikiPageUsesTemplate

n4: n11: n29:

n8:wikiPageUsesTemplate

n9: n14: n27:

n21:

n22:

n23:

Republic

n28:

Sangheili

n31:

2553-01-26

n25:

n26:

n7:abstract

When the Great Schism began, the Covenant as it was known was shattered into pieces. With the betrayal of the San'Shyuum and their Jiralhanae servants, the Sangheili were forced to band together in order to better defend themselves against any outside threats. As one of the few High Councilors that survived the Brute Onslaught, Capa was in a unique position to gather support under himself. During the battle of High Charity, Capa and his followers managed to board and capture a large number of ships and equipment before High Charity was fully consumed by the Flood. After escaping the Flood and Loyalist Covenant forces, they want into hiding in a distance part of Covenant space in order to build up and recruit far flung commanders.

Subject Item

n34:

n19:

n2:

Subject Item

n5:

n6:

n2:

Subject Item

n30:

n6:

n2:

Subject Item

n33:

n6:

n2:

Subject Item

n18:

n19:

n2:

Subject Item

n26:

n19:

n2:

Subject Item

n16:

n17:

n2: