On 13 Sep 2015, at 11:21, Hussein Shafie wrote:
On 09/12/2015 12:44 PM, Leif Halvard Silli (russisk.no) wrote:
Sorry but answering "XXE cannot load or save HTML, only XHTML" was too
tempting.
:-D
XXE should of course not output - and need not support the parsing of
-
tag omissions. But with regard to load and save of data-* attributes,
then, as far as I can tell, well-formed data-* attributes are parsed
and
saved by XXE without trouble.
No, not at all.
Apart from the "red flag", parsing and saving works OK, no?
We don't know how to do that, as data-* prefixed attributes cannot be
expressed in any standard schema language.
1. I suppose, then, that Validator.nu uses a non-standard schema … Or
may be, like the OXygen team, Nuvalidator changed the Relax NG parser:
http://www.oxygenxml.com/forum/topic7698.html
2. Michael Kay
(http://lists.xml.org/archives/xml-dev/201205/msg00002.html) and C. M.
Sperberg-McQueen
(http://stackoverflow.com/questions/27862244/validate-attribute-names-using-regular-expressions)
on the other hand, says that XSD 1.1 does have support for this. Citing
Sperberg-McQueen: «the task is straightforward in XSD 1.1 with
assertions: add an attribute wildcard to the complex type, and add an
assertion along the lines of every $a in ./@* satisfies
matches(name($n),'^(data-|att1$|att2$|...)') (not tested -- replace
att1, att2 with the names of your 'normal' non-data attributes).»
3. Apart for those, advanced solutions, how about this: Let the user, in
a (simple) way specify that the document may contain some *specific*
data-* attributes? For example, let’s say that I want to allow exactly
data-leif="CDATA" in my document. (This is probably already possible,
but only if I learn to handle a schema language.)
However, XXE’s validation service has a few anomalies:
[ ... snip ... ]
OK.
Suggestions for the XXE valdation service:
1. WAI-ARIA attributes (namely, the role="*" attribute pluse the
various attributes prefixed with the "aria-" string) is meant for
any HTML or XML document for human consumption. Thus, you could
perhaps offer WAI-ARIA on/off button (inside Preferences -> Tools ->
Validat(ion)) to enable such attributes anywhere - in SVGs, MathML,
DocBook etc. (But note that, per the HTML5 specification, the exact
place were those attributes are permitted, is, for various reasons,
somehow convoluted. Hence, a on/off option, without further
refinement - while such a thing would be both progress and
acceptable, it would, I think, not completely match HTML5.)
2. There could be a on/off button to allow data-* attributes in any
flavour of HTML/XHTML. This makes sence, from the perspective the
latest iteration of HTML (namely the HTML5 spec) since, for example
the XHTML 1.0 strict doctype can be validated as a HTML5 document
provided that the document otherwise conforms to HTML5 - the NU
validators support this.
3. When working with 'HTML' profile of XHTML documents:
1. There could be a on/off button in the preferences to show a
warning when processing instructions are in use. Since the
latest iteration of HTML, namely HTML5, does not allow PI’s,
this limitation can be applied to XHTML1 meant for text/html
consumption as well - thus the limitation could apply to any
HTML profile document.
2. validation could, perhaps via the above on/off button, display a
'orange' warning message whenever the document contains
processing instructions = extension of HTML5.
3. perhaps via on/off button the validator could disallow PI’s in
'HTML' profile documents.
We would like to implement what you describe but we don't know how to
do it.
As explained above, the schema languages (W3C XML Schema, RELAX NG)
cannot express: "allow any attribute prefixed by strings such as
'data-' or 'aria-'".
Do those schema languages allow **any** fixed reaction for attributes
that begins with a certain string? E.g. "data-"? If yes, then XXE could
at least give a more useful responce than the false information that
such attributes are invalid. If not, then perhaps a message somewhere
else, like in the preferences or whatever, about this limitation of the
validator, would at least help a little bit.
As for ARIA: Please note that in the case of aria-*, then, even if they
follow the same syntax as data-* (namely aria+hypen+foo), that the ARIA
attributes are *specific*, predefined attributes. For example,
aria-labelledby="IDREFS" is one such attribute that has been defined by
the ARIA spec. Note as well, that ARIA defines some schemata that may or
may not be useful to you, if do you want to implement ARIA - both DTDs,
SGML Open Catalog and XSD is mentioned
<http://www.w3.org/TR/wai-aria/appendices#a_schemata>. (However the XSD,
from 2009, is probably outdated
<http://www.w3.org/MarkUp/SCHEMA/aria-attributes-1.xsd>) Btw, ARIA makes
use of at least one attribute – role – which is unprefixed.
For data-*, as hinted above, may be XXE could get an interface by which
users could list some specific data-* attributes that they want to
permit. (A place to enter a string of data-attributes, for example.)
OTOH, "3.2. 'orange' warning message whenever the HTML5 document
contains processing instructions" is an easy one. A very simple
Schematron (https://en.wikipedia.org/wiki/Schematron) could be used to
implement this.
Then I think it would be good if XXE got built-in support for that. ;-)
How about adding a "sanitize for Web" function? What I mean is a
saving/conversion feature which would save a copy of the current
XHTML document as an HTML document and which would, during the
conversion, also
1. strip non valid features (such as PI’s),
2. convert XML features to HTML features (e.g. change
xml:lang="nn"
to lang="nn" and change <?xml version="1.0" encoding="UTF-8"?> to
<meta charset="UTF-8"/>
3. save with the correct file extension
If you use "File|New" and select the document template called
"XHTML|5.0|HTML Page", you'll already have 2) and 3).
1) could indeed be implemented by "XHTML|Preview".
Implementing 1) via XHTML|Preview sounds like a good idea!
Will do.
+1 :-D
--
leif halvard silli
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
