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

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

PrefixNamespace IRI
dctermshttp://purl.org/dc/terms/
n3http://dbkwik.webdatacommons.org/ontology/
n2http://dbkwik.webdatacommons.org/resource/wf2BxrxskEbpxG1qMhiNrg==
rdfshttp://www.w3.org/2000/01/rdf-schema#
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n6http://dbkwik.webdatacommons.org/resource/as4ZbjOj4EG0w3_KPoZepw==
xsdhhttp://www.w3.org/2001/XMLSchema#
Subject Item
n2:
rdfs:label
Arika Kalm
rdfs:comment
Style Notes: The ST prefers anything that would be represented with dots to be a numeral spelling out how many are in a given category. Instead of putting three asterisks or whatever next to your Strength, you would put the numeral “3” beside Strength. This sheet has been prepared with the Solar Exalts in mind, as Solars are the default Exalt type for game-play. It is advisable to make the Name tag into a link to your character's category as well.
dcterms:subject
n6:
n3:abstract
Style Notes: The ST prefers anything that would be represented with dots to be a numeral spelling out how many are in a given category. Instead of putting three asterisks or whatever next to your Strength, you would put the numeral “3” beside Strength. Note that text inside the == Headings Markup == will appear in the contents box as a link to that section. Text that should not appear inside the headings markup should appear on the line below the headings markup. (The number of nested headings markup characters, the equals sign, indicates the sub-heading and sub-sub-heading status, ad nauseum.) This sheet has been prepared with the Solar Exalts in mind, as Solars are the default Exalt type for game-play. It is advisable to make the Name tag into a link to your character's category as well.