The purpose of this file is to define a set of rules a software program may use to create and validate canine Rally Obedience courses.
Using an XML file allows for easy support of multiple Rally Obedience sanctioning organizations and different versions of the rules for any sanctioning group.
In fact, using this approach would make it easy for anyone to create any set of rules, for any occasion.
This page defines how such XML files are to be formatted.
Rally Rule Set files should be created with a suffix of .rrs.
The .rrs files should be located within a single file and the image files should be within a sub-directory
shown below as the SIGN_LOCATION element.
And, it's up to the program to decide whether these files must be installed within a certain directory on their device, or if the program will search
all of its storage for .rrs files (as is common with tablet apps).
It is up to the program to decide if it wants to search the internet for .rrs files.
Contents
The first line of the file defines that the file contains XML content.
From there, we have the outermost element within the file, the RALLY_RULE_SET element.
Exactly one such element is required.
The NAME attribute is required.
When a program needs to display a list of all of the available rule sets (say, when creating a new course),
the program should display a list of the NAME attributes, with one item in the list for each rule set available to the device.
It is up to the device to define where these rule set files must reside - some may choose to only recognize rule set files within a certain directory,
others may choose to recognize rule set files anywhere on the device.
<?xml version="1.0" encoding="ISO-8859-1"?>
<RALLY_RULE_SET NAME="AWKC - January 1, 2012">
.
.
.
</RALLY_RULE_SET>
|
Within the RALLY_RULE_SET element, the following elements may exist.
<?xml version="1.0" encoding="ISO-8859-1"?>
!<-- Comments -->
<RALLY_RULE_SET NAME="AWKC - January 1, 2012">
<REGISTRY>The All-World Kennel Club</REGISTRY>
<REGISTRY_ABBREVIATION>AWKC</REGISTRY_ABBREVIATION>
<EFFECTIVE_DATE>1/1/2012</EFFECTIVE_DATE>
<REGISTRY_URL>https://www.tawkc.org</REGISTRY_URL>
<RULEBOOK_URL>https://www.awkc.org/rulebook.pdf</RULEBOOK_URL>
<SIGN_LOCATION>tawkc_20120101</SIGN_LOCATION>
<ALTERNATE_SIGN_LOCATION>https://www.awkc.org/rallysigns
</ALTERNATE_SIGN_LOCATION>
<COURSE_VERSION>1.00 of 12/29/2011</COURSE_VERSION>
<DISTANCE_UNITS>Feet (US)</DISTANCE_UNITS>
<DATE_FORMAT>MM/DD/YYYY</DATE_FORMAT>
<SANCTIONED_RULE_SET>TRUE</SANCTIONED_RULE_SET>
<COUNT_HONOR_AS_NUMBERED_STATION>TRUE</COUNT_HONOR_AS_NUMBERED_STATION>
<COUNT_START_FINISH_AS_NUMBERED_STATION>TRUE</COUNT_START_FINISH_AS_NUMBERED_STATION>
<COURSE_TYPES>see below</COURSE_TYPES>
<SIGNS>see below</SIGNS>
<ACCESSORIES>see below</ACCESSORIES>
</RALLY_RULE_SET>
|
Let's look at these attributes and elements in more detail.
- REGISTRY (attribute): The full name the registry goes by.
If someone makes up their own rules and signs, they may put their name into this field.
- REGISTRY_ABBREVIATION: The short name the registry goes by.
If someone makes up their own rules and signs, they may put their initials into this field.
- EFFECTIVE_DATE: If this set of rules supercedes a previous set, put in the date this set becomes effective.
- REGISTRY_URL: The link to the registry's website.
- RULEBOOK_URL: The link to the rulebook for this rule set.
- SIGN_LOCATION: Directory path to get to the signs for this rule set.
The path is relative to the location of the .rrs file, unless a URL is provided.
Issue: Different operating systems use different directory delimiters, e.g. Windows uses a backslash, UNIX/LINUX uses a forward slash,
Mac uses a colon.
- ALTERNATE_SIGN_LOCATION: A back-up path to get to the signs for this rule set.
This should be a URL.
- VERSION: Used to keep track of the latest copy of this file.
- DISTANCE_UNITS: "Feet (US)", "Yards (US)", "Meters"
- DATE_FORMAT: Use "Y", "M", "D" and "/" characters to create sequence, such as "MM/DD/YYYY" or "M/D/YY" for US date formats.
- SANCTIONED_RULE_SET: "TRUE" or "FALSE".
This describes whether the registry offering this event has confirmed that this rule set conforms to their written rule set.
If omitted, the value "FALSE" shall be assumed.
- COUNT_HONOR_AS_NUMBERED_STATION:
This describes whether this registry includes the honor station(s) in its count of numbered stations.
If omitted, the value "FALSE" shall be assumed.
- COUNT_START_FINISH_AS_NUMBERED_STATION:
This describes whether this registry includes the Start and Finish station(s) in its count of numbered stations.
If omitted, the value "FALSE" shall be assumed.
COURSE_TYPES
Within the COURSE_TYPES element, one or more COURSE_TYPE elements must exist.
These represent course Levels, sorry for the mix-up in tags.
<COURSE_TYPES>
<COURSE_TYPE LEVEL="Beginners" TYPE="Regular">
<CLASSES>A/B</CLASSES>
<UNITS>Feet (US)</UNITS>
<MIN_RING_WIDTH>40</MIN_RING_WIDTH>
<MIN_RING_HEIGHT>50</MIN_RING_HEIGHT>
<MAX_RING_WIDTH>60</MAX_RING_WIDTH>
<MAX_RING_HEIGHT>70</MAX_RING_HEIGHT>
<INITIAL_RING_WIDTH>50</INITIAL_RING_WIDTH>
<INITIAL_RING_HEIGHT>60</INITIAL_RING_HEIGHT>
<SIGNS_ON_MENU>1-25,28-33</SIGNS_ON_MENU>
<MIN_STATIONS>20</MIN_STATIONS>
<MAX_STATIONS>25</MAX_STATIONS>
<MIN_STATIONARY_SIGNS>20</MIN_STATIONARY_SIGNS>
<MAX_STATIONARY_SIGNS>25</MAX_STATIONARY_SIGNS>
<MIN_SIGN_SPACING TYPE="SOFT">10</MIN_SIGN_SPACING>
<ALLOW_MARRIED_SIGNS LIMIT="2">TRUE</ALLOW_MARRIED_SIGNS>
<USE_POINTS>200</USE_POINTS>
<TOTAL_POINTS>200</TOTAL_POINTS>
<DEFAULT_POINT_VALUE>10</DEFAULT_POINT_VALUE>
<POINT_DOUBLERS>TRUE</POINT_DOUBLERS>
<SIDE_SWITCH_SIGN>87</SIDE_SWITCH_SIGN>
<MAX_SIDE_SWITCHES">3</MAX_SIDE_SWITCHES>
<MAX_SWITCHED_SIDES">6</MAX_SWITCHED_SIDES>
<MIN_STATIONS_FROM_SET NUMBER="5" ALT_ERROR="Display this error instead.">3-37,50-59</MIN_STATIONS_FROM_SET>
<STATION_FROM_LIST STATION="10">8-18,22-42</STATION_FROM_LIST>
<MUST_BE_FOLLOWED_BY FIRSTSIGN="18" ALT_ERROR="Display this error instead.">2,3</MUST_BE_FOLLOWED_BY>
<MUST_FOLLOW LASTSIGN="22" ALT_ERROR="Display this error instead.">7,8</MUST_FOLLOW>
<INITIAL_STATIONS>
<STATION SIGN="1" X="25" Y="10">U1</STATION>
<STATION SIGN="2" X="25" Y="30">U2</STATION>
</INITIAL_STATIONS>
<INITIAL_LINKS>
<LINK FROM="U1" TO="U2">1</LINK>
</INITIAL_LINKS>
<INITIAL_ACCESSORIES>
<ACCESSORY NAME="chair" X="25" Y="30" ROTATION="90">?</ACCESSORY>
</INITIAL_ACCESSORIES>
<SCORESHEET>
<SCORE NAME="Minor Deduction" POINTS="1 - 2">
<LI>Tight leash</LI>
<LI>Dog interfering with handler</LI>
<LI>Poor sits</LI>
<LI>Tight leash</LI>
<LI>Slow, delay, or resistance to respond</LI>
<LI>Touching or ticking a jump, pylon, post or person</LI>
<LI>Out of position</LI>
</SCORE>
</SCORESHEET>
<JUMP_HEIGHTS>
<JUMP_HEIGHT DOG_HEIGHT='less than 10"'>4" high/bar, 8" broad</JUMP_HEIGHT>
<JUMP_HEIGHT DOG_HEIGHT='10" to less than 15"'>8" high/bar, 16" broad</JUMP_HEIGHT>
<JUMP_HEIGHT DOG_HEIGHT='15" to less than 20"'>12" high/bar, 24" broad</JUMP_HEIGHT>
<JUMP_HEIGHT DOG_HEIGHT='20" and over'>16" high/bar, 32" broad</JUMP_HEIGHT>
</JUMP_HEIGHTS>
</COURSE_TYPE>
</COURSE_TYPES>
|
Let's look at these attributes and elements in more detail.
- LEVEL (attribute): The name that defines the level of difficulty of the course.
- TYPE (attribute): Registries may have their own definition of these, but an example is Regular/Non-Regular. (Optional)
- CLASSES: Registries may have their own definition of these, but an example is "A/B". (Optional)
- UNITS: The units that all distance variables are measured in, either Meters, Feet (US), or Yards (US).
If omitted, assume Feet (US).
- MIN/MAX_RING_WIDTH: The minimum or maximum width the ring may be, using the UNITS above.
Assume that maps are drawn in portrait mode, with the HEIGHT being greater than or equal to the WIDTH of the course. (Optional)
- MIN/MAX_RING_HEIGHT: The minimum or maximum height the ring may be. (Optional)
- MIN/MAX_RING_AREA: The minimum or maximum area the ring may be.
This measure may be used in conjunction with or in place of the min/max ring dimensions. (Optional)
- INITIAL_RING_HEIGHT: The recommended height of the ring. (Optional)
- INITIAL_RING_WIDTH: The recommended width of the ring. (Optional)
- SIGNS_ON_MENU: A comma- and dash-separated list of the signs that should be displayed on the program's menu when creating courses at this level.
- Two sign numbers separated by a comma represent two signs.
- Two sign numbers separated by a dash represent a range of signs.
- A list that leads with a dash represents all of the signs from the start, up to the trailing number.
- A list that ends with a dash represnts all of the signs starting with the leading number, all the way to the end of the list.
- If the sign numbers contain a dash, use double-dashes within the sign numbers.
So, a range might be expressed as 0--03-2--50.
This is true within any list of signs present in this specification, but does not apply within the sign definition itself,
where only a single sign is presented, not a list.
- MIN/MAX_STATIONS: The minimum or maximum number of stations on the course, not including any unnumbered and honor stations.
- MIN/MAX_STATIONARY_SIGNS: The minimum or maximum number of stationary signs that may be used on the course.
- MIN_SIGN_SPACING: The recommended or required minimum distance between any two consecutive signs, expressed in the course's DISTANCE_UNITS.
Signs too close should be warned if the TYPE attribute is SOFT or missing, errored if the TYPE attribute is HARD.
- ALLOW_MARRIED_SIGNS: If TRUE, then signs may be marked as Married.
This means that signs may be placed closer than the level's MIN_SIGN_SPACING will not generate an error or warning.
Typically, this represents a LIMIT number of signs that are performed with no heeling between them.
If absent, the default for this feature is FALSE.
If absent, the default for LIMIT is 2.
- USE_POINTS: If present, it defines whether the course uses point values for signs. (optional)
- TOTAL_POINTS: If present, it is a number representing the sum of individual POINT_VALUEs for each sign used on the course. (optional)
- DEFAULT_POINT_VALUE: It is the value to set signs that do not have a POINT_VALUE element. (optional)
- MIN/MAX_POINTS:
If present, it is a number representing the minimum/maximum sum of individual POINT_VALUEs for each sign used on the course. (optional)
- POINT_DOUBLERS: If TRUE, POINTS for individual signs may be doubled.
It should only be evaluated if TOTAL_POINTS, MAX_POUNTS or MIN_POINTS is set. (optional)
- SIDE_SWITCH_SIGN: The NUMBER sign may be paired with another course sign to indicate signs that force the team to switch
the side the dog heels from the normal, left side to the right.
Signs that follow this continue to be executed with the dog on the right side, until encountering one of the signs that automatically
reverses the team's direction. (optional)
- MIN/MAX_SWITCHES: Defines the maximum number of Side Switch signs that may be used on a course. (optional)
- MIN/MAX_SWITCHED_SIDES: Defines the number of signs that may be on the entire course that are executed on the right side. (optional)
- MIN/MAX_STATIONS_FROM_SET: Specifies that the course must contain a certain number of stations come from a particluar set of signs.
In the example above, there must be at least 5 signs from the set 3-37,50-59 on the course.
This element and several others may include an ALT_ERROR attribute.
If included, validation will display the ALT_ERROR text instead of its standard error.
This is another way of inplementing things like side-switch signs.
(optional)
- STATION_FROM_LIST: Specifies that a particular station on the course must contain a sign that comes come from a particluar set of signs.
In the example above, station number 10 must use a sign from the list 8-18,22-42.
(optional)
- MUST_BE_FOLLOWED_BY: Specifies that on this level, the FIRSTSIGN sign must be followed by one of the signs in the comma-separated list.
In the example above, sign 18 must be followed by either sign 2 or sign 3. (Optional)
- MUST_FOLLOW: Specifies that on this level, the LASTSIGN sign must follow one of the signs in the comma-separated list.
In the example above, sign 22 must be followed by either sign 7 or sign 8. (Optional)
- INITIAL_STATIONS: A list of stations that should be placed on the course when creating a new one.
Each station in the list is required to be on the course.
Typically, the list includes at a minumium, two stations representing the Start and Finish signs.
See below.
- INITIAL_LINKS: A list of links that should be placed on the course when creating a new one.
Typically, the list includes at least one link, connecting the Start and Finish signs.
See below.
- INITIAL_ACCESORIES: A set of accessories that must be present for the course, if any.
See below. (optional)
- SCORESHEET: Criteria for deducting points from a dog & handler team.
See below. (optional)
- JUMP_HEIGHTS: Criteria for determining what jump height a dog must be set for.
See below. (optional)
The various combinations of MIN/MAX/INITIAL_RING_WIDTH/HEIGHT may be pre-pended with INDOOR_ or OUTDOOR_,
should the registry desire different ring sizes for different venues.
INITIAL_STATIONS
Signs listed in the INITIAL_STATIONS are reqiured to be on the course.
Programs rendering course maps should place them onto a new course and make it so that they can not be deleted.
<INITIAL_STATIONS>
<STATION SIGN="1" X="25" Y="10">U1</STATION>
<STATION SIGN="2" X="25" Y="30">U2</STATION>
</INITIAL_STATION>
|
In the example above, we are asking to start this level of course with two stations, using sign numbers 1 and 2, which are unnumbered stations 1 and 2.
- SIGN: The NUMBER of the SIGN used at this station.
- X, Y: The offset from the lower-left of the ring, in whatever units are defined for this registry.
Portrait orientation is assumed for layouts.
- ELEMENT TEXT:
Stations with only a number in it are considered Numbered Stations.
Stations leading with a "U" followed by a number are Unnumbered Stations.
(Typically Start and Finish are unnumbered.)
Stations leading with an "H" followed by a number are Honor Stations.
Only Numbered Stations are counted when evaluating the MIN/MAX_STATIONS constraints.
INITIAL_LINKS
LINKs are connections between signs.
<INITIAL_LINKS>
<INITIAL_LINK FROM="U1.nw" TO="U2.sw">1</INITIAL_LINK>
</INITIAL_LINKS>
|
In the example above, we are asking to start each course with a an arrow from the north-west corner of sign 1 to the south-west conrer of sign 2.
- FROM: The STATION, followed by a period, then the corner or side indication of the point where the arrow leaves.
- TO: The STATION, followed by a period, then the corner or side indication of the point where the arrow lands.
ACCESSORIES
Programs should provide several standard accessories: cone, food_bowl, bar_jump, broad_jump, bar_jump.
Additionally, a rule set may define other objects that may be used on their courses, using the ACCESSORIES element.
Within the ACCESSORIES element, one or more ACCESSORY elements must exist.
<ACCESSORIES>
<ACCESSORY>
<NAME>cone</NAME>
</ACCESSORY>
<ACCESSORY>
<NAME>chair</NAME>
<IMAGE_FILENAME>chair.jpg</IMAGE_FILENAME>
<X>35</X>
<Y>5</Y>
<MAX_NUMBER>1</MAX_NUMBER>
</ACCESSORY>
</ACCESSORIES>
|
In the example above, we are asking for an unlimited number of "cone"s be made available for adding to the course and one non-standard "chair" element
be required on the course.
- NAME: A short text description of the item.
- IMAGE_FILENAME: Within the SIGN_LOCATION or ALTERNATE_SIGN_LOCATION location,
the name of the file holding the accessory's image.
Either .jpg or .gif files should be permitted, but objects with non-rectangular silhouetes are best rendered in .gif files.
If this element does not exist, then the NAME must be one of the standard accessories listed above. (optional)
- X, Y: Having the X and Y coordinates defined implies that one of these objects is required.
When present, these values represent the offset from the lower-left of the ring, in whatever units are defined for this registry.
Portrait orientation is assumed for layouts. (optional)
- MAX_NUMBER: The program must provide at most this many of this accessory.
If omitted, the program should not limit the number of these items allowed.
This element may not be present if the X and Y elements are defined (optional)
SCORESHEET
This table describes the point deductions for various infractions a dog and handler team may incur.
Programs will use this information to create custom Score Sheets for judges, instructors and competitors to print and use.
Tablet or other interactive devices may use the information to create scoring apps for judging.
The ScoreSheet may be different for different levels.
Within the SCORESHEET element, one or more SCORE elements must exist.
<SCORESHEET>
<SCORE NAME="Minor Deduction" POINTS="1 - 2">
<LI>Tight leash</LI>
<LI>Dog interfering with handler</LI>
<LI>Poor sits</LI>
<LI>Tight leash</LI>
<LI>Slow, delay, or resistance to respond</LI>
<LI>Touching or ticking a jump, pylon, post or person</LI>
<LI>Out of position</LI>
</SCORE>
<SCORE NAME="Retry Station" POINTS="3" MAX_PER_COURSE="2 MAX_PER_STATION="1>
<LI>Zeros out previous points, deducts 3 points, handler continue with station.
Maximum of two (2) re-tries allowed per run and one (1) per station.</LI>
</SCORE>
</SCORESHEET>
|
The example above describes a single entry into a 3-column table with the NAME in the first column,
the POINTS in the second column and the value of the element in the third column.
- NAME: As defined by the registry.
A NAME of "Retry Station" should be treated special by interactive programs.
- POINTS: May be a single value, a range of values (like 1 - 2), or a list of values (like 1, 3, 5, 7).
If the NAME of this SCORE is "Retry Station", only a single number may be present in this field.
- MAX_PER_COURSE, MAX_PER_STATION: If the NAME of the SCORE is "Retry Station", the SCORE is treated as a retry, where
any points already accrued on the station are wiped out, the valiuue of the POINTS attribute is assigned to the station,
and points may continue to be accured against that station.
These would be used by interactive scoring apps to handle the actions of a button assigned for retries.
- SCORE Value: A set of List Elements (LI) listing infractions that cause the deductions to be applied.
The elements may contain HTML formatting, such as <B> and <I>.
JUMP_HEIGHTS
This table tells the judge and stewards what heights/distances to set jumps for each dog.
The table should only be present on course levels that use jumps.
The jump table is intended to be printed on course maps of levels that use jumps.
Within the JUMP_HEIGHTS element, one or more JUMP_HEIGHT elements must exist.
<JUMP_HEIGHTS>
<JUMP_HEIGHT DOG_HEIGHT='less than 10"'>4" high/bar, 8" broad</JUMP_HEIGHT>
<JUMP_HEIGHT DOG_HEIGHT='10" to less than 15"'>8" high/bar, 16" broad</JUMP_HEIGHT>
<JUMP_HEIGHT DOG_HEIGHT='15" to less than 20"'>12" high/bar, 24" broad</JUMP_HEIGHT>
<JUMP_HEIGHT DOG_HEIGHT='20" and over'>16" high/bar, 32" broad</JUMP_HEIGHT>
</JUMP_HEIGHTS>
|
The example above describes a 2-column table with Dog's Height in the first column and the corresponding Jump Height in the second column.
- DOG_HEIGHT: For dogs with heights (tyically measured at the withers), ...
- JUMP_HEIGHT Value: ...set the jump(s) for this height.
SIGNS
Within the SIGNS element, one or more SIGN elements must exist.
<SIGNS>
<SIGN NUMBER="1">
<NAME>Halt - Sit</NAME>
<STATIONARY>TRUE</STATIONARY>
<MAX_NUMBER TYPE="HARD">1</MAX_NUMBER>
<MIN_SIGN_SPACING TYPE="SOFT" SIDE="BEFORE">10</MIN_SIGN_SPACING>
<POINT_VALUE>5</POINT_VALUE>
<POINT_IN>SW</POINT_IN>
<POINT_OUT>NW</POINT_OUT>
<ANGLE_OUT>0</ANGLE_OUT>
<IMAGE_FILENAME>01_haltsit.jpg</IMAGE_FILENAME>
<SWITCH_SIDES>TRUE</SWITCH_SIDES>
<START>FALSE</START>
<FINISH>FALSE</FINISH>
<HONOR>FALSE</HONOR>
<BONUS>FALSE</BONUS>
<EXERCISE_DESCRIPTION>With the dog heeling to the handler's left, the dog <I>sits</I> as the handler <I>halts</I>.</EXERCISE_DESCRIPTION>
<EXERCISE_DESCRIPTION_AUDIO>01_haltsit.mp3</EXERCISE_DESCRIPTION_AUDIO>
<EXERCISE_DESCRIPTION_VIDEO>01_haltsit.mp4</EXERCISE_DESCRIPTION_VIDEO>
</SIGN>
</SIGNS>
|
Keep in mind that the order of signs is important, since signs may be referred to as ranges.
So, saying signs 1-16 doesn't necessarily mean 16 signs.
For example, if there was a sign 8B that followed sign 8, then referring to a range of signs 1-16 would include 17 signs.
- NUMBER: (attribute) Sign number, but it may include alpha charecters, too (e.g. 8B).
It may not include any dash ("-") or comma (",") characters (since these are used when specifying ranges of signs).
- NAME: A short text description of the exercise.
- STATIONARY: TRUE or FALSE, depending on whether the sign contains a stop in motion.
If omitted, a value of FALSE should be assumed.
- MAX_NUMBER: The maximum number of these signs that may be used.
The TYPE parameter may be either HARD or SOFT.
A HARD value means that, on official courses, the maximum limit must not be exceeded.
A SOFT value means that, on official courses, the maximum limit may be exceeded, but a warning should be issued.
If omitted, the default value is 1 and it is a HARD limit.
- MIN_SIGN_SPACING: The recommended or required minimum distance between this sign and its adjacent signs, expressed in the course's DISTANCE_UNITS.
Signs too close should be warned if the TYPE attribute is SOFT or missing, errored if the TYPE attribute is HARD.
The SIDE parameter may have a value of either BEFORE or AFTER.
- POINT_VALUE: Registries may elect to assign point values to signs, if any of the MIN/MAX/TOTAL_POINTS values are set.
If ommitted, the value of DEFAULT_SIGN_VALUE should be used.
- POINT_IN: When drawing the link from the previous sign, the point on this sign that the arrow should terminate.
Here, we use either 1 or 2 character points on the perimiter of the box.
The values may be either S, SE or SW.
If ommitted, a value of SW should be assumed.
- POINT_OUT: When drawing the link to the next sign, the point on this sign that the arrow should begin.
Here, we use either 1 or 2 character points on the perimiter of the box.
The values may be either N, W, S, E, SE, SW, NE or NW.
If ommitted, a value of NW should be assumed.
- ANGLE_OUT: The direction of the arrow leaving this sign, in degrees, relative to a sign held in readable position.
North is considered 0 degrees, East is 90, South is 180 and West is 270.
Any degree greater than or equal to zero and less than 360 is vaid.
If omitted, a value of zero is assumed.
- IMAGE_FILENAME: Within the SIGN_LOCATION or ALTERNATE_SIGN_LOCATION, the name of the file holding the sign's image.
Either .jpg or .gif files should be permitted.
- SWITCH_SIDES: TRUE, FALSE or OPTIONAL, depending on whether the exercise:
must be performed with the dog heeling on the right (opposite) side of the handler,
may be performed with the dog heeling on the right (opposite) side of the handler, or
may not be performed with the dog heeling on the right (opposite) side of the handler.
If omitted, the default is FALSE. (Optional)
- START: TRUE or FALSE.
If TRUE the sign is a Start sign, or if omitted or FALSE, the sign is not.
If omitted, a value of FALSE is assumed.(Optional)
- FINISH: TRUE or FALSE.
If TRUE the sign is a Finish sign, or if omitted or FALSE, the sign is not.
If omitted, a value of FALSE is assumed.(Optional)
- HONOR: TRUE or FALSE.
If TRUE the sign is an honor sign, or if omitted or FALSE, the sign is not an Honor sign.
Honor signs only follow the course's Finish sign.
Some registries may allow or require one or more honor signs on a course. (Optional)
- BONUS: TRUE or FALSE.
If TRUE the sign is a bonus sign, or if omitted or FALSE, the sign is not a Bonussign.
Bonus signs may only follow the course's Finish sign.
Some registries may allow or require one or more bonus sign on a course. (Optional)
- EXERCISE_DESCRIPTION: Text describing how the exercise is to be peformed.
The text may contain HTML formatting and so, may contain bold and itallicized text, tables, etc. (Optional)
- EXERCISE_DESCRIPTION_AUDIO: Audio file describing how the exercise is to be peformed.
The file should reside in the SIGN_LOCATION or ALTERNATE_SIGN_LOCATION.(Optional)
- EXERCISE_DESCRIPTION_VIDEO: Video file demonstrating how the exercise is to be peformed.
The file should reside in the SIGN_LOCATION or ALTERNATE_SIGN_LOCATION. (Optional)
Note that there is no ANGLE_IN parameter.
The assumption there is that all signs are entered from the south and the sign is oriented such that it is in landscape mode and is readable.
Other items of consideration...
- How to put in a jump height table?
And rather than a table, what if there was a rule like obedience, closest 2" mark to the dog's withers?
- Should we be able to put in a warning message at any level?
If we run across a constraint the software can't support, the warning would remind the user to look at that.
- Custom Judge's Books and Judge's Worksheets?