Lists Home |
Date Index |
I've written a plugin to IBM's open source Eclipse IDE  that includes
support for entity resolution using XML Catalog. I'm wrestling with a design
issue and would welcome the thoughts of others on this.
Eclipse provides a sort of virtual filesystem within its workspace. The
workspace represents the filesystem root, with each project being an
immediate child folder of the workspace (regardless of where they actually
lie in the filesystem). For example, a file called "bar" in the project
"foo" would have the absolute path of "/foo/bar", even though the actual
path in the filesystem might look something like
"c:\eclipse\projects\foo\bar" (just as a hypothetical example). I'd like to
use URIs whose paths match the view presented to the user within the
What's the best way to do this? Would representing the above file as
"file:///foo/bar" be abusing the "file" URI scheme since it doesn't match
the actual file path? Would it be better to use a custom URI scheme (e.g.
"workspace://foo/bar") so that it is more evident that the URI cannot be
used directly but must be resolved first (e.g. via "rewriteURI" entries for
each project in an XML Catalog)? I'm usually uncomfortable with creating
proprietary URI schemes, but maybe this approach fits here. Any other
approaches that might fit, here?