<?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>9716</bug_id>
          
          <creation_ts>2010-05-12 13:40:52 +0000</creation_ts>
          <short_desc>&quot;stringify&quot;</short_desc>
          <delta_ts>2011-06-08 21:17:19 +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>Working drafts</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>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="David Carlisle">davidc</reporter>
          <assigned_to name="Michael Kay">mike</assigned_to>
          <cc>evan</cc>
          
          <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>35621</commentid>
    <comment_count>0</comment_count>
    <who name="David Carlisle">davidc</who>
    <bug_when>2010-05-12 13:40:52 +0000</bug_when>
    <thetext>I&apos;m not sure that  &quot;stringify&quot; is a word, and perhaps more importantly, the behaviour of on-no-match? = &quot;stringify&quot; is not to generate a string but rather to copy text nodes. The difference between strings and text nodes doesn&apos;t usually matter, but when it does matter, it confuses people, so not using a syntax based on the word &quot;string&quot; would be good I think.

It&apos;s easier to criticise the current name than to suggest a new one. copy-text perhaps.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>35625</commentid>
    <comment_count>1</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2010-05-12 13:51:17 +0000</bug_when>
    <thetext>textualize? Or perhaps just &quot;text&quot;? (we wanted a verb, and I suppose &quot;text&quot; is a verb these days...)

We&apos;ve toyed with various ideas. I think we left &quot;stringify&quot; in as bait to attract comments.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>35648</commentid>
    <comment_count>2</comment_count>
    <who name="Evan Lenz">evan</who>
    <bug_when>2010-05-12 19:05:55 +0000</bug_when>
    <thetext>I like David&apos;s suggestion of &quot;copy-text&quot;. It avoids the misleading implication that elements are &quot;stringified.&quot; I had to read the description before realizing that it&apos;s just the normal default behavior. It also distinguishes itself nicely from &quot;copy&quot; (which applies to elements too).

Similarly, &quot;discard-text&quot; seems more appropriate, to avoid the implication that elements are discarded. Again, I found &quot;discard&quot; by itself misleading.

Yes, the distinction applies to attributes too (and simple values), but those are never processed implicitly, so it seems less important to make them explicit in the name.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>49342</commentid>
    <comment_count>3</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2011-06-08 21:07:23 +0000</bug_when>
    <thetext>The minutes of the Prague F2F (March 2011) say:

Note: discussed ad nauseam. MoZ has action item to write up alternative solutions for us to examine and select from. 
We reviewed MoZ&apos;s email of 2 September 2010.

http://lists.w3.org/Archives/Member/w3c-xsl-wg/2010Sep/0003.html (member-only)

We amended the proposal by replacing recursive-copy and recursive-skip by shallow-copy and shallow-skip, respectively.

RESOLVED: approve proposal as amended.

The resolution is thus:

1. deep-copy
2. shallow-copy (ex &quot;copy&quot;)
3. text-only-copy (ex &quot;stringify&quot;)
4. shallow-skip (ex &quot;discard&quot;)
5. deep-skip
6. fail (no change)

The draft has now been updated to reflect this resolution. David, if you are satisfied with this resolution could you please close the bug.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>49345</commentid>
    <comment_count>4</comment_count>
    <who name="David Carlisle">davidc</who>
    <bug_when>2011-06-08 21:17:19 +0000</bug_when>
    <thetext>thanks, closing</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>