Testing Linked Metadata Records

[dauwhe]

Testing Linked Metadata Records

[mattgarrish]

Would the package doc link to, um, another package document that contains conflicting FXL metadata?

A different serialization of it, I believe, yes. Wasn't this to avoid any confusion about precedence when we expected to define a web-friendly json version?

The closest we have now is a pub manifest, which isn't specifically defined for rendering, but in theory something like a conflicting page progression direction shouldn't override the package document.

I wouldn't call it a realistic test scenario, but linked resources kind of stray into an area where we could write a lot of tests and still not cover anything useful. Developers may be the only ones who can ever attest whether the restrictions are followed.

[dlazin]

Matthew seems to be working on this in #57.

[m22chan]

Hi everyone, the test merged in #57 assumes the linked metadata is ONIX. Is is only intended to test:

In the case of a linked metadata record [EPUB-33], Reading Systems MUST NOT skip processing the metadata expressed in the Package Document and only use the information expressed in the record.

The test book I submitted isn't reflective of any real scenario that I could see in the publishing industry - I'll admit, haha.

[iherman]

Closing' #57 takes care of this.