Re: [manifest] Link space / "deep linking" (#288)

On Saturday, December 20, 2014, Ben Francis <notifications@github.com>
wrote:

> Why would you want this to be separate from "scope"?
>
No, no, no - I think I failed to communicate properly (again!): scope can
be treated separately from linking (same as we have done with everything
else in the spec - everything is atomic). This is not to say they are
unrelated or won't interact - it's just a separation of concerns.

This is what I meant by treating this separate from scope.


>  Why would you want the manifest to apply to one set of URLs inside the
> origin when already inside an application context, but another set of URLs
> when outside the application context?
>
I don't think I ever said anything about how this would work? In
particular, I'm not advocating anything like the above or below?

> I can maybe see use cases for defining an additional set of URLs outside
> the origin which should stay in the application context if already in it,
> but not two separate sets of URLs inside the origin.
>
> Why should the app not capture navigations for all URLs inside the "scope"?
>

I would ask the exact same thing :) however, it's important to always ask
and for us to discuss.

Seriously Ben, I really value your input but sometimes you jump the gun a
little bit. Please don't make presumptions about positions I, or other
participants, may or may not hold. Everything is up for discussion - or I
might have said something ambiguously (and, sometimes I might be outright
wrong :)).

Anyway, the above are good questions... But it's midnight on Saturday so...
💤

> —
> Reply to this email directly or view it on GitHub
> <https://github.com/w3c/manifest/issues/288#issuecomment-67734122>.
>

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/288#issuecomment-67736328