Hello I hope this isn't too subjective and is technical-enough of a question. I have been researching this for a bit and am not quite clear on an optimally formatted filename for the requirements.
I have an app that is released in the wild starting with a date stamp. It's ISO-8601 but without dashes so isn't very human-readable at a glance. This has led to a project of updating the file name with these key requirements:
- Easily human readable
- Encode arbitrary data in filename
- Primary compatibility: Windows, POSIX, Browser URL (no URI encoding preferably)
Let's get to the formats.
Current:
20170516T083919-09 e20170516T083945+09 l19.654321_-155.123456 n_miPad.txt
Proposed:
2021-12-20T10:52:16.123+0500_e2021-12-20T10:52:16_l19.654321,-155.123456_nmiPad.txt
The file format has a fairly wordy description at the app info page. Basically, there are keys and values in the filename for timestamps, location and text.
The proposed isn't quite ideal: Underscores for spaces and the comma, for example. URL params with key=value& reads well enough to my eye but = and & seem not compatible enough to use.
Thanks for your thoughts.
