We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://readium.org/lcp-specs/releases/lcp/latest.html#35-pointing-to-external-resources-the-links-object
length - Content length in octets - Integer
length
Content length in octets
Integer
hash - SHA-256 hash of the resource - Base 64 encoded octet sequence
hash
SHA-256 hash of the resource
Base 64 encoded octet sequence
"example 3":
{ "rel": "publication", "href": "https://www.example.com/file.epub", "type": "application/epub+zip", "length": "264929", "hash": "8b752f93e5e73a3efff1c706c1c2e267dffc6ec01c382cbe2a6ca9bd57cc8378" },
...as you can see, the example shows hash as a hex-encoded value, not b64. Furthermore, length is a string, not an integer.
The Go implementation produces hash as hex-encoding, and length as number value:
See examples of LCP license JSONs generated by the Go implementation:
https://www.edrlab.org/readium-lcp/testing-readium-lcp-compliant-devices/
Suggested fix:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
https://readium.org/lcp-specs/releases/lcp/latest.html#35-pointing-to-external-resources-the-links-object
length
-Content length in octets
-Integer
hash
-SHA-256 hash of the resource
-Base 64 encoded octet sequence
"example 3":
...as you can see, the example shows
hash
as a hex-encoded value, not b64. Furthermore,length
is a string, not an integer.The Go implementation produces
hash
as hex-encoding, andlength
as number value:See examples of LCP license JSONs generated by the Go implementation:
https://www.edrlab.org/readium-lcp/testing-readium-lcp-compliant-devices/
Suggested fix:
length
example by replacing the string with an integerThe text was updated successfully, but these errors were encountered: