Open Tournament Summary
  • Overview
  • Guiding Principles
  • JSON Object
  • Storage Format
  • Standardized Tournament Summary
    • The Specification
    • spec_version
    • site_name
    • network_name
    • internal_version
    • tournament_number
    • tournament_name
    • start_date_utc
    • end_date_utc
    • currency
    • buyin_amount
    • fee_amount
    • bounty_fee_amount
    • bounty_value_amount
    • initial_stack
    • type
    • flags
    • speed
    • prize_pool
    • hero_player_name
    • player_count
    • tournament_finishes_and_winnings
    • rebuy_cost
    • addon_cost
    • tournament_rebuys
  • speed object
    • <speed_object>
    • type
    • round_time
  • Tournament Finish Object
    • <tournament_finish_obj>
    • player_name
    • finish_position
    • still_playing
    • prize
    • ticket_value
  • TOURNAMENT REBUY OBJECT
    • <tournament_rebuy_obj>
    • player_name
    • rebuys
    • addons
  • String Formats
    • version_string
  • Examples
    • Sample Sit N' Go
    • More coming soon.
  • Contact Us
    • Change Request Process
    • Support
  • CHANGE LOG
    • Change Log
Powered by GitBook
On this page

Was this helpful?

Guiding Principles

Our guiding principles for making design choices.

This specification was created and will be maintained by following these main principles:

  • Open Standard:

    • No Intentional Secrets: The standard does NOT withhold any detail necessary for interoperable implementation. As flaws are inevitable, the standard will fix flaws identified during implementation and interoperability testing and incorporate said changes into a revised version or superseding version of the standard to be released under terms that do not violate the open standard requirement.

    • Availability: The standard is freely and publicly available under royalty-free and patent-free terms.

    • No Agreements: There is no license agreements, NDA, grant, click-through or any other form of paper to deploy conforming implementations of the standard.

    • Interoperable: Implementation and consumption of the standard does not require any non open standard technology.

  • Lossless:

    • The standard should allow for no loss of data from the real-time events from the user's perspective. The user's perspective should be completely repayable via the user at any point in time after the hand has completed.

  • Efficient

    • The standard should be as efficient as possible without sacrificing data loss and portability. However, due to cheap storage, efficiency should always be the last guiding principle.

PreviousOverviewNextJSON Object

Last updated 5 years ago

Was this helpful?