If there is a possibility, would this issue be converted into a Github Discussion?
27.09.2024 we had a very inspiring and intense discussion with Philipp Koellinger. Please find the video here:
...and the Fireflies.ai transcript and summary here.
We have discussed many aspects of decentralised PID from conceptual, philosophical and technical points of view, referring to our new Concept document and CODEX library. After the discussion, we highlighted the following questions that, as we all agreed, any team working on the concept of the decentralised PID should address:
Should the minting and provenance of the PID-associated data be based on the transaction-based model, as the blockchain-based technologies suggest? Is there a way to provide persistence, versioning and provenance without spending resources on blockchain maintenance? The other concern is the reliance on the third-party blockchain, like ETH we have right now.
Do we need to store all the operations and intention descriptions? Would creating a network of nodes exchanging non-anonymous open messages with a limited lifetime, but strictly standardised (and identified with highest-level PIDs) format and structure be more useful? This approach is highly inspired by ROS and SWIFT systems, where a message is always trusted due to its format identified with PID, and it is a subject for cross-control by every node the message passes. The idea here is to preserve persistence and versioning without keeping a log of all actions the involved Agents perform, as the ownership concept is already implemented in the persistent storage infrastructure.
Is the Agent's identity equal to his private key? Should we use the unified internal representation of an Agent to perform 2FA and persistent login of the single agent over many third-party identity token providers?
The synonymic model proposed in the CODEX library works like direct aliasing, and Philipp placed an example about dPID aliased by DOI. Could side-effectors be implemented to provide functionality for UNIRESOLVER? Ideally, here we should think about the decentralised system working over any other, as we may be the last ones having valid lookup tables available.
The users urge over the sovereignty implemented via prefixes. As the limit, every internal Agent's ID should be a) a PID, and b) the prefix. What do you think the best way is to implement this?
Is there a way to control and partially localize indexing, to keep it reusable?
The deployment costs need to be addressed. The technologies we use may be quite computationally expensive, and the users should have a very thorough estimation of costs and efforts. The deployment packages are also extremely useful, so is there a way to provide them?
Do we have now a central bootstrap point when the CODEX endpoint is deployed? How would we avoid this?
Do we consider the possibility of having different implementations of the same functionality of the key components of the PID system, like in the \$\LaTeX\$ ecosystem we have?
If there is a possibility, would this issue be converted into a Github Discussion?
27.09.2024 we had a very inspiring and intense discussion with Philipp Koellinger. Please find the video here:
...and the Fireflies.ai transcript and summary here.
We have discussed many aspects of decentralised PID from conceptual, philosophical and technical points of view, referring to our new Concept document and CODEX library. After the discussion, we highlighted the following questions that, as we all agreed, any team working on the concept of the decentralised PID should address: