Behavior of Memento endpoints in replay systems with iframes

Skip to first unread message

Sawood Alam

Jul 3, 2019, 2:40:38 PM7/3/19
to memento-dev
I wanted to discuss here the behavior of Memento endpoints of replay systems that use iframes to isolate banners from the memento. The iframe of the memento may or may not be served from a different domain.

• Should the parent/wrapper URI be returned in Memento related Link headers or the inner iframe URI (or both maintain their independent URI-Ms)?
• How should tools establish relationship between the banner URI-M and the actual inner URI-M (without processing HTML or executing JS to identify the iframe hosting the inner memento)?
• What should be reported in TimeMaps (banner mementos, inner mementos, or both)?
• What should be the behavior of aggregators?
• TimeMap of banner URI-M means there won't be the actual content in it when a non-recursive fetch is made (using tools like cURL) and all URI-Ms will return largely the same content.
• Should replay systems always advertise the inner URI-M, but in a web browser environment redirect to the top (banner) iframe when loaded?


Note: This has been posted in the IIPC Slack, but Martin suggested memento-dev would be a better place for this discussion.


Sawood Alam
Department of Computer Science
Old Dominion University
Norfolk VA 23529

Reply all
Reply to author
0 new messages