From bbc96295421968b6528d12b8ffb24a490c1e8a93 Mon Sep 17 00:00:00 2001 From: Yurii Shynbuiev - IOHK Date: Tue, 9 Jul 2024 03:12:49 +0700 Subject: [PATCH] feat: upgrade docusaurus and semantic-release packages Signed-off-by: Yurii Shynbuiev - IOHK Signed-off-by: Shota Jolbordi --- docs/docusaurus/credentials/issue.md | 4 ++-- docs/docusaurus/schemas/credential-schema.md | 2 +- docs/docusaurus/secrets/seed-generation.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/docusaurus/credentials/issue.md b/docs/docusaurus/credentials/issue.md index 086178a18e..30646fa8e0 100644 --- a/docs/docusaurus/credentials/issue.md +++ b/docs/docusaurus/credentials/issue.md @@ -183,7 +183,7 @@ The `issuingDID` and `connectionId` properties come from completing the pre-requ ::: - 📌 **Note:** Claims can also include the `exp` Expiration Time attribute, which is part of JWT claims. `exp` attribute is disclosable if specified and can have a value in epoch time (in seconds), indicating when the SDJWT credential expires for more details - +[RFC5719](https://datatracker.ietf.org/doc/html/rfc7519#page-9) Once the request initiates, a new credential record for the issuer gets created with a unique ID. The state of this record is now `OfferPending`. @@ -352,7 +352,7 @@ curl -X POST "http://localhost:8090/cloud-agent/issue-credentials/records/$holde } ``` 2. `keyId`: This is optional field but must be specified to choose which key bounds to the verifiable credential. - For more information on key-binding, . + For more information on key-binding, [ietf-oauth-selective-disclosure-jwt](https://datatracker.ietf.org/doc/draft-ietf-oauth-selective-disclosure-jwt). Currently, we only support the EdDSA algorithm and curve Ed25519. The specified keyId should be of type Ed25519. The purpose of the keyId should be authentication. diff --git a/docs/docusaurus/schemas/credential-schema.md b/docs/docusaurus/schemas/credential-schema.md index 77c826038b..56aff05830 100644 --- a/docs/docusaurus/schemas/credential-schema.md +++ b/docs/docusaurus/schemas/credential-schema.md @@ -168,7 +168,7 @@ DID of the identity which authored the credential schema. ### schema (JSON Schema) A valid [JSON-SCHEMA](https://json-schema.org/) where the credential schema semantic gets defined. -JSON Schema must be composed according to schema. +JSON Schema must be composed according to the [Metaschema](https://json-schema.org/draft/2020-12/schema) schema. **Example:** ```json diff --git a/docs/docusaurus/secrets/seed-generation.md b/docs/docusaurus/secrets/seed-generation.md index 5d9e805819..38bb865224 100644 --- a/docs/docusaurus/secrets/seed-generation.md +++ b/docs/docusaurus/secrets/seed-generation.md @@ -52,5 +52,5 @@ users can write down their mnemonic phrase, making it more convenient to keep tr By using BIP39, users have options to choose a mnemonic phrase length as well as a passphrase. There are many tools for generating a BIP39 seed including but not limited to: -- (use the BIP39 seed field which provides a 128-chars hex string) +- [BIP39](https://iancoleman.io/bip39/) (use the BIP39 seed field which provides a 128-chars hex string) - [BIP39 - implementations section](https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki#other-implementations) also provides a list of implementations