Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File integrity of documents #1725

Open
jpmckinney opened this issue Dec 11, 2024 · 1 comment
Open

File integrity of documents #1725

jpmckinney opened this issue Dec 11, 2024 · 1 comment
Labels
Schema: Fields Relating to adding or deprecating fields in the JSON Schema

Comments

@jpmckinney
Copy link
Member

jpmckinney commented Dec 11, 2024

Split from #1724

For hashes and digital signatures, we can consider adding to the Document subschema an integrity array, to allow for any kind of hash (sha256, etc.) This array can be composed of objects that reuse the existing Identifier subschema, where scheme can be set to "sha256", "ipfs", etc. and id can be the hash or signature. So:

{
  "tender": {
    "documents": [
      {
        "integrity": [
          {
            "scheme": "sha384",
            "id": "oqVuAfXRKap7fdgcCY5uykM6+R9GqQ8K/uxy9rx7HNQlGYl1kPzQho1wx4JwY8wC"
          }
        ]
      }
    ]
  }
}
@jpmckinney jpmckinney added the Schema: Fields Relating to adding or deprecating fields in the JSON Schema label Dec 11, 2024
@jpmckinney jpmckinney changed the title Document file integrity File integrity of documents Dec 11, 2024
@pdiadia
Copy link

pdiadia commented Dec 12, 2024

Thank you, I agree with this proposal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Schema: Fields Relating to adding or deprecating fields in the JSON Schema
Projects
None yet
Development

No branches or pull requests

2 participants