<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
<div></div>
<div>You can generate a temporary manifest from the MEI with a few well-written xpath queries. You may even wish to do this on the client side </div>
<div><br>
On Oct 18, 2016, at 8:39 AM, Michael Ryan Bannon <<a href="mailto:ryan.bannon@gmail.com">ryan.bannon@gmail.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<p dir="ltr">The problem is that diva.js is not able to load an image just by the image uri. It requires the entire manifest. But, at this point, it's no longer an mei concern. :)</p>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Oct 18, 2016 06:25, "Johannes Kepper" <<a href="mailto:kepper@edirom.de">kepper@edirom.de</a>> wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Andrew,<br>
<br>
Am 18.10.2016 um 06:13 schrieb Andrew Hankinson <<a href="mailto:andrew.hankinson@mail.mcgill.ca">andrew.hankinson@mail.mcgill.<wbr>ca</a>>:<br>
><br>
> IIIF Images have individual URIs to them. e.g.,<br>
><br>
> <a href="http://example.com/iiif/image.jpg/full/full/0/default.jpg" rel="noreferrer" target="_blank">
http://example.com/iiif/image.<wbr>jpg/full/full/0/default.jpg</a><br>
><br>
<br>
I was aware of that. I understood that Ryan would like to link to the manifest, which may be located somewhere completely different than the individual image files. When Diva.js was mentioned, I immediately had those cases with manuscripts spread across multiple
libraries in mind. While the image server should be able to deliver _some_ manifest from a predictable URL, it may not be the one that compiles the manuscript parts from different servers.<br>
<br>
> You can associate this with individual surface elements. Zone elements can then be related as child elements to those surfaces.<br>
><br>
> I would avoid using hash parameters for pages since the response from a IIIF manifest is JSON, and hash parameters have an undefined behaviour when presented with a non-XML or non-HTML response.<br>
<br>
You just found the words to better express my uneasiness ;-)<br>
<br>
><br>
> -Andrew<br>
><br>
> PS: Ryan is one of the 'folks at McGill.' :)<br>
><br>
<br>
That's what I thought – thanks for letting us participate in your discussions ;-)<br>
jo<br>
<br>
><br>
>> On Oct 14, 2016, at 2:12 PM, Johannes Kepper <<a href="mailto:kepper@edirom.de">kepper@edirom.de</a>> wrote:<br>
>><br>
>><br>
>>> Am 14.10.2016 um 19:35 schrieb Michael Ryan Bannon <<a href="mailto:ryan.bannon@gmail.com">ryan.bannon@gmail.com</a>>:<br>
>>><br>
>>> Hi Johannes,<br>
>>><br>
>>> Thanks for the input. I guess <graphic target="..." type="iiif" /> solves part of my problem - I can link to the manifest. However, I'm using Diva.js to display the contents so I can't reference a page directly with a URL. Rather, I have to load the entire
manifest then give a page index to the Diva.js API to load. So, I guess my question now is if I can attach extra data to a <graphic> element.<br>
>>><br>
>>> I suppose what I could do (which is maybe cheating) is to assume my own graphic type -- let's call it 'divajs' -- that requires the target be a URI with a page parameter. So, I could have:<br>
>>><br>
>><br>
>> this is exactly what I tried to say ;-)<br>
>><br>
>>> <graphic target="<a href="http://url/to/iiif/manifest.json#100" rel="noreferrer" target="_blank">http://url/to/iiif/<wbr>manifest.json#100</a>" type="divajs" /><br>
>>><br>
>>> Is this still valid MEI?<br>
>><br>
>> yes. graphic/@target has "anyURI" as content, and @type is just a token of your choice. MEI doesn't know or define what @type="iiif" means, and since it's your application that has to make use of it, you can equally well use @type="divajs". The only problem
I see with this setup is that<br>
>><br>
>>> <a href="http://url/to/iiif/manifest.json#100" rel="noreferrer" target="_blank">
http://url/to/iiif/manifest.<wbr>json#100</a><br>
>><br>
>> is not a regular URI (at least to my knowledge): Unlike in HTML, the hash has no specific meaning to get something inside a JSON file. However, if I got that right, IIIF is using JSON-LD. Following the documentation [1], each page is defined using a separate
object in an array:<br>
>><br>
>> "canvases": [<br>
>> {"@id":"<a href="http://www.example.org/iiif/book1/canvas/p1" rel="noreferrer" target="_blank">http://www.example.<wbr>org/iiif/book1/canvas/p1</a>",<br>
>> "@type":"sc:Canvas",<br>
>> "label":"p. 1"<br>
>> // ...<br>
>> },<br>
>> //...<br>
>> ]<br>
>><br>
>> The @id value is intended as the "official" link to this item. However, if you use mei:graphic/@target to point to this, you loose the reference to the manifest itself. You could add a bunch of redirects to your web server to resolve those links to the manifest,
but this feels equally strange as the "…/manifest.json#p100" solution.<br>
>><br>
>> I'd love to hear how the folks at McGill handle this…<br>
>> jo<br>
>><br>
>><br>
>><br>
>>><br>
>>> Tx,<br>
>>><br>
>>> Ryan<br>
>>><br>
>>> On Fri, Oct 14, 2016 at 1:10 PM, Johannes Kepper <<a href="mailto:kepper@edirom.de">kepper@edirom.de</a>> wrote:<br>
>>> Hi Ryan,<br>
>>><br>
>>> right now, I'm still using individual <surface> elements inside <facsimile>, one for each page. Each surface then has a <graphic target="path/to/manifest.json" type="iiif/>. This works mostly because I don't have a manifest for all pages (yet), but individual
for each page. This is clearly not ideal, but works for me for the time being. I wouldn't mind to link to the same manifest from multiple targets, and then use some kind of URI mechanism to refer to a specific page inside that manifest. I'm not that familiar
with IIIF, but afaik, each page (canvas) has an "@id" property, which can be used as target for the reference. I know the following syntax isn't working out of the box, but you may get the idea:<br>
>>><br>
>>> <facsimile><br>
>>> <surface label="fol 3v"><br>
>>> <graphic target="path/to/manifest.json#<wbr>page17" type="iiif/><br>
>>> <zone/><!-- if you like… --><br>
>>> </surface><br>
>>> </facsimile><br>
>>><br>
>>> Like you, I'm keen to learn about better ways to do this ;-)<br>
>>> jo<br>
>>><br>
>>><br>
>>>> Am 14.10.2016 um 18:47 schrieb Michael Ryan Bannon <<a href="mailto:ryan.bannon@gmail.com">ryan.bannon@gmail.com</a>>:<br>
>>>><br>
>>>> Hello MEI-ers,<br>
>>>><br>
>>>> I've been going over the MEI guidelines to find the best way of associating an external image manifest with an MEI <facsimile>, but I haven't had much luck. In particular, I'm dealing with images hosted on an IIIF server. So, I wouldn't necessarily have
a URL to the image. Rather, I would have:<br>
>>>><br>
>>>> - URL to an IIIF manifest<br>
>>>> - indices of pages in the manifest<br>
>>>><br>
>>>> I'm guessing the best solution is to have a <ref> element in my <meiHead> somewhere, then point to that <ref> from the <facsimile> element? (That's my best guess as I can't see how <facsimile> could contain the IIIF manifest URL or page indices, unless
I'm missing something.)<br>
>>>><br>
>>>> Any help is greatly appreciated.<br>
>>>><br>
>>>> Tx,<br>
>>>><br>
>>>> Ryan<br>
>>>> ______________________________<wbr>_________________<br>
>>>> mei-l mailing list<br>
>>>> <a href="mailto:mei-l@lists.uni-paderborn.de">mei-l@lists.uni-paderborn.de</a><br>
>>>> <a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l" rel="noreferrer" target="_blank">
https://lists.uni-paderborn.<wbr>de/mailman/listinfo/mei-l</a><br>
>>><br>
>>><br>
>>> ______________________________<wbr>_________________<br>
>>> mei-l mailing list<br>
>>> <a href="mailto:mei-l@lists.uni-paderborn.de">mei-l@lists.uni-paderborn.de</a><br>
>>> <a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l" rel="noreferrer" target="_blank">
https://lists.uni-paderborn.<wbr>de/mailman/listinfo/mei-l</a><br>
>>><br>
>>> ______________________________<wbr>_________________<br>
>>> mei-l mailing list<br>
>>> <a href="mailto:mei-l@lists.uni-paderborn.de">mei-l@lists.uni-paderborn.de</a><br>
>>> <a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l" rel="noreferrer" target="_blank">
https://lists.uni-paderborn.<wbr>de/mailman/listinfo/mei-l</a><br>
>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> mei-l mailing list<br>
>> <a href="mailto:mei-l@lists.uni-paderborn.de">mei-l@lists.uni-paderborn.de</a><br>
>> <a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l" rel="noreferrer" target="_blank">
https://lists.uni-paderborn.<wbr>de/mailman/listinfo/mei-l</a><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> mei-l mailing list<br>
> <a href="mailto:mei-l@lists.uni-paderborn.de">mei-l@lists.uni-paderborn.de</a><br>
> <a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l" rel="noreferrer" target="_blank">
https://lists.uni-paderborn.<wbr>de/mailman/listinfo/mei-l</a><br>
<br>
<br>
______________________________<wbr>_________________<br>
mei-l mailing list<br>
<a href="mailto:mei-l@lists.uni-paderborn.de">mei-l@lists.uni-paderborn.de</a><br>
<a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l" rel="noreferrer" target="_blank">https://lists.uni-paderborn.<wbr>de/mailman/listinfo/mei-l</a><br>
<br>
</blockquote>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>mei-l mailing list</span><br>
<span><a href="mailto:mei-l@lists.uni-paderborn.de">mei-l@lists.uni-paderborn.de</a></span><br>
<span><a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a></span><br>
</div>
</blockquote>
</body>
</html>