use case documents, manifests, latest lists...

Dear all,

we had a really good discussion last Monday, and I was just wondering how to take it further.

Heather was quick enough to include the list we compiled at the of the meeting into the UCR draft:

https://w3c.github.io/dpub-pwp-ucr/#manifests-metadata

I was wondering hot to take it from here. I believe what we should do, for each of those entries, to have one or more use cases (simple they may be) that show why those entries are necessary. Editorially, this means collecting the various requirements attached to the use cases. As examples, I picked up 3 of those items and came up with two simple use cases; see below. If we think that is the right way to go, then maybe each of you who participated at the discussion (or others!) should come up with a short text to cover your favourite item on the list; the editors can then combine them into the document. Note that the manifest, at least in my mind, is in a very abstract sense, ie, (at least in my view): we are talking about all the information that a reading system needs to render/process/etc the publication content. Whether these information items should be mapped onto a single JSON file, or several files depending on the content, etc, is the next step.

Heather & Co. should tell us what the best way is to submit these. I am fine creating a PR on github with this, or just sending them by email, or anything else…

So here are my two entries for a start:

[[[

Alice reads an art catalogue publication on line, which is typeset with a particular type of font to increase the visual quality of the publication. Alice wants to be able to enjoy the catalogue offline (eg, on a plane), so she instructs her browser to make this possible. However, to do so, her browser (reading system) should ensure that the special font has the right licensing term to be installed on Alice's machine (as opposed to be just displayed when rendered).

Requirement:
 - 1. the information on the licensing terms of the publication resources must be available to the reading system

------
Dave wants to read a publication that consists of a several chapters, and includes lots of illustrations. Dave also wants to be able to read that content offline.

The publisher's production workflow is such that each chapter is provided as a separate HTML file; each HTML file links to a number of auxiliary files like CSS or data files, and the illustrations are also provided through separate high resolution images. The HTML files may also include links to other Web resources, which do not form an essential part of the publication, though (e.g., a link to a Wikipedia page describing the subject of the publication); Dave is fine if that resource is not necessarily available while offline

Requirements:
 - 1. the list of all _essential_ constituent resources must be available to the reading system
 - 2. the reading system must have the information on the reading order of the different chapters (including the starting point)

]]]

WDYT?

Ivan

----
Ivan Herman, W3C
Digital Publishing Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
ORCID ID: http://orcid.org/0000-0003-0782-2704