On Wed, Jan 21, 2015 at 10:38 AM, Martin Thomson <martin.thom...@gmail.com> wrote:
> On 21 January 2015 at 10:28, Ilya Grigorik <igrigo...@google.com> wrote: > > Can you elaborate on what the missing components are? > > The ability to take a meta-resource and treat it as a single unit. > Packaging, basically. I believe this is still satisfied. The browser (and/or any other tool) fetches a single resource, which in turn triggers some cascade of background actions that fetch necessary subresources. Perhaps we just need a different name to describe this.. In effect, we're describing something like NPM's package.json [1] or Ruby's gemspec [2]. Except, I'm not even sure we need to define a new format for this, since an HTML page linked via <link rel=import> can deliver everything we need. ig [1] http://browsenpm.org/package.json [2] http://guides.rubygems.org/specification-reference/
