URI Confusion


Uniform Resource Identifiers are confusing. Even leaving aside the further confusion of Internationalized Resource Identifiers (don't get me started on those!), I have to say that the URI spec sometimes reads like some opaque philosophy text (and yes I have read Aristotle's Metaphysics in the original Greek so I know a thing or two about opaque philosophy texts!). This morning I spent an inordinate amount of time carefully constructing a precious few sentences for addition to rfc4622bis in order to address feedback from a helpful reviewer within the IETF. Here's an example:

XMPP IRIs and URIs are defined primarily for the purpose of identification rather than of interaction (regarding this distinction, see Section 1.2.2 of [URI]). The "Internet resource" identified by an XMPP IRI or URI is an entity that can communicate via XMPP over a network. An XMPP IRI or URI can contain additional information above and beyond the identified resource; in particular, as described under Section 2.5 a query component can be included to specify suggested semantics for an interaction with the identified resource. It is envisioned that when an XMPP application resolves an XMPP IRI or URI containing suggested interaction semantics, the application will generate an XMPP stanza and send it to the identified resource, where the generated stanza may include user or application inputs that are consistent with the suggested interaction semantics (for details, see Section 2.8.1).

Writing Internet specifications often makes me feel like I'm back in philosophy class. :)

Peter Saint-Andre > Journal