I have been part of the Canadian Warmblood young breeders’ team since I was 16 (now 20). My first competition was held in England, the second in Canada, and for my third I travelled to the beautiful country of Austria. I am not a frequent traveller, so the 12 hours of flying, with a lay-over in Toronto, had me eager to get off the plane and explore this new territory.
I took a train with Maria Ardito and her mother from the Vienna airport to Linz, where we met up with the other team members. We then continued on our way to Stadl Paura where we would be staying during the competition and the excursions.
The opening ceremony consisted of a Parade of the Teams, and with true Canadian pride we marched with our heads and our flags held high. This was followed by the introduction of each team and its members as well as the judges.
Day one
The first day started with a team meeting over breakfast, and a brief last-minute study session in preparation for our theoretical exam that would shortly follow. After the exam we had a 15-minute break to regroup and talk about the exam with our team members before it was time to judge the loose gaits and chute jumping. We were given two pre judged horses, in which the judges shared their scores with all the competitors and their reasoning as to why they scored the way they did. Then we were left to judge five more horses independently. They provided us with a wide range of horses to judge that allowed us to use a full range of scores.
After judging the loose gaits and chute jumping we had a one-hour break for lunch. By this time the temperature had already reached a whopping 32 degrees celsius!
All teams were called to the outdoor arena where we would begin the conformation judging portion of the competition. The arena was split in half, with the juniors placed on one side and the seniors on the other. This process was similar to judging the loose gaits; we were given two pre-judged horses, and then scored three more on our own...
To read the complete article you need to be a subscriber
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
A video-sharing platform for users to upload, view, and share videos across various genres and topics.
Registers a unique ID to keep statistics of what videos from YouTube the user has seen.
Session
DEVICE_INFO
Used to detect if the visitor has accepted the marketing category in the cookie banner. This cookie is necessary for GDPR-compliance of the website.
179 days
LOGIN_INFO
This cookie is used to play YouTube videos embedded on the website.
2 years
VISITOR_PRIVACY_METADATA
Youtube visitor privacy metadata cookie
180 days
GPS
Registers a unique ID on mobile devices to enable tracking based on geographical GPS location.
1 day
VISITOR_INFO1_LIVE
Tries to estimate the users' bandwidth on pages with integrated YouTube videos. Also used for marketing
179 days
PREF
This cookie stores your preferences and other information, in particular preferred language, how many search results you wish to be shown on your page, and whether or not you wish to have Google’s SafeSearch filter turned on.