<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://www.w3.org/Bugs/Public/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4"
          urlbase="https://www.w3.org/Bugs/Public/"
          
          maintainer="sysbot+bugzilla@w3.org"
>

    <bug>
          <bug_id>29513</bug_id>
          
          <creation_ts>2016-03-02 11:26:19 +0000</creation_ts>
          <short_desc>[XSL30] Definition of &quot;potentially consuming&quot; in Glossary not complete</short_desc>
          <delta_ts>2016-07-21 16:33:23 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>XPath / XQuery / XSLT</product>
          <component>XSLT 3.0</component>
          <version>Candidate Recommendation</version>
          <rep_platform>PC</rep_platform>
          <op_sys>Windows NT</op_sys>
          <bug_status>CLOSED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>editorial</bug_severity>
          <target_milestone>---</target_milestone>
          <dependson>29516</dependson>
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Abel Braaksma">abel.braaksma</reporter>
          <assigned_to name="Michael Kay">mike</assigned_to>
          
          
          <qa_contact name="Mailing list for public feedback on specs from XSL and XML Query WGs">public-qt-comments</qa_contact>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>125320</commentid>
    <comment_count>0</comment_count>
    <who name="Abel Braaksma">abel.braaksma</who>
    <bug_when>2016-03-02 11:26:19 +0000</bug_when>
    <thetext>The definition of &quot;potentially consuming&quot; in section C Glossary reads:

&lt;quote&gt;
potentially consuming

    An operand is potentially consuming if either or both of the following conditions applies:
&lt;/quote&gt;

In other words, the important part of the definition, after the colon, has disappeared.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>125321</commentid>
    <comment_count>1</comment_count>
    <who name="Abel Braaksma">abel.braaksma</who>
    <bug_when>2016-03-02 11:27:13 +0000</bug_when>
    <thetext>(and shouldn&apos;t it be &quot;apply&quot; instead of &quot;applies&quot;?)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>125322</commentid>
    <comment_count>2</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2016-03-02 12:36:05 +0000</bug_when>
    <thetext>Yes I&apos;ve been frustrated by this limitation in the markup design for a long time: we don&apos;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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>125323</commentid>
    <comment_count>3</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2016-03-02 12:42:23 +0000</bug_when>
    <thetext>The serialization spec has many definitions that end in mid-sentence like this, but I noticed that they&apos;ve solved the problem in section 9 for the definition of serializing &quot;to a JSON string&quot; which is a multi-paragraph definition. So we should find out how they did it.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>125347</commentid>
    <comment_count>4</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2016-03-04 00:03:00 +0000</bug_when>
    <thetext>In the latest editor&apos;s draft I have fixed this using the markup suggested in bug #29516. I haven&apos;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&apos;t like &quot;either or both of these conditions apply&quot; (it just sounds wrong although the text books say it&apos;s right), so I changed it to &quot;at least one of these conditions applies&quot;.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>125678</commentid>
    <comment_count>5</comment_count>
    <who name="Abel Braaksma">abel.braaksma</who>
    <bug_when>2016-03-31 21:32:35 +0000</bug_when>
    <thetext>I can see the fix in the current internal draft and it looks correct, should we close this bug report?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>125679</commentid>
    <comment_count>6</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2016-03-31 21:58:06 +0000</bug_when>
    <thetext>I&apos;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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>126955</commentid>
    <comment_count>7</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2016-07-14 22:13:59 +0000</bug_when>
    <thetext>The DTD and stylesheet extensions to handle multi-paragraph glossary definitions have now been committed.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>127008</commentid>
    <comment_count>8</comment_count>
    <who name="Abel Braaksma">abel.braaksma</who>
    <bug_when>2016-07-20 14:11:02 +0000</bug_when>
    <thetext>I checked the diff version and the normal version of the internal WD&apos;s, they both look good and I didn&apos;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 &quot;combined posture&quot;, &quot;tail position&quot; and &quot;non-positional predicate&quot;, which previously all ended with a colon (:) and a missing list paragraph, but are now complete with the full definition of the text.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>