Edit comment LC-1572 for Device Independence Working Group

Quick access to LC-1563 LC-1565 LC-1566 LC-1567 LC-1568 LC-1569 LC-1570 LC-1571 LC-1572 LC-1573 LC-1574 LC-1575 LC-1777

Comment LC-1572

Comment Shortname:

Commenter: Al Gilman <Alfred.S.Gilman@IEEE.org>

Message-id:

Section of the document concerned:

[Free text description]Document as a wholeAbstract Status of this Document Table of Contents 1 Introduction 1.1 Towards a Device Independent Markup Language Profile 1.2 Reading the Specification 1.2.1 Conformance Information for DISelect 1.2.1.1 Normative and Informative Parts 1.2.1.2 Normative Language for Conformance Requirements 1.2.1.3 DISelect Profiles 1.2.1.4 Document Conformance 1.2.1.5 DISelect Implementation Conformance 1.3 Documentation Conventions 2 Document Structure 2.1 The Namespaces 2.2 The Selection Module 3 Processing Model 3.1 Events Overview 3.2 Events in Response to Errors Exception Error 3.2.1 The diselect-invalid-type-error Event 3.2.2 The diselect-redeclaration-error Event 3.2.3 The diselect-declaration-exception Event 3.2.4 The diselect-compute-exception Event 4 Attributes for Conditional Processing 4.1 Overview 4.2 The expr Attribute 4.3 The selid and selidname Attributes 4.3.1 Generated Host Language Identifiers 4.4 The functions Attribute 4.5 Using the Attributes 5 Elements for Conditional Processing 5.1 Overview 5.2 Conditional Processing 5.2.1 The if Element 5.2.1.1 Attributes 5.2.2 The select Element 5.2.2.1 Attributes 5.2.2.2 Processing 5.2.3 The when Element 5.2.3.1 Attributes 5.2.4 The otherwise Element 5.2.4.1 Attributes 5.3 Using the Elements 6 Variables 6.1 The variable Element 6.1.1 Attributes 6.1.2 Declaring a Variable 6.1.3 Referencing an Existing Variable Using the variable Element 6.1.4 References to Variables in XPath Expressions 6.1.5 Scope of Variables and Nesting 6.1.6 Types string number boolean 6.1.6.1 Type Conversion 6.2 The value Element 6.2.1 Attributes 6.3 Using Variables 7 Attribute Value Templates 7.1 Using Attribute Value Templates 8 XPath Expressions 8.1 Identifying Profiles and Versions 8.1.1 The getProfileName function 8.1.1.1 Prototype 8.1.1.2 Function 8.1.2 The sel:getVersion function 8.1.2.1 Prototype 8.1.2.2 Function 8.2 DISelect Basic XPath Support 8.2.1 Accessing the Delivery Context using the XPath Subset 8.2.2 Formal Grammar for the DISelect Basic Subset 8.3 DISelect Full XPath Support 8.3.1 Path-Based Access to the Delivery Context 8.3.2 Path-Based Access to the Host Document 8.4 Extension Functions A Schema B References B.1 Normative References B.2 Informative References C Changelog (Non-Normative) C.1 Changes in this Version D Acknowledgements (Non-Normative)
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:

References:

- Issues:
http://www.w3.org/TR/2006/WD-cselection-20061010/issues.html#Gilman-14

- Current 2nd Last Call draft:
http://www.w3.org/TR/2006/WD-cselection-20061010/#id2269811

Thank you for agreeing with my earlier comments. I think an
editorial glitch remains, however.

The wording in the current draft

<quote
cite="http://www.w3.org/TR/2006/WD-cselection-20061010/#id2269892">
>This mandatory attribute defines an expression used in determining
>whether or not the descendents of the element appear in the result
>infoset. If the expression evaluates to a boolean value of true, the
>descendents of the if element appear in the result infoset. If the
>expression evaluates to a value of false, the descendents of the if
>element are omitted from the result infoset.
</quote>

does not seem to make it clear whether the 'expr' attribute itself
appears in the results
infoset. My impression is that you meant the answer to be 'no.' But
it didn't get into
this paragraph in the specification text.

Al


At 5:07 PM +0000 11/17/05, Roland Merrick wrote:
>Greetings Al, my apologies, should have sent this to you and not
>just to diselect-editors list.
>
>Regards, Roland
>Tel/Fax: +44 (0)1926-465440
>Mobile: +44 (0)77 2520-0620
>----- Forwarded by Roland Merrick/UK/IBM on 17/11/2005 17:01 -----
>Roland Merrick/UK/IBM
>
>17/11/2005 14:44
>To
>public-diselect-editors@w3.org
>cc
>w3c-di-wg@w3.org
>Subject
>Gilman-14
>
>
>
>
>Greetings Al, thanks for your comments on the content selection last
>call [1]. As part of this you include "Content of
><http://www.w3.org/TR/2005/WD-cselection-20050502/#sec-sel-if-element>the
>'if' Element" which starts with: "The specification prose says that
>an 'if' condition "allows control to be applied to "an arbitrary
>fragment" of the host language."
>
>The DIWG assigned this comment the identifier Gilman-14.
>
>This mail documents DIWG's response to your comments.
>
>DIWG Response
>=============
>
>We agree that this is an inappropriate use of the term arbitrary and
>implies more than we had intended. We will use more appropriate
>wording such as "The if element allows control to be applied to a
>wider range of xml document fragments than does the expr attribute
>alone."
>
>[1]
>http://lists.w3.org/Archives/Public/public-diselect-editors/2005AprJun/0012.html
>
>Regards, Roland

Related issues: (space separated ids)

WG Notes: We do need to clarify the wording in the descriptions of individual parts of the markup. This qustion is covered in the processing model section.

Resolution: Update the description to make it clear that the elements and attributes do not themselves appear in the result infoset. Add links back to the processing model section. 2007-01-28 changes made Resolution communicated in http://lists.w3.org/Archives/Public/public-diselect-editors/2007JanMar/0011.html Al accepted the changes in http://lists.w3.org/Archives/Public/public-diselect-editors/2007JanMar/0022.html and suggested some additional improvements in the text which were accepted in http://lists.w3.org/Archives/Public/public-diselect-editors/2007JanMar/0034.html

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