As an example, I have put this into the 'notsoshifty' alias:
{"web":"http://www.notsoshifty.de/","fb":"notsoshifty","twitter":"notsoshifty","nxtacct":"11111125831111116332","smtp":"notsoshifty111@example.com","skype":"notsoshifty1971"}
Or, easier to read:
{
"web" : "http://www.notsoshifty.de/",
"nxtacct" : "11111125831111116332",
"smtp" : "notsoshifty111@example.com",
"skype" : "notsoshifty1971",
"twitter" : "notsoshifty",
"fb" : "notsoshifty"
}
So the idea would be that if "nxt:notsoshifty" was entered into a browser, the browser extension would fetch the alias, look for the 'web' entry, and go to that URL (
http://www.notsoshifty.de/). A nxt client would look for the 'nxtacct' entry if it was in reference to making a payment; an email client would look for 'smtp', etc.
Ferment: if you think this is a good idea, perhaps you could modify the 22k.io site (and browser extensions?) to check for json and act accordingly? (It should also support the existing method of course). Also anybody who might be developing nxt clients using aliases as account numbers.
{"contact:{"web":"http://www.notsoshifty.de/","fb":"notsoshifty","twitter":"notsoshifty","nxtacct":"11111125831111116332","smtp":"notsoshifty111@example.com","skype":"notsoshifty1971"}}
Then a parser could decide quickly how to handle a nxtdata alias instead of having to guess by the existence of a combination of key names.