This will be necessary on implementations where some files don't have character-string names.
Could someone clarify this?
See the description of file operations. The point here is that some file names aren't valid character strings according to any specific encoding, since file systems don't carry an encoding about with them. We make provision for this by allowing implementations to provide file specs that don't include path. The idea here is to permit that with include(-ci) as well.
We voted yes (assuming we keep file-spec lists).