"revocation_date": " ", // additionally generate new hash? chain independent of the entries? design? java microservice revocation (mutable)
"revocation_reason": "", // revocation of a registration only under special circumstances e.g. proof of copyright infringement (mutable)
"registration_date": " ", // timestamp without time zone (immutable)
"tags": " ", (immutable)
"relation": " ", // also for collections (immutable)
"tags": " ", (mutable)
"relation": " ", // also for collections (mutable)
"supersedes": " ", // new version of the work (mutable)
"counter": "3156", // subsequent number of work, not sure if we still need that
"counter": "3156", // subsequent number of work (immutable), not tight
"publishing_date":"2022-03-12", // date of broadcasting (mutable)
"grid": "RC-01-LIZ0000003156-2", // RC > FC / FR (immutable)
"public_certificate": "https://www.registeredcommons.org/document/1124800676.pdf", // if we generate some extra certificate, we put the URI here (immutable)
"language": "DE_de", // ISO ?? check DB (immutable)
"language": "DE_de", // ISO ?? check DB (mutable)
"visibility": "yes", // work is public (mutable) The visibility can be changed afterwords.
"customkey0": "2022-02-12", // date of archiving, specific to a user / type of work: audio > duration
"customkey1": "", // free selectable attributes, sub-record in the DB, second table, attributes-array
...
...
@@ -95,4 +95,6 @@ Auf Arweave deployte Metadaten des "CHINA 2" NFT
]
}
}
```
\ No newline at end of file
```
Users can issue a new version, then the supersedes field of the new version holds the GRID of the old version.
