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

Gave this more thought on the weekend, and `site` feels right, but it conflicts with `scope`. They are mutually exclusive.  

That is, if you declare a scope, you can't declare a site. But if you declare a site, it invalidates your scope (because scope can only apply to one origin). 

The might be ok, because it covers the most basic cases:

 1. "I own example.com", and I don't care where you go within my domain ("unbounded"). If you leave my domain, the browser "punishes" you. 
 1. "I own example.com", but I only want my app to be in "/foo": use scope. 
 1. "I own foo.example.com, bar.example.com, *.example.com", and I want to jump from one sub domain to the other. Use: `site`.
 
The highest priority case to solve is the multiple "site" problem, but in a way that is not reckless with cross-origin (i.e., I think we should forget about foo.com and bar.com, and instead only allow *.foo.com via "site"). 

@boyofgreen, @RobDolinMS, @kenchris, @benfrancis, wdyt?  


---
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-214632182