I agree that we should only use curly brackets if and only if there is a namespace in the name. And even then, I'm not sure it's exactly what we want.

IIRC, the FileSystemConnector maps the IDs to the file system paths. That means that an ID of "/foo/bar" will ultimately represent a file or folder named "bar" under a folder named "foo" (in whatever location/directory the connector is using). But per the above change, if "bar" were namespaced with a namespace URI of "http://example.com", then the ID would be (as coded):

    /foo/http://example.combar

or, if we surround the namespace URI with curly braces:

    /foo/{http://example.com}bar

Neither of these is a valid name for a file or folder, are they? Do we have to escape the characters in the namespaces?

The 2.x file system connector expressly avoided using non-default namespaces as [invalid](https://github.com/ModeShape/modeshape/blob/2.x/extensions/modeshape-connector-filesystem/src/main/java/org/modeshape/connector/filesystem/FileSystemWorkspace.java#L753).