<?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>3055</bug_id>
          
          <creation_ts>2006-03-28 09:59:06 +0000</creation_ts>
          <short_desc>[F+O] How does iri-to-uri() handle an invalid IRI?</short_desc>
          <delta_ts>2006-11-16 18:52:54 +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>Functions and Operators 1.0</component>
          <version>Candidate Recommendation</version>
          <rep_platform>PC</rep_platform>
          <op_sys>Windows XP</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="Michael Kay">mike</reporter>
          <assigned_to name="Ashok Malhotra">ashok.malhotra</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>8927</commentid>
    <comment_count>0</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2006-03-28 09:59:06 +0000</bug_when>
    <thetext>The new rules for iri-to-uri() agreed in

http://www.w3.org/Bugs/Public/show_bug.cgi?id=2457

do not say how an invalid IRI should be handled: for example, a string that is not a valid IRI because it contains a space character.

There are two options: we define a new error code, or we say that invalid characters should be %HH-encoded.

Because it is common practice to use a space in a URI with the expectation that it will be encoded as %20, I suggest that we use the latter approach.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9300</commentid>
    <comment_count>1</comment_count>
    <who name="Ashok Malhotra">ashok.malhotra</who>
    <bug_when>2006-04-18 22:12:09 +0000</bug_when>
    <thetext>On the 2006 April 18 telcon the joint WGs agreed to add the following words to the description of fn:iri-to-uri: If $uri-part contains an invalid character, such as a space character, the invalid character is 
replaced by its percent-encoded form as described in [rfc3986] before the conversion is performed.

The WGS also asked that a note be added saying that this function does not check whether $uri-part was a legal IRI; it merely operates on the characters in $uri-part.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>