Closed StephanMeijer closed 4 years ago
Not all content should and would be on a HTTP server in real life. URIs and URNs in general should be supported including but not limited to:
data:,Hello%20World
I therefore propose to replace the following attributes:
{ ... "contentHash": "8C9453EF2C0C6F2F94104D16FF0A8105BC6C9793D926457839D8BCADE0888342", "contentUrl": "https://test.com/image.png", ... }
With the following:
{ ... "content": { "hash": "8C9453EF2C0C6F2F94104D16FF0A8105BC6C9793D926457839D8BCADE0888342", "location": { "type": "url", "identifier": "https://test.com/image.png" } } ... }
Where $.content.location.type can be any of "url", "urn" or "uri".
$.content.location.type
"url"
"urn"
"uri"
Or alternatively:
{ ... "contentHash": "8C9453EF2C0C6F2F94104D16FF0A8105BC6C9793D926457839D8BCADE0888342", "contentLocation": { "type": "url", "identifier": "https://test.com/image.png" } ... }
Where $.contentLocation.type can be any of "url", "urn" or "uri".
$.contentLocation.type
Moved to right repository: https://github.com/wordproof/timestamp-standard/issues/6
Not all content should and would be on a HTTP server in real life. URIs and URNs in general should be supported including but not limited to:
data:,Hello%20World
I therefore propose to replace the following attributes:
With the following:
Where
$.content.location.type
can be any of"url"
,"urn"
or"uri"
.Or alternatively:
Where
$.contentLocation.type
can be any of"url"
,"urn"
or"uri"
.