Re: [Uri-review] XMPP jabber: URI scheme not registered?

[Peter Saint-Andre <[e-mail]>]

On 11/28/12 9:14 PM, "Martin J. Dürst" wrote:
> Hello Peter,
> 
> On 2012/11/29 8:19, Peter Saint-Andre wrote:
> So here is the registration...
> 
> ###
> 
>     URI scheme name.
>        jabber
> 
>     Status.
>        permanent
> 
>     URI scheme syntax.
>        The only allowable strings are:
>        - jabber:client
>> ..
>     URI scheme semantics.
>        Strings of the form 'jabber:*' and 'jabber:*:*' were
>        used as XML namespace names during development of the
>        technology that became the Extensible Messaging and
>        Presence Protocol (XMPP).  The scheme was never used
>        for any other purpose.  The only namespace names
>        minted with this scheme are listed above.  No other
>        strings were minted, and no other strings shall be
>        minted.  Note that defining new URI schemes for XML
>        namespaces is now discouraged.  The 'jabber' scheme
>        was defined before standard best practices emerged.
> 
>     Encoding considerations.
>        Encoded as UTF-8 within XMPP protocol streams.
> 
>> This is irrelevant. See http://tools.ietf.org/html/rfc4395#section-2.6.
> 
>> I would write this as following:
> 
>>     Encoding considerations.
>>       None. All characters are within the characters allowed in URIs.

You are right. How about the following...

   Encoding considerations.
      None. Because the limited number of URIs (XML namespace
      names) minted with this scheme contain characters only
      from the ASCII range, encoding of internationalized code
      points is out of scope.  In addition, these namespace names
      do not contain any text fields that would be subject to
      specialized encoding.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/