While there are many potential real-world applications, so far there are zero actual real-world applications.
Just because some currencies my server supports are fictional doesn't make the ability to buy them using bitcoins any less real than if someone bought any other product or service using real bitcoins.
Furthermore NMC, I0C, IXC, and DVC, even if none or only some of the others so far supported, do not think of themselves as not being real world. They are real world blockchains, tracking real world tokens, which real world people can control by use of real world cryptographic keys.
Sure there can be a slippery slope of amount of real-ness, with bitcoins being easier to cash out to fiat currencies at various exchanges while some of the other supported tokens have no direct cash-out to fiat currencies, but that is itself a real world thing as it is legal and political aspects of the real world that require some things to be farther from direct cashability into fiat than others.
I would like to think that this current alpha test is an alpha test of real world applicability of Open Transactions, in fact. It would be a pity if politics/law prevents real world applicability and even more so if it prevents even mere testing-for-real of whether it is in fact real world applicable.
GPG apparently ships with 4096 bit key capability so it seems that gimping it down to only 1024 bits or even 2048 bits out of fear of some legal/political attempt to prevent real world application of 4096 bit encryption might be a bit of "living in the past". Testing some gimped-down pretend/play version of the thing maybe isn't really a valid test of real world applicability if in the real world 1024 or 2048 bits are no longer considered sufficient bits for real world applications.
Allowing exchanges even just between DVC and BTC should be a real world application. How is it not?
-MarkM-
EDIT: Maybe for the real world we should structure things such that our customer is the signer of the signed nym that that customer uses to prove to us a nym is one of their nyms. That way there can be a separation of powers between a customer-knower agency that is our customer and the server, which does not need to know the customer-knowers private data about who its own customers are.
As long as we know who signed the certificate/nym, we can direct any enquiries as to on whose behalf that nym does its thing. From our perspective, it does it on their behalf.