Closed kuzdogan closed 1 month ago
I've updated the spec in #11
If we all agree, can you update it for Sourcify too @marcocastignoli ?
The only doubts that I have here is that inside the values some of the keys (e.g. libraries) contain multiple fields.
So it makes sense to have the transformation name in the singular, while transformation_values object keys in the plural.
transformations
[
{
"reason": "library",
"id": "__$KEY1$__"
....
},
{
"reason": "library",
"id": "__$KEY2$__"
....
}
]
transformation_values
{
"libraries": {
"__$KEY1$__": "0x...",
"__$KEY2$__": "0x...",
}
}
transformations keys:
values:
Fine for me. Any opinions @rimrakhimov ?
I agree with @marcocastignoli. I just believe 'data' is used in both singular and plural forms, so maybe it should be cborAuxdata
in both value and transformation
In the current application of the VerA schema, at least in practice, we have inconsistent naming for the transformations and the values "reasons":
Call Protection:
Transformation:
Value:
Similarly:
Rename all of them as such consistently:
callProtection
cborAxudata
immutable
library
constructorArguments
This doesn't need to be specified in an SQL schema etc. but putting it here for clarity. This will be specified in a doc explaining the JSON fields.