From 74bc794794c3cfea3e5229546766cd38efdf387d Mon Sep 17 00:00:00 2001 From: Juan Benet Date: Sun, 8 Nov 2015 08:16:09 -0500 Subject: [PATCH] link to paths issue --- merkledag/ipld.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/merkledag/ipld.md b/merkledag/ipld.md index 23d254e84..b159f3d46 100644 --- a/merkledag/ipld.md +++ b/merkledag/ipld.md @@ -286,7 +286,7 @@ Suppose _this_ was the _exact order_ in the _Canonical Format_ (not json, but cb #### Path Restrictions -There are some important problems that come about with path descriptions in Unix and the web. For a discussion see (TODO link to path issue in go-ipfs or go-ipld). In order to be compatible with the models and expectations of unix and the web, IPLD explicitly disallows paths with certain path components. **Note that the data itself _may_ still contain these properties (someone will do it, and there are legitimate uses for it). So it is only _Path Resolvers_ that MUST NOT resolve through those paths.** The restrictions are the same as typical unix and UTF-8 path systems: +There are some important problems that come about with path descriptions in Unix and the web. For a discussion see [this discussion](https://github.com/ipfs/go-ipfs/issues/1710). In order to be compatible with the models and expectations of unix and the web, IPLD explicitly disallows paths with certain path components. **Note that the data itself _may_ still contain these properties (someone will do it, and there are legitimate uses for it). So it is only _Path Resolvers_ that MUST NOT resolve through those paths.** The restrictions are the same as typical unix and UTF-8 path systems: TODO: