Edit comment LC-1563 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-1563

Comment Shortname:

Commenter: Elliotte Harold <elharo@metalab.unc.edu>

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:

There is a pervasive problem of missing spaces in the HTML version of the spec. For example, there's a space missing between functions and attribute in section 4.4:

"The value of the functionsattribute is a space-separated list of the
XPath extension functions that are required for processing. Each..."

A side note: the word functions is in code and the word attribute is
not. This is not the first time I've noticed this particular style of
missing space in a W3C draft. is it possible something in your toolchain is losing spaces after a </code> tag?

Also:

In section 1.1 I find this:

One common theme emerging from this work was the need to support authors
in the specification of variabilityin the materials they produce.

In this case there's a missing space between "variability" and "in".
Here a </a> tag separates them. It really is starting to look like a
weird tool bug.

Related issues: (space separated ids)

WG Notes: This seems to be an interaction between how the particular XML editor used to create the XMLSPEC document and the XSLT used to create the HTML. A different editor seems not to cause this particular problem. Resolution communicated in http://lists.w3.org/Archives/Public/public-diselect-editors/2007JanMar/0008.html

Resolution: Continue to use the alternate editor and to review the document for missing spaces after conversion.

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