{"action":"created","issue":{"url":"https://api.github.com/repos/ipfs/go-ipfs/issues/1678","labels_url":"https://api.github.com/repos/ipfs/go-ipfs/issues/1678/labels{/name}","comments_url":"https://api.github.com/repos/ipfs/go-ipfs/issues/1678/comments","events_url":"https://api.github.com/repos/ipfs/go-ipfs/issues/1678/events","html_url":"https://github.com/ipfs/go-ipfs/issues/1678","id":105824027,"number":1678,"title":"Standard URL format for ipfs/ipns objects","user":{"login":"larsks","id":82622,"avatar_url":"https://avatars.githubusercontent.com/u/82622?v=3","gravatar_id":"","url":"https://api.github.com/users/larsks","html_url":"https://github.com/larsks","followers_url":"https://api.github.com/users/larsks/followers","following_url":"https://api.github.com/users/larsks/following{/other_user}","gists_url":"https://api.github.com/users/larsks/gists{/gist_id}","starred_url":"https://api.github.com/users/larsks/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/larsks/subscriptions","organizations_url":"https://api.github.com/users/larsks/orgs","repos_url":"https://api.github.com/users/larsks/repos","events_url":"https://api.github.com/users/larsks/events{/privacy}","received_events_url":"https://api.github.com/users/larsks/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":15,"created_at":"2015-09-10T14:40:18Z","updated_at":"2015-09-13T04:11:27Z","closed_at":null,"body":"I would like to add ipfs support to a tool that expects a URL-format specification.  Hypothetically, let's say I wanted to add ipfs suport to `curl`.  I would need a `scheme:data` format specification that follows [the standard url format](http://www.w3.org/Addressing/URL/url-spec.txt).\r\n\r\nI asked about this on irc and immediately folks started trying to direct me *away* from URLs to the [multiaddr](https://github.com/jbenet/multiaddr) spec.  Setting aside for the moment then I'm not clear what problem multiaddr is trying to solve or why URLs aren't appropriate, some tools will simply require a URL format to operate.\r\n\r\nIn the absence of any other suggestions, I would like to suggest that we document the following standard forms:\r\n\r\n- `ipfs:<hash>[/<path>]` for IPFS objects, as in: \r\n\r\n        ipfs:QmPXME1oRtoT627YKaDPDQ3PwA8tdP9rWuAAweLzqSwAWT/readme\r\n\r\n- `ipns:<hash>[/path]` for IPNS names:\r\n\r\n        ipns:QmXfrS3pHerg44zzK6QKQj6JDk8H6cMtQS7pdXbohwNQfK/pages/gpg.md\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/ipfs/go-ipfs/issues/comments/139843292","html_url":"https://github.com/ipfs/go-ipfs/issues/1678#issuecomment-139843292","issue_url":"https://api.github.com/repos/ipfs/go-ipfs/issues/1678","id":139843292,"user":{"login":"btrask","id":301663,"avatar_url":"https://avatars.githubusercontent.com/u/301663?v=3","gravatar_id":"","url":"https://api.github.com/users/btrask","html_url":"https://github.com/btrask","followers_url":"https://api.github.com/users/btrask/followers","following_url":"https://api.github.com/users/btrask/following{/other_user}","gists_url":"https://api.github.com/users/btrask/gists{/gist_id}","starred_url":"https://api.github.com/users/btrask/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/btrask/subscriptions","organizations_url":"https://api.github.com/users/btrask/orgs","repos_url":"https://api.github.com/users/btrask/repos","events_url":"https://api.github.com/users/btrask/events{/privacy}","received_events_url":"https://api.github.com/users/btrask/received_events","type":"User","site_admin":false},"created_at":"2015-09-13T04:11:27Z","updated_at":"2015-09-13T04:11:27Z","body":"I understand Juan. Sorry for the misleading comparison.\r\n\r\nIf IPFS addresses are paths, what would you think about simply using `file://` URLs?\r\n\r\n```\r\nfile:///ipfs/QmeeQhGoyMQc7eQWERE88kFFq4WbdVRrjHctZhH1hPHNds/006/mdag.waist.png\r\nfile:///ipns/QmfVrBzjaXjWWfC7UhFrZnnFFMYA1ENPCjzxAtREaQz8MS/006/mdag.waist.png\r\nfile:///ipns/ipfs.io/docs/install\r\n```"}}