ISO 8601 is hard to read even after reading documentation

[bidoubiwa]

Introduction

For the moment a typical duration returned by MeiliSearch looks like this:

      duration: 'PT0.006734800S',

Format choice

The format is hard to read. I have a hard time understanding what I'm reading above: PT0.006734800SIs it 0.006734800 seconds ?
The Wikipedia page barely help me understand the format as well. The only passage I found on the subject is the following :

To resolve ambiguity, "P1M" is a one-month duration and "PT1M" is a one-minute duration (note the time designator, T, that precedes the time value). The smallest value used may also have a decimal fraction,[35] as in "P0.5Y" to indicate half a year. This decimal fraction may be specified with either a comma or a full stop, as in "P0,5Y" or "P0.5Y". The standard does not prohibit date and time values in a duration representation from exceeding their "carry over points" except as noted below. Thus, "PT36H" could be used as well as "P1DT12H" for representing the same duration. But keep in mind that "PT36H" is not the same as "P1DT12H" when switching from or to Daylight saving time.

Seconds alternative

The only reasons (for me at least) that you need duration is either looking at it with human eyes, or showcasing it in some way either on terminal or in your app.

Using seconds both are made easy. While using ISO 8601 makes it hard.

Implementation

I did not find a standard library to transform ISO 8601 into seconds. I did find standard libraries to transform ISO 8601 into date time but this is not what we want since we only want to extract seconds.

This requires that in every language I checked the user has to parse the string to extract the seconds value

Precision

PT0.006734800S

The numbers of digit after the coma seems a bit overkill and makes it even harder to read. I suggest we remove the trailing 0 to lighten the number.