3 ms·
Does an IPFS system allow you traverse the revision tree? I think the ideal system would be one with a canonical identifier plus a content / version based ident
by x1798DE 11y ago
Does an IPFS system allow you traverse the revision tree? I think the ideal system would be one with a canonical identifier plus a content / version based identifier, so that if, for example, there is a retraction, you will know that by visiting the current version, but if you want to see the cited version, that is also available.
- verisimilidude 11y agoI'd love to see that. I think versioning is possible in IPFS via merkle tree, but I haven't taken the time to understand how it would be implemented. https://github.com/ipfs/specs/tree/master/merkledag https://github.com/ipfs/specs/tree/master/merkledag
- IanCal 11y agoThat's something that would be possible with IPNS (which allows a mutable 'pointer' to an IPFS hash, though this is just my lay understanding). This way your IPNS address becomes your DOI equivalent, but also providing the IPFS hash would give a static reference to exactly what it was you saw. There are some kinks here, as there isn't currently a way of verifying that the IPFS hash given was seen at the IPNS address. You also can't take an IPNS address and get all previous versions. It does sound like that's possible to add to IPNS, but is a future plan. It would be a step forwards from the current system though. A bit of info on IPNS, which is in really quite early stages afaik: https://ipfs.io/ipfs/QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxdXBFca7D/example#/ipfs/QmQwAP9vFjbCtKvD8RkJdCvPHqLQjZfW7Mqbbqx18zd8j7/ipns/readme.md https://ipfs.io/ipfs/QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxd...