Comments on: Are URI schemas a dying art? http://thewebdesignjournal.com/2007/06/uri-schemas-are-dead/ Thu, 24 Dec 2009 08:30:09 -0700 http://wordpress.org/?v=2.8 hourly 1 By: Daniel Aleksandersen http://thewebdesignjournal.com/2007/06/uri-schemas-are-dead/comment-page-1/#comment-13024 Daniel Aleksandersen Fri, 29 Jun 2007 17:04:36 +0000 http://thewebdesignjournal.com/2007/06/uri-schemas-are-dead/#comment-13024 My point with this article where that URI schemas should describe resources and not actions. Such as <i>email:</i> instead of <i>mailto:</i>. The schema naming is the main problem here. If you use <abbr title="K Desktop Environment">KDE</abbr> for Linux you can choose system wide default applications. <abbr title="Macintosh Operating System">Mac OS</abbr> allows for something similar. This might be a little more difficult under Windows (as so much else). For your example you would have chosen one default voip application (like Skype) that should handle telephone resources such as tel: and sms:. My point with this article where that URI schemas should describe resources and not actions. Such as email: instead of mailto:. The schema naming is the main problem here.

If you use KDE for Linux you can choose system wide default applications. Mac OS allows for something similar. This might be a little more difficult under Windows (as so much else).

For your example you would have chosen one default voip application (like Skype) that should handle telephone resources such as tel: and sms:.

]]> By: Abdul Qabiz http://thewebdesignjournal.com/2007/06/uri-schemas-are-dead/comment-page-1/#comment-13013 Abdul Qabiz Fri, 29 Jun 2007 13:51:47 +0000 http://thewebdesignjournal.com/2007/06/uri-schemas-are-dead/#comment-13013 It seems, applications are not taking care of standard. And applications tend to come up with their own scheme to make sure application is launched always. If I install three different VOIP softwares, assuming all of them work with tel:// scheme. What should be the user interaction to launch application? Should user be presented three options to choose any one? Current pattern is to associate tel:// with any one application, that is what happens in case of mailto:// or file:// I think, to avoid the above scenario applications come up with non-standard things.. Which makes sense in some cases.. I would love to see a better user-interaction and standard way. -abdul It seems, applications are not taking care of standard. And applications tend to come up with their own scheme to make sure application is launched always.

If I install three different VOIP softwares, assuming all of them work with tel:// scheme. What should be the user interaction to launch application? Should user be presented three options to choose any one?

Current pattern is to associate tel:// with any one application, that is what happens in case of mailto:// or file://

I think, to avoid the above scenario applications come up with non-standard things.. Which makes sense in some cases..

I would love to see a better user-interaction and standard way.

-abdul

]]>