W3C

List of comments on “Protocol for Web Description Resources (POWDER): Grouping of Resources” (dated 9 July 2007)

Quick access to

There are 6 comments (sorted by their types, and the section they are about).

typo comments

Comment LC-1880: JC 2
Commenter: Jeremy Carroll <jjc@hpl.hp.com> (archived message)
Context: Example 4-6: A relatively complex Resource Set definition e...
Typo
<wdr:excludeHosts>video.example.com</wdr:includeHosts>
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

substantive comments

Comment LC-1910: includeHost constraints
Commenter: Art Barstow <art.barstow@nokia.com> (archived message)
Context: in
Regarding <http://www.w3.org/TR/2007/WD-powder-grouping-20070709/>,
what are the lexical constraints (= conforming syntax) for the values
of the includeHosts property?

Thanks,

Art Barstow
---
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1879: JC 1
Commenter: Jeremy Carroll <jjc@hpl.hp.com> (archived message)
Context: http://joe:mypasswd@www.example.com:1234/example1/example2...
Note the example
http://joe:mypasswd@www.example.com:1234/example1/example2?query=help#fragment

is illegal, in that it does not conform with HTTP spec which does not allow username and password. Also the :mypasswd syntax is strongly discouraged in RFC 3986
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1883: JC 5
Commenter: Jeremy Carroll <jjc@hpl.hp.com> (archived message)
Context: Example 4-7: A complex Resource Set definition using nested...
The SHOULD under 4.7 is way too strong. I see no reason why the
expression in 4.7 cannot be implemented efficiently and be generally
useful; setting the expectation that Powder won't work well is not a
good idea
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

editorial comments

Comment LC-1881: JC 3
Commenter: Jeremy Carroll <jjc@hpl.hp.com> (archived message)
Context: in
includeHosts
You seem to mean that includeHosts with example.org also includes
www.example.org - in a quick skim I didn't see this stated explicitly,
or for example that it does not include example.www.org or whatever; nor
what to do if you only want example.org and not foo.example.org
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1882: JC 4
Commenter: Jeremy Carroll <jjc@hpl.hp.com> (archived message)
Context: Example 4-6: A relatively complex Resource Set definition e...
I found example 4.6 I had to think fairly hard. If this is a standard
idiom then it may be worth spelling it out a bit.

"all resources on example.com except those on video.example.com shot in
widescreen format."
which is
"all resources on example.com except those on video.example.com, and
all resources on example.com except those shot in widescreen format."
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Add a comment.


Developed and maintained by Dominique Hazaël-Massieux (dom@w3.org).
$Id: Overview.php,v 1.46 2013-10-04 08:11:33 dom Exp $
Please send bug reports and request for enhancements to w3t-sys.org