Digital Publishing Interest Group Teleconference -- 23 Sep 2013

<trackbot> Date: 23 September 2013

<ivan> Guest: Karen (karen) Myers, W3C

<scribe> scribe: tzviya

Markus opens meeting

Markus: today will discuss pagination task force
... first half discuss wiki entries
... social reading and annotations has come the farthest

<mgylling> http://lists.w3.org/Archives/Public/public-digipub-ig/2013Sep/0015.html

Markus: minutes approved
... new members
... Dave Cramer and Pierre Danet

Pierre: Pierre Danet of Hachette Livre
... business rep at W3C and involved in IDPF
... less technical and will be involved in use cases

Dave: Dave Cramer of hachette book group
... bagen with typesetter, got involved in XML, HBG shifted to EPUB 2 and EPUB 3, involved in industry groups

markus: logistics: TPAC is in November. we will meet there
... Visa takes time.

Agenda item: to new items on wiki http://www.w3.org/dpub/IG/wiki/UseCase_Directory

Markus: Rob to take us through new use cases in social reading

Rob: Annotating parts of embedded resources

<ivan> Pointer to the wiki

Rob: for example, point to just a rectangle within an image

Markus: does this include elements of hypertext

<madi> madi has joined from the UK

Rob: that is <span> - resources that the DOM references, not the DOM itself

<mgylling> http://www.w3.org/dpub/IG/wiki/Anno_Specific_6

Rob: http://www.w3.org/dpub/IG/wiki/Anno_Specific_6 - user wants to annotate two parts of a resource
... likely for comparison purposes
... requirement is multiple targets

Ivan: would this be a URI identifying multiple targets?

Rob: all that you need to do is add additional has target relationships (note: please make sure this is correct)

pdanet: is this used for text only?

Rob: no, several use cases involve elements other than text, such as image, video

<mgylling> http://www.w3.org/dpub/IG/wiki/Anno_Specific_7

Rob: annotate multiple parts or publications or resources within them
... but two parts come from different areas, e.g. one character that appears in multiple books (Bilbo in the hobbit and the lord of the rings)
... this is complicated and out (as Ivan noted)

Ivan: how do you uniquely identify a book?

<Pdanet> Yes, Ivan, it was Pierre

Rob: if products are off-line it is difficult to identify what a book is

Markus: IDPF will announce open anno project this week

<Pdanet> Sorry for my central Europe accent ))

<mgylling> http://www.w3.org/dpub/IG/wiki/Anno_Advanced_1

<mgylling> http://www.w3.org/dpub/IG/wiki/Anno_Advanced_2

Rob: cross format anno http://www.w3.org/dpub/IG/wiki/Anno_Advanced_1 - same content, different format

<fjh> annotations should be portable
...http: //www.w3.org/dpub/IG/wiki/Anno_Advanced_2 cross-version, anno maintained when version is updated
.....http: //www.w3.org/dpub/IG/wiki/Anno_Advanced_3 maintain style - incorporates CSS into annotations - don't loose the styling that was part of annotation
... similar in that don't lose annotation when shift layout
...http: //www.w3.org/dpub/IG/wiki/Anno_Advanced_5 - responsive design/content negotatiation with annotation

Pierre: what do you call the work ID?

Rob: the identity identifies the content irrespective of where it appears

Pierre: this does not really exist yet.

Markus: We realize this. We have to work with this to get annotations to work
... security use cases

Ivan: Please notify email group that have updated wiki when new use case added

Sharad: http://www.w3.org/dpub/IG/wiki/Security_UC#Security-1
... publisher would like information to be available offline on authorized machine
... requires encryption, authorization, decryption
...http: //www.w3.org/dpub/IG/wiki/Security_UC#Security-2
... client side use case
... user should have secure reader to access encrypted content

Markus: recommend removing EPUB from requirements as this is for OWP

<azaroth> +1 re W3C vs EPUB

Pierre: security rules are usually linked to business rules (number of pages, number of cookies...). Where are the details of the security process?

<karen> Tzviya: one of issues of DRM in past is that it can inhibit usability

<karen> ...whatever security is added should enable full usability

<karen> ...and as it relates to accessibility

Rob: this also impacts annotation
... if you quote text, will impact annotation
... a combined security/anno use case would be helpful

Markus: pagination task force
... Dave Cramer will lead
... define scope, priorities, and help in kicking this off for Dave
... We must not run out of time, so must focus on essential issues

Dave: how is what we are doing related to working CSS?

Markus: this is part of the risk. With the exception of few contributions, there has been little input from publishing
... we need to describe basic tenets of pagination

Dave

Dave: we are being media-agnostic
... working on CSS that will work in browsers, print, reading systems

+1 to media agnostic

thanks

<azaroth> +1

Markus: we will keep CSS WG in loop the whole time and ask for feedback
... one question for peter linss is who should liasons be?
... Alan Stearns and Elika
... have been working on fragmentation and column work
... Setting priorities: Clarify priorities of publishers is important

<azaroth> (@alanstearns at Adobe)

Markus: we have built prioritization into use case template, but that will not highlight critical elements
... this will also vary across publishing

Dave: people will tell you it's all critical

Peter: We may just need to gather a few things to throw at CSS WG first and see what can get done first

Markus: need an active team of contributors to work with Dave

Elka and Alan will hopefully participate

Dave: Would like to see someone from Pearson
... they have done work on 4C textbooks
... will go to Paul Belfonte

Ivan: Would still be helpful to give Karen pointers to non-W3C people who might be helpful

Markus: Alan Stearns of Adobe is very involved. What about organizations involved in IDPF?
... e.g. B&N or iBooks?

VitalSource

Markus: Is there a model in mind?
... Consider using the Japanese model

Dave: describe what should happen in every circumstance imaginable

<ivan> Requirements for Japanese Text layout

<plinss> http://www.w3.org/TR/jlreq/

Markus: this is also about concrete functional requirements
... e.g. is it enough to have headers and footers or do we need to transclude text?

Dave: it might make sense to start from typographic perspective because that is where the body of knowledge comes from
... then shift to OWP

Markus: we target to spend a lot of TPAC F2F on pagination
... to present whatever state our information is in at that point
... do we know whether we will meet with CSS WG at TPAC, Peter?

Peter: I will bring it up

Markus: meet with Dave to continue planning

<azaroth> Sorry for so many annotation use cases today, trying to do 3 or 4 a week so ended up with more than normal with the missed call

<ivan> trackbot, stop telcon

<trackbot> Sorry, ivan, I don't understand 'trackbot, stop telcon'. Please refer to <http://www.w3.org/2005/06/tracker/irc> for help.

<ivan> trackbot, end telcon

- DRAFT -

Digital Publishing Interest Group Teleconference

23 Sep 2013

Attendees

Contents

Summary of Action Items

Scribe.perl diagnostic output