2010-02-03 Conference Call
Time: 20:00 UTC, 12:00 Los Angeles, 13:00 Denver, 15:00 New York, 20:00 London, 21:00 Zurich, 05:00 Tokyo next day, 07:00 Sydney next day
For other times, see the world clock at: http://www.timeanddate.com/worldclock/full.html
Dial in: +1 712.432.7300 Pin: 314850#
1. Minutes, Recording, and Scribe
The Agenda & Minutes is a single node in the EPUB Maintenance wiki. The scribe will insert the minutes into the agenda. Working group members may contribute to the minutes, make corrections etc. Essentially minutes will be available shortly after the call.
Recording will be available for calls: use the same dial in and pin. *3 followed by the file name, yymmdd (100203)
Reminder: Catherine Zekri will record the call separately for her research. For a Summary of Research & Information to Participants see her web page ebooks-and-society.
Minutes:
Scribe for the day: xxx
2. Present: xx Participants
- George Kerscher – DAISY Consortium
- Garth Conboy – eBook Technologies
- Alexis Wiles – OverDrive
- Bill Kasdork – Apex CoVantage
- Brady Duga – eBook Technologies
- Catherine Zekri – University of Montreal
- Guy Fain – Crossway Books & Biblies
- Hadrien Gardeur – Feedbooks
- Jim Link – Macmillan Publishing Solutions
- John Prabhu – HOV Services
- Markus Gylling – DAISY Consortium
- Paul Norton – Invited Expert
- Takeshi Kanai – Sony
- Michael Smith – IDPF
Regrets:
- Pat Payton; Bowker
- Keith Fahlgren, Threepress
- Liza Daly, Threepress
- Eric Muller, Adobe
- Karen Broome, Sony
3 Discussion of issues moving towards maintenance release
- Two new posts re the NCX Reading System Requirements issue:
- last week suggested NCX should be
- comment seven has been added as suggested prose for resolution. We wil wait week to see if any objections
- NavMap, NavList, PageList
- KF: not yet comfortable with saying reading systems MUST support pageList
- pageList is for mapping print page number with pageList. Intention to synch print book with digital book in Education
- up to content creator to properly markup file.
- If publisher doesn't need page numbers to synch print/digital they don't need to add pageListt
- BK: feels that Journals and Scholarly Publications should work to make this clear and straight forward. Make this a normal practice as EPUB moves forward
- important for cross-references
- Concern raised that we don't wish to break any compliant reading systems
- PS: Doesn't like language that says "must be included"
- BD: feels like 2.0 version wasn't passed with this intent
- If content creator has list going many levels deep into document there may an issue with reading devices
- GK: If go more than 6 levels deep, generally too much. TextBooks etc likely only need to go no more than 4 levels at most
- NavMap supplies heirarchal information, pageList
- BD: 2 questions:
- What level of support do we want to mandate regarding NCX support.
- currently it is vague
- Is this appropriate time to be making change of requirements on reading systems?
- are we imposing restrictions on reading systems that were not intended at 2.0 time
- GC: concerned about having something at 2.01 level that defines...
- PS: reminder there are devices out there that do not define TOC because consumer hasn't asked for it
- BK: maybe this is more an issue of degree. Can we put instruction they need to support at least at Chapter Level
- What about readers that say they support EPUB but are not able to read even at Chapter Level
- GK: this is powerful function. To display there is a "go to page" function. Same is true for navigation where it just pops up or have "hot key" to go to next area
- If we decide it's not for this release and is for future consideration, we need to state it here
- If someone going to add this functionality they should use this system instead of reinventing anything.
- BD: We can go to a "should" and not a "must" for this functionality. If going to support then they should use "pageList."
- GK: if not going to use the way it's defined in specification what are you proposing. All we need to do is say "Here is how you do it" within the spec.
- BD: felt it was a content change to support NCX and for reading devices.
- MG: We should add a paragraph to suggest we will make this a must in the next revision fo the spec
- Issue 28: Backing off of XML1.1
- concern of breaking existing files if we go to XML1.0
- XML 1.1 can still be processed by reading systems
- XML 1.1 content is deprecated. It is allowed but reader systems should not support it.
- Issue 23:
- Comment 6: Making of playOrder optional...(Mike to listen to recording here)
- If you use
4 Discussion of issues working towards resolution.
Minutes:
5 Update from Garth: Origins of Intitial Sets of EPUB Tests
Official W3C CSS Test Suites:
http://www.w3.org/Style/CSS/Test/
-- Selector.tests => follow "Selectors Release Candidate" link to:
http://www.w3.org/Style/CSS/Test/CSS3/Selectors/current/xhtml/index.html
W3C HTML/XHTML Test Suites: http://www.w3.org/MarkUp/Test/
-- html401.tests => follow "Current" link to "HTML Test Suite Tests" to:
