- From: Jeni Tennison <jeni@jenitennison.com>
- Date: Sun, 13 Apr 2014 21:38:50 +0100
- To: Alex Russell <slightlyoff@google.com>
- Cc: "www-tag@w3.org List" <www-tag@w3.org>
Hi Alex, From: Alex Russell slightlyoff@google.com Date: 8 April 2014 at 19:25:10 > This is outstanding work. A few questions: > > - I don't see an example that serves the root document out of the > package itself (ala 209). Is there something that describes the "root > document" or advice about where in the package to find the requested > document? It’s mentioned in 2.2.2 Guidelines [1] for use when Installing Web Applications [2]. There’s also a bit of advice about part ordering in Section 3.6.2 [3] which talks about putting a ‘root document’ first, and the example in Section 3.1 on the Package Header [4] illustrates using a config.xml file as the root document. But we could add an example that demonstrates it. > - In section 4.1, example 19 I see: scope="/" . ISTM that the "*" at the > end should be explicit. Also, is it possible to add multiple scopes in a > single declaration using a separator of some sort? Providing a single URL prefix in the scope is, I think, the simplest thing that could possibly work. There are lots of ways we could make it more complicated. I’m not sure what value adding ‘*’ at the end provides? Doesn’t it just make people think they can do '*.png’? Can you explain a bit more about why you think these are worth the extra complexity? Is it to be consistent with something else? Cheers, Jeni [1] http://w3ctag.github.io/packaging-on-the-web/#guidelines-1 [2] http://w3ctag.github.io/packaging-on-the-web/#installing-web-applications [3] http://w3ctag.github.io/packaging-on-the-web/#part-ordering [4] http://w3ctag.github.io/packaging-on-the-web/#package-header -- Jeni Tennison http://www.jenitennison.com/
Received on Sunday, 13 April 2014 20:39:15 UTC