Actually, if I'm not misunderstaning, @javierbertoli  is not suggesting to remove the prepending type, but just avoiding to use the string  config for "some" files prefixes and use dir instead of file for directories, which makes sense.

For me +1 for an approach like the one summed up by Javier:
```
config_file_* # for main config file
some_file_* # for other files 
config_dir_* # For main config dir
some_dir_* # For other dirs
```
which actually looks quite nextgen, but with the difference that, for coherency, seds and so on:
``` 
NO template - YES config_template
NO source - YES config_source
```
And for the namevar
```
config_path
```

Prepending the type is plainly necessary IMHO, as we have to refer to different types from a single interface and that gives clear indication of where the parameter is going to be applied.
We can definitively decide that config_ is the prefix for the main file, ad other files have a descriptive naming (without the need of adding a 'config' string).

We *could* introduce the exception that for file resources we don't specify the type (so config_* or some_* instead of config_file_*) but that would be an exception and it would introduce potential confusion on params names.
We could also decide that this could apply only to the main config, so config_* and some_file_* but that's another exception to the general pattern.