I would like any suggestions or advice in hunting down a useful file system structure definition language. That may be a misleading term so allow me to elaborate:

Currently I'm using a proprietary language built where I work with it's own parsing system. The language needs to be readable by non-tech types so that when a project starts and we discuss the desired file system structure they can scan over it easily. For example:

|-- reference: ->ref, lock, sync=everyDay
    |-- initialPlan
    # This will be for ops
    |-- restore: lock=datasys
    |-- planref: lock
        |-- <app_code>
            |-- reference
            |-- <app>: lock, namerule=[a-z]{2}\d{3}[a-z]?
                |-- reference
                |-- <app_section>: lock, namerule=[a-z]{2}\d{3}[a-z]?_\d{4}[a-z]?
                    |-- reference
    |-- ux

Would generate a file system structure where the parts within the angled brackets differ by codenames for different sections/apps we are working on and following the colons we define "rules" for access and naming conventions of the folders.

If you wanted to access the folder reference under the app_code folder it would follow this path:

reference/restore/planref/app_code/reference/

If any of that doesn't make sense please ask. The question is - is there an existing standard that can be used for the same task? We're using our own parser and it isn't the most robust of things, so an 'industry standard' with a variety of parsers, syntax hilighting schemes and/or extensions by the community who uses it would be most welcome. The o/s is Linux based.