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

Quick access to LC-2112 LC-2116 LC-2119 LC-2126 LC-2135 LC-2136 LC-2137 LC-2138 LC-2139 LC-2140 LC-2141 LC-2142 LC-2143 LC-2144 LC-2145 LC-2146 LC-2147 LC-2148 LC-2149 LC-2150 LC-2151 LC-2152 LC-2153 LC-2154 LC-2155 LC-2156 LC-2157 LC-2158

Comment LC-2149

Comment Shortname:

Commenter: Michael Schneider <schneid@fzi.de>

Message-id:

Section of the document concerned:

[Free text description]Document as a wholeProtocol for Web Description Resources (POWDER): Formal Se... Abstract Status of this document This document and the Description Resources [DR] document bo... Table of Contents 1 Introduction The GRDDL transform from POWDER to POWDER-BASE to POWDER-S i... 1.1 Namespaces, Terminology and Conventions Used in This Document. Table 1: Prefixes and Namespaces used in this document Pre... 2 Attribution Element Semantics 2.1 POWDER Attribution Semantics 2.2 POWDER-S Attribution Semantics As a shortcut designed to avoid the automatic need to declar... Example 2-1: The Generic Semantics of the attribution Eleme... As noted above, some elements within the POWDER namespace th... issuedby SHOULD Example 2-2: The Semantics of the POWDER-Specific Child Ele... 3 Description Resource Semantics Example 3-1: A Generic Example of A Descriptor Set and Tag... The ex:finish element specifies that the ex:finish relation... Example 3-2 The POWDER-S Encoding of Example 3-1 [RDF/XML]... Example 3-3: A DR with Multiple IRI Sets in its Scope [XML]... Example 3-4: The POWDER-S encoding of Example 3-3 [RDF/XML]... Examples 3-3 and 3-4 also show that if a descriptorset eleme... 3.1 Multiple Description Resources in a Single POWDER Document Example 3-5: A POWDER Document Containing Multiple DRs [XML... Example 3-6: The POWDER-S Encoding of Example 3-5 [RDF/XML]... Example 3-7: An Ordered List of DRs [XML] 1 <ol> 2... Example 3-8: The POWDER-S Encoding of Example 3-7 [RDF/XML]... 3.2 Descriptor Set Semantics 3.2.1 Descriptor Sets expressed as RDF Properties and Values In the simplest case, a descriptor set contains RDF properti... Example 3-9: A Descriptor Set Containing an RDF Property wi... These simple cases will normally be what is required for Des... Example 3-10: A Descriptor Set Containing a Blank Node POWD... Example 3-11: A Descriptor Set Containing an Identified Nod... 3.2.2 Asserting the rdf:type Relationship Example 3-12: A Descriptor Set Asserting that IRIs within i... If used directly, the rdf:type property will be treated in t... 3.2.3 Referring to External Descriptor Sets Example 3-13: A Descriptor Set Referring to one in an Exter... 3.2.4 Further Descriptors 3.3 Tag Set Semantics The semantics of the (free text) tags are similar to those f... Example 3-14: A Tag Set. POWDER [XML] 1 <tagset> 2... 4 IRI Set Semantics 4.1 White Space and List Pre-Processing 4.2 POWDER and POWDER-BASE IRI Set Semantics Example 4-1: The POWDER and POWDER-BASE Encoding of an Exam... Table 3. Template regular expressions for IRI constraints t... Example 4-2: The POWDER and POWDER-BASE Encoding of an Exam... Example 4-3: The POWDER and POWDER-BASE Encoding of an Exam... 4.3 POWDER-S IRI Set Semantics wdrs:matchesregex rdf:type owl:DatatypeProperty . wdrs:... The following example takes a complete example POWDER docume... Example 4-4: The Full Transformation of an Example from POW... Example 4-5: The POWDER, POWDER-BASE and POWDER-S Encoding... 4.4 Direct Descriptions In POWDER-S, such descriptions are translated into classes,... Example 4-6: The Semantics of Direct Description Elements P... 4.5 Semantics of abouthosts and aboutregex This process is demonstrated by Example 4.7. Notice that in... Example 4-7: The Semantics of abouthosts POWDER Document [X... As discussed in Section 3.2.3, a DR MAY refer to descriptors... 4.6 POWDER-BASE IRI Set Semantics in OWL 2 (Informative) hasIRI rdf:type owl:DatatypeProperty . hasIRI rdf:type owl:... Example 4-8: The POWDER-S Encoding of Example 4-4 With User... 5 Acknowledgements 6 References [WEBARCH] [GRDDL] [XSLT] [DR] [GROUP] [USECASES] [PRIMER] [TESTS] [WDR] [WDRS] [WDRD] [PDR-GRDDL] [XSD2] [N3] [DC] [FOAF [W3C DTF] [OWL] [OWL2] [RDF-SEMANTICS] [XQXP] [XSLT2] [Rabin] [RFC2119] 7 Change Log 7.1 Changes since First Public Working Draft
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

Resolution status:

Response drafted Resolution implemented Reply sent to commenter

Response status:

No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):

Comment:

I don't follow this argumentation. I don't see that the bNode leads to any problems when the descriptor set is defined
independent on any DR.
Maybe there is a misunderstanding in what the above example means. The existential variable isn't about resources
from a DR, but about the values of a descriptor for such resources. The construct above tells the following: If the
above descriptorset is defined for some DR, and r is a resource in that DR (i.e. if r is in the IRI-set defined by that DR),
then there /exists/ some x, being an instance of class Wood, where x has a shiny finish and is made of cedar, and the
following relationship holds: 'r ex:material x'. the existential variable x appears on the /right/ hand side of the
relationship!
If this was a misunderstanding, then I suggest to simply remove the whole paragraph.

Related issues: (space separated ids)

WG Notes: Paragraph removed as a response to LC-2126, as the WG has resolved to drop this feature-at-risk.

Resolution:

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