ereuse
/
pyvckit
8
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

update READMES

This commit is contained in:
Cayo Puigdefabregas 2024-06-06 10:36:42 +02:00
parent 49bff70ed5
commit 1ec9b9ce9e
2 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -144,3 +144,11 @@ This document is an example and in production it must be adapted to contain the
did = generate_did(key, url) did = generate_did(key, url)
definitive_url, document = gen_did_document(did, key) definitive_url, document = gen_did_document(did, key)
``` ```
# Differences with didkit from spruceId:
Although there is didkit support, there are some small differences in behavior.
## Namespaces:
In didkit it is necessary to define in the context every name, (key) used in the credential or else both the signature and the verification will fail.
In pyvckit if a name, (key) is used but is not defined in the context, then that signature or verification will filter out that part of the credential and ignore it as if it did not exist.
The signature will be made by deleting that undefined part.

9
README_es.md
View File

@ -144,3 +144,12 @@ Este documento es un ejemplo y en producción hay que adaptarlo para contener la
did = generate_did(key, url) did = generate_did(key, url)
definitive_url, document = gen_did_document(did, key) definitive_url, document = gen_did_document(did, key)
``` ```
# Diferencias con didkit de spruceId:
Aunque hay compatibilidad con didkit, hay algunas pequeñas diferencias en el comportamiento.
## Espacios de nombres:
En didkit es necesario definir en el contexto todo nombre, (clave) usada en la credencial o si no fallará tanto la firma como la verificación.
En pyvckit si un nombre, (clave) se usa pero no esta definido en el contexto, entonces esa firma o verificación filtrará esa parte de la credencial y la omitirá como si no existiera.
La firma se hará borrando esa parte no definida.