[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: URI/IRI/XRI - what should extend what?
Hi All, The XRI Syntax spec describes IRI as extending the character set of URI, and then describes XRI as extending the syntactic elements (but not the character set) of IRI. If I were a product vendor, it would sound to me like in order to support XRI, my products would first (or also) have to support IRI. I might think IRI support sounds complex with lots of implications to my install base, so if I decide not to support IRI it also means I wouldn't be supporting XRI. To me it seems like IRI adds lots of complexity to XRI. I'd rather just say XRI is a URI scheme, restricted to UTF-8 like any other URI. In XRI let's not even worry about other encodings. When international characters are needed in an XRI, then the IRI spec deals with how to do it. Let's leave the complexity in the IRI spec. Of course we could include a section in the XRI Syntax spec that gives examples of how to convert a URI with a scheme of xri:// into an IRI according to the steps described in RFC 3987. I put this idea on the wiki (item #3.11 under XRI Syntax). Marty.Schleiff@boeing.com; CISSP Associate Technical Fellow - Cyber Identity Specialist Computing Security Infrastructure (206) 679-5933
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]