On 2011-09-23 01:40, Tab Atkins Jr. wrote:
On Thu, Sep 22, 2011 at 3:28 PM, James Hawkins<jhawk...@google.com> wrote:
When designing the format of the Web Intents action string, we got a lot of
feedback that the java namespacing is not native to the web and that URLS
would be a better namespacing scheme. This gave us the added benefit that,
by setting precedence with the default list actions, action URLs serve both
as a namespace mechanism and the page at the URL contains documentation for
the particular action. If a developer wants to find out more about
http://webintents.org/share, all she has to do is visit that URL (try it!).
If, for example, Twitter decided to add a new action, say 'tweet', they
could set the action string to http://dev.twitter.com/tweet which would
contain the input/output specification for this action.
URLs are really, really not a good namespacing mechanism, because URLs
are not names in practice. Names are compared with string-equality,
generally. URLs are compared as URLs, which is a lot crazier. Is
...
No, they are not. It depends on context.
"http://dev.twitter.com/tweet"; the same action as
"http://dev.twitter.com/tweet/";? What about
"https://dev.twitter.com/tweet"; or "//dev.twitter.com/tweet" or
"/tweet" (assume this last one is on a page within dev.twitter.com)?
Yes, a spec needs to specify that.
There's a decent chance that all of these are considered "the same
url" by devs, and devs will probably attempt to use them. I haven't
even mentioned yet the presence/absence of "www" in urls.
Contrary to what you say, I don't see anybody confused by URI comparison
when URIs are used as identifiers.
...
Best regards, Julian
