Johan Corveleyn wrote on Fri, May 05, 2017 at 11:09:33 +0200:
> Come to think of it: if reserving a namespace for future use, and
> "/iota" doesn't exist yet, can't you just block the name "/iota"
> without glob pattern? It doesn't exist anyway, so if you'd like to
> create some subtree under it, you first have to create /iota, right?
> Now, in the end, I don't want this issue to be blocked forever :-). I
> think in practice the confusion will be minimal, because either the
> administrator knows what kind of item "iota" is (a file or a
> directory), or the item doesn't exist yet and he'll be doing the
> "reserve namespace" use case. So for me it's fine if "/iota/**"
> effectively matches both the "directory iota and its subtree" and "the
> file iota". As long as it's documented that way then :-).
> If Daniel insists, I'm fine with using "/***" as well, if we want to
> have this special "reserve namespace" meaning.
I hope I'm not coming across as "insisting", Johan. I certainly didn't
Regarding "reserve a namespace", I agree with you that "[/trunk/iota]
*=" appears to serve that purpose. Let's wait to hear from Doug.
Received on 2017-05-06 03:33:53 CEST