Edit comment LC-1883 for Protocol for Web Description Resources (POWDER) Working Group

Quick access to LC-1879 LC-1880 LC-1881 LC-1882 LC-1883 LC-1910

Comment LC-1883

Comment Shortname:

Commenter: Jeremy Carroll <jjc@hpl.hp.com>

Message-id:

Section of the document concerned:

[Free text description]Document as a wholeProtocol for Web Description Resources (POWDER): Grouping... Protocol for Web Description Resources (POWDER): Grouping of Resources Abstract Status of this document Table of Contents 1 Introduction (Informative) 1.1 Design Goals and Constraints 1.2 Outline Methodology 2 Grouping by address 2.1 Grouping by IRI/URI component http://joe:mypasswd@www.example.com:1234/example1/example2... Table 1: Mapping between regular expression variables and U... Table 2: The RDF Properties used to define resource sets by... Table 2: The RDF Properties used to define resource sets by... Example 2-1: A Resource Set definition using three RDF prop... 2.1.1 Resource Set Definitions Referring to Ports Example 2-2: A Resource Set definition using port lists and... † 2.1.2 Resource Set Definitions Referring to Paths and/or Query Strings ‡ 2.1.3 IRI/URI Canonicalization Table 3: Examples of canonicalized IRIs and URIs Input IR... Table 3: Examples of canonicalized IRIs and URIs 2.1.4 Data encoding 2.2 Grouping by Regular Expression: The includeUriPattern and excludeUriPattern Properties Example 2-3: Set definition by regular expression (not incl... Example 2-4: Set definition by regular expression, includin... 2.2.1 Safe Use of includeUriPattern Example 2-5: An example of a bad set definition by regular... Example 2-6: A second example of a bad set definition by re... Example 2-7: An example of a correct set definition by regu... Example 2-8: A re-write of Example 2-7 without using a regu... 2.3 Grouping by IP Address Example 2-9: A Resource Set definition using the includeIPs... Example 2-10: A Resource Set definition using the includeIp... 2.3.1 Safe Usage of the includeIpRanges Property Example 2-11: Resource Set definition across several IP add... Example 2-12: Erroneous Resource Set definition across seve... 2.4 Enumerating Elements of a Resource Set: the includeResources and excludeResources properties Example 2-13 Resource Set definition using excludeResources... Example 2-14 Erroneous Resource Set definition using includ... Example 2-15 Correct Resource Set definition using includeR... 2.5 Redirection: the includeRedirection property Example 2-16 Resource Set definition using includeRedirecti... 3 Grouping by Resource Property 3.1 Basic Resource Set Definition by Resource Property: the includeConditional and excludeConditional properties Example 3-1: Basic Resource Set definition by resource prop... 3.2 Resource Set Definition by Property Look Up Example 3-2: Resource Set definition with property look up.... Example 3-3: Resource Set definition with property look up... 4 Conjunction and disjunction 4.1 Combining Definitions Within a Resource Set Example 4-1: Resource Set definition with a two element lis... Example 4-2: An invalid Resource Set definition in which a... Example 4-3: Resource Set definition with two RDF propertie... Example 4-4: Resource Set definition with two RDF propertie... 4.2 Combining Multiple Resource Sets Example 4-5: A Resource Set formed from a union of two sub... Example 4-6: A relatively complex Resource Set definition e... Example 4-7: A complex Resource Set definition using nested... Example 4-8: A more efficient way of expressing the same Re... 5 Logical Inconsistency Example 5-1 A simple Resource Set definition anticipated as... Example 5-2 A repeat of Example 5-1 with an additional line... Example 5-3: A corrected version of Example 5-2 <wdr:Resou... 6 Extension Mechanism 6.1 Extension Example 1: ISAN Example 6-1: A Resource Set Definition using an ISAN number... 6.2 Extension Example 2: Custom URL Patterns Example 6-2 A Resource Set definition using a custom URL pa... 7 References Normative References [URIS] [IRIS] [UTF-8] [PERL] [CIDR] [HTTPCODE] [HTTPRDF] [OWLSO] Sources [WDR] [VOC] [Rabin] [WCL-XG] [PUC] [URISpace] [SPARQL] [SOAP] [ROBOTS] [ISAN1] [ISAN2] [Google] 8 Acknowledgments
or

Refinement of the section concerned:

Status:

open proposal pending resolved_yes resolved_no resolved_partial other assigned to Nobody

Type: substantive editorial typo question general comment undefined

Comment:

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

Related issues: (space separated ids)

WG Notes:

Resolution:

(Please make sure the resolution is adapted for public consumption)