EVENT STYLE

<< Click to Display Table of Contents >>

Navigation:  Support > Reconfigurable Rulebook > Definition Types >

EVENT STYLE

Description

An Event Style defines a type of shooting.

When defining Event Styles the following principles should be employed:

Attributes should not be included in defining an Event Style unless the Attribute refers to different equipment classes. For example, in the ISSF Men’s and Women’s air rifle should not be two different Event Styles since both events are ran by the exact same rules. However, in three-position air rifle there should be separate Event Styles for Sporter and Precision since they represent fundamentally different equipment.

Team events should not have their own Event Styles if the individual and team event have the exact same Stage Styles.

Events that could be shot at different distances should not be given different Event Styles. Unless again they represent different equipment classes.

 

Attribute Name

Type

Description

Discipline

String

The high-level shooting discipline. Must be one of the following strings:

ARCHERY

BENCHREST

BIATHLON

HYBRID

PISTOL

RIFLE

RUNNING TARGET

SHOTGUN

Not required.

EventStyles

List of string

An ordered list of Event Styles that comprise this Event Style. Each Event Style is listed by its SetName.

Either EventStyles or StageStyles, but not both, is required. If included at least one Event Style must be listed

HierarchicalName

String

A HierarchicalName uniquely identifies a definition, excluding the version. It has two parts, namespace and proper name. The namespace identifies the organization that owns the definition. The proper name is a human readable title for the definition. The two parts are concatenated together with colons.

Required

RelatedEventStyles

List of string

A list (order is inconsequential) of other Event Styles that are similar to the defined Event Style. Each Event Style is listed by its SetName.

Not required.

SetName

String

A SetName uniquely identifies a definition within a type. It has three parts, version, namespace, and proper name. The namespace identifies the organization that owns the definition. The proper name is a human readable title for the definition. Version is a major version and minor version pair. Version is prepended with a ‘v’. The three parts are concatenated together with colons. For example, “v1.2:orion:generic target”.

Special case is when version is “0.0” this always denotes the most recent version of the definition. For example, “v0.0:orion:generic target”. “X.0” (where x is a major version) always denotes the most recent version within a major version.

Required, however, managed by Orion's cloud.

SimpleCOFs

List of SimpleCOF

A list of SimpleCOF. This lists the common ways to displaying scores from this Event Style.

Required only if StageStyles is included, and there must be at least one element in the list. It may not be used if EventStyles is included

StageStyles

List of string

An ordered list of Stage Styles that comprise the Event Style. Each Stage Style is listed by its SetName.

 

Either EventStyles or StageStyles, but not both, is required. If included at least one Stage Style must be listed.

Owner

String

The IAM user name of the Orion account. Of the form OrionAcctnnnnnn. Where nnnnnnis the Orion account number. For example OrionAcct001234.

Required for all top level definitions.

Type

String

The type of reconfigurable rulebook definition. Must be one of the following Strings:

ATTRIBUTE

COURSE OF FIRE

DERIVED ATTRIBUTE

EVENT STYLE

FUNCTION

RANGE

RANKING RULES

RESULT

RULEBOOK

STAGE STYLE

TARGET

Required for all top level definitions.

Version

String

Version has two parts, major version and minor version. Both represented by integers. Stored as the concatenation together with an period(‘.’). For example 1.12 (major version = 1, minor version = 12).

Both major version and minor version must start at 1 and increment up.

Required for all top level definitions.

 


 

Note:

The Reconfigurable Rulebook and functionality will be implemented with the release of Orion Scoring System v. 3.0 (TBA)