Re: [w3c/manifest] Allow for multiple scopes (#449)

> That said, I think it is confusing to have something replace something else and I am not sure people will get that. We don't want to end up with something like density again here. Also, people might want to scope each of these sites.

Scoping per site would be messy - we should try to avoid that (below).  

> Why not just allow scope to be an array, but that any entry must be eTLD+1+scope?

Yeah, something like that might work.... but it's still super messy. Like: 

```JSON
{
  scope: [
    "foo.com/bar"
   ]
}
```

Means all of these are in scope: 
 * sub.foo.com/bar, 
 * dub.foo.com/barista
 * and so on... 

So then you get a mess of:

```JSON
{
  scope: [
    "foo.com/bar",
    "foo.com/app",
   ]
}
```

Where now everything matching anything `*.foo.com/bar*` and `*.foo.com/app*` is scope and it's hard to reason about.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/449#issuecomment-215011750