w3c/epubweb

Issues by Dave Pawsons

Opened this issue · 2 comments

(Reproduced from email with authorization)

Terminology could do with a glossary

  • Portable document
  • Open web platform
  • Page (as used here)
  • STM (not expanded, ditto other acronyms)

No overall goal? See 2. for possibility " this effort will provide an open, non-proprietary, portable document format"

'Bright line distinctions' - could be clearer? Suggest different categories.

'or on-demand use of their distinguishing characteristics' suggest 'separate' characteristics

' People with technical expertise by anyone other than information technology departments were not previously required in traditional publishing workflows. ' Requires clarification?

'in case the data is too large to be distributed offline' Is this a proposed feature? Very useful for small memory devices, would be a worthwhile goal IMHO.

'as well complex administrative' s/well/well as/

Complex user manuals. A requirement is strict vsn control. Optional feature perhaps?

2.5 No mention of variant screen size? How to address 32" flat screen and 4" mobile issues? Making content flexible enough to be usable on both, or address this issue in the case of non-scalability? I note 2.8 intimates this but reality is that this is not always the case.

2.7 The archival of s/archival/archiving/

Issue: Elephant in the room? Google books, Kindle etc? Possible major users, not mentioned? Hinted at in 3.6

Section 3 reads very well!

3.3 may be very hard! No mention of learning from xlink, xpointer, SGML architectural documents.

3.7 Very important for me as a user.

Summary. An excellent start gentlemen. I wish you well. If I can help further, please ask.

Best wishes.

Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk

Added a set of fixes for this issue (list below). We need to figure out if there is more work to do in terms of definitions and acronym expansions before we can close. I don't have a problem with the current state in this regard, but I've been wrong before...

e1f58bc
8cb18ec
64750ae
0801e5c

I am fine with the changes; as for the glossary, I would propose we wait until issue #4 (the naming of the whole thing) is resolved, because that may lead other changes in terms of terminology...