-
Notifications
You must be signed in to change notification settings - Fork 58
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
namespace check: encryption.xml EncryptionProperty > ns:Compression (ns = http://www.idpf.org/2016/encryption#compression) #24
Comments
I opened an issue in the ReadiumSDK repository: |
Regarding the Compression XML element namespace, @mattgarrish says that it's either |
EPUB 3.1 draft update: |
Related issue (thanks @drmnside @thkim2015) w3c/epub-specs#697 |
Updated source code reference: type Compression struct {
Method int `xml:"Method,attr"`
OriginalLength uint64 `xml:"OriginalLength,attr"`
}
type EncryptionProperty struct {
Compression Compression `xml:"http://idpf.org/ns/encryption#compression Compression"`
}
type EncryptionProperties struct {
Properties []EncryptionProperty `xml:"http://www.w3.org/2001/04/xmlenc# EncryptionProperty"`
}
type Data struct {
encryptedType
Properties *EncryptionProperties `xml:"http://www.w3.org/2001/04/xmlenc# EncryptionProperties,omitempty"`
} |
The IDPF-endorsed XML namespace is @jpbougie could you please update: type EncryptionProperty struct {
Compression Compression `xml:"http://idpf.org/ns/encryption#compression Compression"`
} Many thanks! |
Fixed with 91cd5b1 |
Let's open this issue to track whether or not the LCP server implementation is using the correct namespace for
encryption.xml
's custom elementEncryptionProperty
>ns:Compression
, which currently is http://idpf.org/ocf/encryption#compression (reminder: this is where the attributesMethod
andOriginalLength
are used to cover the optional deflate+compress+store case)The IDPF specification currently does not normatively define this namespace, so we need a fallback strategy. I suggest a readium.org namespace, similar to that used for LCP. This would impact the source code:
https://github.com/readium/readium-lcp-server/blob/feature/compress-before-encryption/xmlenc/encryption.go#L120
...and of course Readium's own implementation:
https://github.com/readium/readium-sdk/blob/develop/ePub3/ePub/encryption.cpp#L27
(as you can see, there's already an inconsistency!)
Full EPUB issue:
w3c/epub-specs#646 (comment)
The text was updated successfully, but these errors were encountered: