Changelog

Updates to the NautiX interface are published on this page.

Version 1.4

20.05.2026 - 2a6a9f1

Media Validation

New option for less strict validation of image checksums: “non-strict” allows MD5 checksums that do not match the checksum of the file actually delivered:

<media validation="non-strict">
<images>
<image type="image/jpeg" caption="Boat on sea" md5="9810a142dc0c92d601a4dd916d881863">
https://d3tvazj243kxep.cloudfront.net/fotos/9CzU564F/11516-large.jpg
</image>

Existing feeds with version prior to 1.4 are handled as validation=”strict” by default.

For further details see the Documentation. (5 Images & Documents)

Additional Sail Attributes

We added more sails:

  • storm_jib

  • code_zero

Plus standing rig items:

  • shrouds

  • backstay

  • forestay

For all sail and rig items, it is now possible to specify both the material and the year.

<rig_sails>
   <main_sail area="40" unit="m2" material="dyneema" year="2025" furling="boom" battened="true">Dimension Polyant</main_sail>
   <storm_jib>true OR additional text</storm_jib>
   <code_zero area="60" unit="m2" material="dyneema" year="2024">North Sails</code_zero>
   <shrouds material="steel_wire" year="2017">true OR additional text</shrouds>
   <backstay material="steel_wire" year="2009">true OR additional text</backstay>
   <forestay material="steel_wire" year="2009">true OR additional text</forestay>
</rig_sails>

New Cover Types

In the <covers> section we added:

  • main_sail_cover

  • head_sail_cover

  • wheel_cover

NautiX Push

12.08.2025

NautiX Push is being introduced to speed up updates. All details about the concept can be found here.

Version 1.3

07.08.2024 - 0dae69f

Better differentiation of internal_code: 

<internal_code>Boat Nr B-65</internal_code>
<internal_code_public>Boat Nr B-65</internal_code_public>
<internal_code_private>Current Owner: John Doe</internal_code_private>

This improves the definition of whether the internal code may be shared with the public or whether it is only intended for internal use by the broker.

We also removed no_engines from the XSD and sample XML. There is no longer any use for this field. Whether and how many engines are available can be defined completely using number_of_engines:

  • one or more engines: e.g. number_of_engines=2

  • no engine: number_of_engines=0

  • engine information not available: completely leave away the node number_of_engines


Version 1.2

20.02.2024 - ad8ea0b

A new field model year has been introduced plus small improvements for sale class and sale status.

model year

<model_year>2018</model_year>
<year_built>2017</year_built>
<year_launched>2018</year_launched>
<last_refit>2020</last_refit>

sale class

We added the value “not-applicable” to sale class (used / new / etc). It should be only used for moorings.

<sale_class>not-applicable</sale_class>

sale status

There have been questions about the status under-offer: it is the equivalent for “sale pending, real offer from prospective buyer, boat is under offer etc.”

<sale_status>under-offer</sale_status>


Version 1.1

10.03.2022 - 11e0c3b

We made two small changes on the XML/XSD. Both changes are backward compatible and do not require immediate updates on current implementations.

range and consumption

We combined range and consumption with cruising and max speed in order to define those measures for each “speed level”:

v1

<cruising_speed unit="kn">8</cruising_speed>
<max_speed unit="kn">15</max_speed>
<cruising_consumption unit="lh">21</cruising_consumption>
<max_consumption unit="lh">35</max_consumption> <range unit="nm">100</range>

v1.1

<cruising_speed unit="kn" range="100" range_unit="nm" fuel_consumption="21" consumption_unit="lh">8</cruising_speed>
<max_speed unit="kn" range="30" range_unit="nm" fuel_consumption="35" consumption_unit="lh">15</max_speed>

engine count

The definition of the engine count with the number of <engine> nodes is not self explanatory enough. Thus it has led to some incorrect implementations and the engine count has not been correctly exported. We improved this with v1.1 and added a specific node to prevent this issue:

v1.1

<boat_data>
    <drive>
        <number_of_engines>2</number_of_engines>
    </drive>
</boat_data>