Re: [Glossary] Definition of a portable document (and other things...)

I think we are almost there…

However, I would prefer to the MUST in the second bullet as a SHOULD (strong recommendation, not requirement).  I know this is the one point on which Bill and I disagree, but we have some actual use cases where this comes up.  Also, in my mind, this is the “cached” state for the PWD – where it would normally get something online but when not connected it could/would use something local (but not part of the document).

Leonard

From: Ivan Herman
Date: Thursday, September 10, 2015 at 7:24 AM
To: Bill McCoy
Cc: W3C Digital Publishing IG, Deborah Kaplan, Liam Quin, Leonard Rosenthol, Ralph Swick, Olaf Drümmer
Subject: Re: [Glossary] Definition of a portable document (and other things...)

Bill,

just picking up where we were yesterday, to settle the last few meters:-)

We seem to be in agreement in the definition of Web Resources, and Web Documents[1]; let us not repeat them here. What we want is a refinement of the portable part. At present, we have:

• A Portable Web Document: a Web Document which contains, within its constituent set, the information necessary to provide delivery of essential content and functionality, or a graceful degradation thereof, without the presence of any other Web Resources.

Following the idea I had yesterday evening, and also following Deborah's approach on adding some 'explanation' to the terms, what about adding the following two items:

[[[
• It must be possible to present the essential content of a Portable Web Document even if it is offline (though possibly with a lower quality, e.g., using suboptimal, but local fonts, or images instead of a remote video).

• Active processes (e.g., scripts) of a Portable Web Document, when responsible for an essential functionality, must not depend on Web Resources external to the Portable Web Document.
]]]

I was wondering about adding to the second post: "apart from the standards defined for Portable Web Documents, i.e., programming environments and standard API-s available in User Agents", but that might become to much details. This is not mathematics, after all:-)

Any more such "qualifying" notes? Are those fine?

I think that if we find a consensus on this part, we are done with the first round of glossary definitions… But there are more!

Ivan

[1] https://www.w3.org/dpub/IG/wiki/Glossary


----
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