**Status:** open — enhancement proposal (reverses the current by-design refusal, see the resolved `file+zip://` work). Forcing a format/container on a local path requires the full chained scheme `<transport>+<token>://` even when the transport is trivially the local filesystem: ``` create("file+xml:///tmp/catalog.renamed") -> XmlBaseNode (OK) create("xml:///tmp/catalog.renamed") -> DrbFactoryException create("file+zip:///tmp/archive.renamed") -> DrbBaseZipNode (OK) create("zip:///tmp/archive.renamed") -> DrbFactoryException ``` **Proposal:** when a URL scheme is not a known PROTOCOL topic but matches the factory of a known FORMATTING/CONTAINER topic (`xml`, `zip`, `image`, …), rewrite it as `file+<token>://`. A genuinely unknown scheme (`ftp://`) must keep raising. "No transport ⇒ local file, force any format." **Trade-off:** blurs the clean transport/format separation; define `//` authority semantics for relative paths.