W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2016

[Bug 29814] [xslt30] Use of XPath comments

From: <bugzilla@jessica.w3.org>
Date: Thu, 22 Sep 2016 20:10:33 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29814-523-qYq4in2vmH@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29814

--- Comment #2 from Michael Kay <mike@saxonica.com> ---
We discussed this today. There was support for a view that said we should be
very liberal about accepting comments anywhere that it made sense, rather than
requiring users to remember which attributes allowed comments and which did
not. The downside is that where we define an attribute using XSD data types, we
don't want to allow things that XSD doesn't allow (or allow us to define),
because some people are likely to use the schema-for-XSLT to help with
syntax-directed editing.

I was given an action to propose a way forward.

Reviewing the list of attribute types in 2.2, I think we should allow
XPath-style comments anywhere that whitespace is allowed in attributes of
types:

expression
pattern
item-type
sequence-type

and of course within expressions in value templates

We should not allow comments in attributes of other types (boolean, string,
uri, uris, qname, eqname, eqnames, token, tokens, nmtoken, nmtokens, char,
integer, decimal, ncname, prefix, id) because this would interfere with our
ability to validate the attributes using XSD.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 22 September 2016 20:10:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:02 UTC