This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 29513 - [XSL30] Definition of "potentially consuming" in Glossary not complete
Summary: [XSL30] Definition of "potentially consuming" in Glossary not complete
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows NT
: P2 editorial
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on: 29516
Blocks:
  Show dependency treegraph
 
Reported: 2016-03-02 11:26 UTC by Abel Braaksma
Modified: 2016-07-21 16:33 UTC (History)
0 users

See Also:


Attachments

Description Abel Braaksma 2016-03-02 11:26:19 UTC
The definition of "potentially consuming" in section C Glossary reads:

<quote>
potentially consuming

    An operand is potentially consuming if either or both of the following conditions applies:
</quote>

In other words, the important part of the definition, after the colon, has disappeared.
Comment 1 Abel Braaksma 2016-03-02 11:27:13 UTC
(and shouldn't it be "apply" instead of "applies"?)
Comment 2 Michael Kay 2016-03-02 12:36:05 UTC
Yes I've been frustrated by this limitation in the markup design for a long time: we don't have the ability for a definition to span multiple paragraphs. I have a feeling some of the other specs have solved the issue, I need to find out how.
Comment 3 Michael Kay 2016-03-02 12:42:23 UTC
The serialization spec has many definitions that end in mid-sentence like this, but I noticed that they've solved the problem in section 9 for the definition of serializing "to a JSON string" which is a multi-paragraph definition. So we should find out how they did it.
Comment 4 Michael Kay 2016-03-04 00:03:00 UTC
In the latest editor's draft I have fixed this using the markup suggested in bug #29516. I haven't yet committed the DTD changes needed to validate this markup; the DTDs are shared documents and consensus is needed to change them.

For some reason I don't like "either or both of these conditions apply" (it just sounds wrong although the text books say it's right), so I changed it to "at least one of these conditions applies".
Comment 5 Abel Braaksma 2016-03-31 21:32:35 UTC
I can see the fix in the current internal draft and it looks correct, should we close this bug report?
Comment 6 Michael Kay 2016-03-31 21:58:06 UTC
I'll close it when I have done a few more tests to ensure that the stylesheet changes have no adverse effects on other specs, and when I have committed all the changes.
Comment 7 Michael Kay 2016-07-14 22:13:59 UTC
The DTD and stylesheet extensions to handle multi-paragraph glossary definitions have now been committed.
Comment 8 Abel Braaksma 2016-07-20 14:11:02 UTC
I checked the diff version and the normal version of the internal WD's, they both look good and I didn't see other definitions in this section being disrupted (some got better though). I think this can be closed now.

Note: this change influenced the definition of "combined posture", "tail position" and "non-positional predicate", which previously all ended with a colon (:) and a missing list paragraph, but are now complete with the full definition of the text.