- From: <bugzilla@jessica.w3.org>
- Date: Thu, 03 Mar 2016 12:04:21 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29516
Bug ID: 29516
Summary: [ser31] Definitions spanning paragraphs
Product: XPath / XQuery / XSLT
Version: Candidate Recommendation
Hardware: PC
OS: All
Status: NEW
Severity: editorial
Priority: P2
Component: Serialization 3.1
Assignee: cmsmcq@blackmesatech.com
Reporter: mike@saxonica.com
QA Contact: public-qt-comments@w3.org
Target Milestone: ---
See the definition of
https://www.w3.org/TR/xslt-xquery-serialization-31/#to-a-json-string
At first sight it appears that the spec has solved the problem of writing a
multi-paragraph definition, highlighted in bug #29513 against the XSLT 3.0
specification.
However, on closer examination it appears that the markup is not DTD-valid, so
it's not a solution to the problem at all (and I'm surprised that the build
succeeds). It has a <p> which contains a <termdef> which contains an <olist>.
Our markup doesn't allow lists within paragraphs, so this breaks the rules.
It would be good to enhance the DTD and stylesheet for all the specs to allow
multi-paragraph definitions. Note that there are many cases in the
serialization spec where a definition ends in mid-sentence because of this
limitation.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 3 March 2016 12:04:25 UTC