The position:namespace makes it easy to find positions and take positions independent of any
particular issue statement.

This is particularly important when:

collect them all

See position:all for a list of all positions, and all party positions for a list of all those positions that have been taken by any political party using Living Platform itself. Collect them all! position trading cards may soon be available - see OP:game.

one of several namespaces

See: list of namespaces

open politics argument

The open politics argument standards are still evolving. There are advantages to TIPAESA form but also to debatepoint form or a party platform comparison chart.

Any argument within any position may link to further evidence/source/authority with a cite link. A position may relate to another position with a refer link or simply use it to introduce an argument restated in the context of the main position or "debate point". debatepoint uses a different structure that has some advantages in open-ended debates.

position, evidence, authority

An adversarial process relies on positions, for which there is evidence, which is admitted/vetted by an authority. Simple examples are civil procedure and criminal procedure which employs standard positions like "the defendant is guilty of..." a crime and "the defendant is not guilty of..." the same crime. Both sides may examine the same evidence and neither may withhold "its own" evidence from the other. This permits them to make different arguments using it to back their positions. Or, challenge the source by which the evidence was conveyed or the authorityi that says it matters. At the end of the trial the issue/position/argument structure can be created, with evidence/source/authority for those points that have been challenged. That is the final TIPAESA structure.

for free-floating positions

Unlike a position embedded in an issue/position/argument structure, a position need not be restrained or limited to the list of policy terms, nor indeed to any language used previously. However it must be stated exactly and follow other naming conventions:
  • It cannot have a space after the colon no matter how pretty this looks - prettiness is a quite separate problem
  • In a URI, the colon comes after the protocol, e.g. "mailto:" or "ftp:" but before the domain name - if each position becomes a domain in the local DNS then it presumably does not start with a space. If it does the preceding underscore must be used very consistently - but never a preceding space.
  • it must conserve capitals, since it must assume that the word "position" and the first word of the position statement are not the entire sentence, necessarily, in which the link to the position appears.
  • it must avoid plurals unless it refers to something that is inherently plural, e.g. "multiple stakeholders"
  • it should avoid any use of "a" or "the" or other small words that would make it harder to use the exact wording of the position in an arbitrary sentence