Hi,
The current sitemap is available through cocoon:/foo Root sitemap is available through cocoon://foo How about making parent sitemaps available through cocoon:../foo, cocoon:../../foo, etc?
Context: I'm currently trying to get Forrest working in samples/forrest, and find myself having to hardcode 'cocoon://samples/forrest/...' refs everywhere, because subsitemaps need access to pipelines in the main forrest sitemap. Having a cocoon:../ syntax would make things much more portable.
I've been historically against this in order to limit about and force better SoC at the URL-space level, but if you really found a need for it, I'd be happy to change my vote from -1 to +0.
Stefano.
