feat: add a draft specification for prism VDR (WIP) #3
Conversation
Signed-off-by: FabioPinheiro <fabiomgpinheiro@gmail.com>
FabioPinheiro
force-pushed
the
prism-vdr
branch
from
68020b0 to
2343210
Compare
| The DID Docuemtn is a simplacy version of the lasters status of the SSI. | ||
| That does not contains the `MASTER_KEY`; `ISSUING_KEY`; `VDR_KEY`. | ||
|
|
||
| Note: There are usa case where the SSI entry is not used as a DID. For example if you cares about managing Storage Entry. |
There was a problem hiding this comment.
It is confusing sentence for me , apart from the spelling mistakes
There was a problem hiding this comment.
I need review
| The data type for a Storage Entry is defined by the create event/operation. Depending on the filter used in the data, the following types of information/data may be stored: | ||
| - `E-7-3` - **bytes**: Represents a raw array of bytes. | ||
| - `E-7-4` - **Token Status List**: Represents a status list, as defined by https://datatracker.ietf.org/doc/draft-ietf-oauth-status-list/10/ | ||
| - `E-7-5` - **bitstring_status_list**: ???? | ||
| - `E-7-?` - **CID (content identifier)**: A reference to an IPFS document. |
There was a problem hiding this comment.
What do you think about storing just raw bytes and use media type to express how to handle the data? Application will interpret the data and protocol don't need to care what is being stored.
For example
text/plain; charset=utf-8application/statuslist+jwt- one of options in bit string statuslist
- other possible media types in SSI ecosystem
| - The Indexer MUST be deterministic. | ||
| - The Indexer MUST be able to rever all steps to a previous `Cardano Block`. | ||
| Ideally, we recommend that the index is able to backtrack all the steps and unapply. | ||
| - It's not responsibility of the Indexer to validate the signature of the PRISM Operation. |
There was a problem hiding this comment.
Interesting take. Why isn't this similar to the resolver? Behind the VDR interface, client wouldn't have the ability to replay all the events? Maybe in this document Indexer != VDR driver?
|
This is still a draft
Scecrtiong missing :