Write is_supported_content_addressed_uri

[njgheorghita]

What was wrong?

Already used this function in both ethpm-cli and the ipfs pinner, so it seems like it belongs here.

Cute Animal Picture

[pipermerriam]

I'm 👍 on this as-is for now but this will very likely need to be extensible at some point to allow 3rd party URIs to be registered and accepted. Probably a similar mechanism to the eth-abi library with some kind of Registry implementation that allows new ones to be added with the library supporting the common use case with a default registry with the built-in URIs pre-registered.

[njgheorghita]

@pipermerriam What exactly do you have in mind by '3rd party URIs'? Can you give an example? I was under the impression that it was pretty much IPFS, Github blob, Swarm (eventually) that will be supported/valid content-addressed uris.

[pipermerriam]

@njgheorghita bitbucket, gitlab, gists, .... ipfs-gateway uris (there can be more than one gateway, cloudflair has one). The EthPM spec is intentionally open about the definition of a content addressable URI and thus, there are tons of options out there for people to include the content hash in different URI schemes.