I'm not sure which file naming convention is right for you, but from experience I know that my storage grows and my needs for accumulated data keep changing over time.Changing the folder structure or naming conventions to meet new needs can be very cumbersome, but if the structure and conventions are properly managed, it's a simple task. So, I think it's more important to manage and maintain them so that they can be converted at any time than it is to find the best naming convention, which is one of the reasons I created the file name system.

Thanks for the feedback! I understand that you are pointing out that no can be interpreted as false. I'll have to update the spec to require ‘string’ for folder and file names.

There's no big reason why i'm using yaml. Originally I was trying to create a very simple spec with just simple text rules, like you said. I needed a way to distinguish whether <year>-<month>-<day>-<hour>-<minutes>-<seconds>.txt was a file or a folder, and for folders I used ‘:’ for this.

I'm not interested in the semantic structure of YAML, I chose it because it's an easy format for users to read and write. I'll give more thought to whether or not to use YAML.

Oops. Fixed the title.