Unico Hommes wrote:
Wild idea: context:/ identifies the current context, context:// identifies the root sitemap? Like in cocoon: protocol?
Great idea (again!). Currently, the "context:" protocol requires the double-slash and links to the root sitemap, so we can implement this additional behaviour with a single slash with no compatibility break. And the similarity with "cocoon:" makes it easy to understand.
This makes me think that "cocoon:" must also be be relative to the "current" sitemap, and not that handling the request.
BAD IDEA.
Please, you are adding contracts to the URL spec that aren't there. Instead I would highly encourage you to provide a way to set the base URL where relative URLs would be resolved to.
Work *with* the contract instead of extending it in non-intuitive ways.
See my rant in another email.
