RE: Packaging Review

Thanks, Liam

Perhaps I'm misunderstanding something, but I think it is possible to fetch individual items using the type parameter in the URL? 

http://example.org/downloads/spending.pack#rel=describedby;type=application/ld+json
is the example 15 the section on Fragment IDs [1]. This is a URL pointing the metadata in JSON-LD (as opposed the metadata in Turtle.

In our publications world, might we see something like this to access the video element:
http://example.org/downloads/bookTitle.pack#rel=describedby;type= video/mp4 

I believe if we want to fetch multiple parts in parallel, we use a less specific URL. 

[1] http://w3ctag.github.io/packaging-on-the-web/#fragment-identifiers 


Tzviya Siegman
Digital Book Standards & Capabilities Lead
Wiley
201-748-6884
tsiegman@wiley.com 

-----Original Message-----
From: Liam R E Quin [mailto:liam@w3.org] 
Sent: Tuesday, February 10, 2015 11:32 PM
To: Siegman, Tzviya - Hoboken
Cc: DPUB mailing list (public-digipub-ig@w3.org)
Subject: Re: Packaging Review

On Tue, 10 Feb 2015 17:11:49 -0500
"Siegman, Tzviya - Hoboken" <tsiegman@wiley.com> wrote:

> Note that the document itself includes some issues as open questions. We might wish to offer our thoughts on those issues.

I think that would be a good idea.

Some thoughts I had when looking at the TAG document included...

* The lack of a byte-oriented table of contents means no ability to use HTTP Range to fetch an individual item, or to fetch multiple parts in parallel (consider a 3-hour long video with text captions in a following part)

* Similarly you can't easily extract individual items, hence might not be suitable for storing an ebook on disk (you _can_ do that with zip)


Liam



--
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.org/

Received on Wednesday, 11 February 2015 14:25:16 UTC