Arrived on the famous Easter Island (Chile) on May 20th, the R4WO scientific teams have proceeded onto the first scientific surveys in the South Pacific Garbage Patch on the coasts of the island devastated by plastic waste
Team Brunel (Bouwe Bekking/NED) completed a triumphant Leg 7 early on Wednesday to bolster their hopes of finishing with a podium place in the Volvo Ocean Race and also keep alive the possibility of overall victory.
Team Brunel were on Tuesday battling towards possible victory in Lisbon on Leg 7, just over two weeks after skipper Bouwe Bekking (NED) had declared that he feared their challenge for the overall Volvo Ocean Race trophy was likely to fall short.
The ISAF XRR message service allows instant
integration of results management systems with the ISAF results
database. Use of the service allows for rapid publication
of race and event standings so that regatta management teams can
automate some of their office procedures.
Overall, the ISAF XRR service allows for these
Upload of fleet racing results
Upload of match racing results
Upload of team racing results (with variable crew lists)
Download of sailor biography information (including
Download of regatta information (with divisions)
In order to make use of the ISAF XRR data
service you will require regatta management software that is XRR
enabled, to see a list of the available packages please follow the
link to "Software Packages" above.
Alternatively, the following section covers the technical detail of
integrating 3rd party software with the ISAF XRR data
Technical Description (Upload)
All XRR communications with ISAF are conducted
through the URL:
A connection is made by the client software
using a standard HTTP connection - specific to the framework libraries
that support your chosen programming language.
All communication objects should be set up to
use UTF-8 encoding and the document content passed to our data-feed
URL using the HTTP POST mechanism. The following files
contain examples of this implemented in a number of languages:
In the instance that the uploaded document
content is malformed or has internal referential problems the HTTP
status code of the response will be 404 and the content of the
response will list each of the problems on a line by line basis
(separated by new-lines), if the upload is valid the response code
will be 200.
The import process works on a 3 stage basis: schema
reference validation, persistence.
Schema validation: The initial
stage ensures that the document content meets the structural
constraints of the chosen version of the XRR schema, this is done by
using the standard XML DOM validation library facilities available in
most programming languages.
Internal reference validation:
This stage ensures that all of the unique keys necessary to link the
various individual elements are in place. It also ensures that they
haven't been used in multiplicity and that all IDs required for
referencing the external (ISAF) unique references are in place and
Persistence: This stage takes
on three forms, depending on agreement between ISAF and the document
source. An Event element may or may not have the attribute IFUploadCode populated, this attribute is described in technical specification v1.3.1. Assuming the document content passes the previous integrity checks the valid combinations are as follows:
An uploaded document with the word TESTING populated into the IFUploadCode attribute will have the content validated and will report back on errors, if any, without initiating a full import. This method has been provided to allow testing of the service.
An uploaded document with nothing populated into the IFUploadCode attribute will be placed in a queue pending approval by the Competitions management
team at the ISAF secretariat. They then have the facility to approve, amend or reject each submitted document.
In the instance that an event is provided in advance, by ISAF, with a pass-code for populating the IFUploadCode attribute this will allow a results document to import directly into the ISAF results database on receipt.