Mickaël Menu

Keeping the fragments as strings is really important in my opinion: - A fragment identifier is supposed to be a string of characters - We can use them with URI...

I'm trying to add the remaining `` properties into `otherMetadata`. But I don't know what to do with those namespace prefixes (eg. `dc` in `dc:source`). Should we remove it from...

Okay, I think I found something in `libxml2` that I could expose to Swift (`node->nsDef`) to get the `xmlns:x` attributes.

I have three related questions: 1. How do we handle multiple values (eg. several `` with same `property` or `name`)? The entries in the `otherMetadata` could be either `String` or...

I just found out that the prefixes used in `meta[@property]` are not XML namespace prefixes, but actually declared in `package[@prefix]` with a list of default prefixes (http://www.idpf.org/epub/301/spec/epub-publications.html#sec-metadata-reserved-vocabs). Great news, I...

For reference, I came up with this solution on Swift: https://github.com/readium/r2-streamer-swift/commit/037de4d2c15f2697176f7eb26e315dd0b01ea236?diff=unified#diff-b8124a64cd2aa700aa444e5f9a7d7232 This generates the `otherMetadata` JSON but is also used to access metadata from their name and associated vocabulary. This...

Note for anyone tackling this issue: `Link.href` can be templated and thus should stay as a String, because the conversion with URL loses information.

No it's actually not done yet, I commented this to make sure that the person tackling this issue wouldn't convert the `Link.href` to an URL, as it would break templated...

It's not supported, the `User` object only mirrors the JSON schema with the list of encrypted fields: https://github.com/readium/r2-lcp-swift/blob/d69f7bd315d40ea29c5f75d80adbc6a0578d1c7e/readium-lcp-swift/License/Model/Components/LCP/User.swift#L24

A possible solution that allows all the customization needed would be this delegate to be implemented by the host app (possibly the navigator can provide a default implementation using the...