This week I’ve completed the last of the ACES granulation strategy, incorporating the feedback from the community on our last call. I also wrote an initial file granulation strategy description and need some opinions on how to specify restrictions for the file path itself.
Just as a stub, I set the restriction for a file path to be alphanumeric (A-Z, a-z, 0-9), allowing also dashes, underscores, and spaces (because these have become so ingrained in file naming patterns that it’d hinder adoption to leave it out). But I recognize how myopic this restriction is, given that the world is vastly larger than the 52 characters of the Roman alphabet. I’d like to hear from you all about what are reasonable recommendations to make — should we say that all characters from Unicode are allowed, except for control characters? Or is that too broad?
Tomorrow I’ll also go over the length and path separator character specifications that I wrote up; I’m interested in your thoughts there as well.
What was supposed to be a simple task has, predictably, turned out to be a bit larger than I’d hoped, but thankfully it’s limited in scope.
If you would like to join us, please feel free to do so at the usual time (9:00am US Central) and place (Teams)!