Publishing Business Group Telco -- 13 Mar 2018

<garth> Scribe expectations set appropriately low.

<ivan> scribenick: garth

Luc: first item for EPUB 3.2 resolution

Principles for EPUB 3.2 proposal

Luc: Version 3.2; lots of work to do.
... Agree with princples? Or have comments?

<Julian_Calderazi> link: https://docs.google.com/document/d/1r2RbLipc5VY3vUp_iuPak3oaNxI5BF9gJ5s-98qsmEY/edit?ts=5a578c4c#heading=h.izdc9lnn3tf

<dauwhe> http://w3c.github.io/publ-epub-revision/epub32/spec/epub-spec.html

Luc: otherwise we’ll move to ask CG to proceed with work on EPUB 3.2 (with all due haste).
... Good concensus so far
... No Objections, it seems!
... Concensus on call; 72 hour notice to go out.

RESOLUTION: CG can go ahead, provided there is no objection within 72 hours

<Makoto> Who is going to lead the taskforce for this work in the CG?

<Bill_Kasdorf> s/there is an objection/there is no objection

Garth: can we get Matt to help with draft?
... how Matt is allocated?

George: Matt is 100% with Daisy.

Garth: Garth will reach out to Matt, for time availability.

George: Matt would likely want to work on this but A11Y?

<wolfgang> s/Geroge:/George:/

Dave: did first pass as draft, that’s what we’ll work from. Need issues to move forward.
... most development should move through gitbub

<Makoto> I was disconnected for a while.

Dave: Maybe kick-off meeting makes sense.

<ivan> +1 to George

George: we MUST say SHOULD :-)

<Makoto> Yes, I will!

George: (beware of W3C/ISO vocab differences)

new person on the call

Luc: Welcome Dan Fauxsmith?

<Julian_Calderazi> Welcome Dan! Good to have you here.

<ivan> scribejs, set Dan Dan Fauxsmith

DPUB Summit

Luc: Can anybody explain where we are with DPUB Summit
... in Berlin the 17th of May
... Book your rooms!

<BillM> https://www.edrlab.org/dpub-summit-2018/

Luc: 1:00p on 16th to 5:30p on the 17th
... Program on web site

<Makoto> I will be there.

<ivan> +1 Makoto!

<laudrain> +1

Luc: Daisy devices moving to EPUB 3 to be demoed.

BillM: W3C is co-sponsoring event

<Brian_> Conflicts with a BISG metadata summit in NY; unable to attend

BillM: Good general agenda and W3C-ish Publishing topics too
... Mix of (light) technical topcis and business too

<Julian_Calderazi> Makoto, u muted?

<Makoto> Windows 10 tries to block me.

Summit follows AC meeting Monday/Tuesday; Readium meeting 16th AM

epubcheck funding

Liisa: epubcheck funding
... Need to raise $90-$100K to get epubcheck to where it needs to be
... Maybe get 20-30 compaires to put in $3K+

<Makoto> I wanted to point out that there will be WHATWG people in the AC meeting. It would be a good chance for us to understand how we should contact WHATWG about HTML.

Liisa: do we need tiers of funding

Garth: no, for an amount that small.

<rkwright> Ric agrees with Garth

Luc: How will this be announced?

Liisa: Ric could work with a list of prospects.
... Should it just be a letter from this group

<Julian_Calderazi> Whatever might be needed as regards to design, count with me.

<rkwright> I believe Liisa means Rick, as in Rick Johnson

Liisa: How did we land on getting payment and storing payment

Brian: Tiers might be good… for a lead tier (maybe $25K)

<Bill_Kasdorf> +1 to Brian

Tzviya: brian makes a good point
... where do the checks go?

Garth: +1 to Brian’s single bigger tier

Liisa: need to settle how we’re going to deal with cash
... Nominate BillM for handling that

<laudrain> +1

Bill: will take that on and explore option

Tzviya: if Readium, need to make sure it looks good, relative to W3C taking over for IDPF

Laurent: is there a history of W3C do this sort of stuff: fundraising and paying for development

Ivan: not really

<tzviya> https://www.w3.org/International/sponsorship/

Ivan: general pushback against potential competition with member orgs
... some fundraising for general programs (e.g., mobile web initiative)

<tzviya> who funds https://validator.w3.org/?

Luc: Readium and EDRlab may make sense.

Laurent: yes, well could be

Luc: though announcements need to be clear

Julian: how long do we fundraise?

Liisa: until to get to $100K (semi smiley)

Tzviya: initial release in a month-ish, then start on EPUB 3.2
... then there is also general maintenance

Liisa: which is why were looking to have an annual budget

Ric: Folks may be taking HappyPills(tm) with said estimates
... it’s involved, and must be scoped and algile-ish

Luc: EPUB 3.2 is making it somewhat easier, due to compatibility with EPUB 3.0.1

Ric: suffers historically from too many cooks in the kitchen

Tzviya: Six months was allotted for general cleanup of code and test suite

Ric: happy to help refine

Luc: IDPF web site

IDPF Web site's fate

Luc: discussion about what to move where; A11Y resources move to Daisy?

George: problem with maintaining info in two different places; A11Y guidelines on IDPF site; ACE knowledge base
... should redirect to new ACE location

<scribe> … new ACE knowledge is newer and should no be with overlapping copyright (swith older IDPF stuff)

<Makoto> +q

Ivan: beyond A11Y…
... what do we do with the IDPF Web site?
... some pages should be deprecated there
... Keep some IDPF pages alive for W3C publishing?

<Makoto> Yes

<Makoto> I would like to point out that

<Makoto> EPUB 3.1 depends on some

<Makoto> registries at the IDPF site.

<Makoto> URLs are hardcoded in the specs.

ask rkwright

Ric: have been working on some Readium site work, with some light cloning from IDPF

<dauwhe> we've ported some IDPF documents to the CG github: https://w3c.github.io/publ-cg/

BillK: Some aux specs (e.g., indexes) could well move to be CG notes
... if still valid

Liisa: Should 3.2 not point to anything on IDPF site?

<Makoto> That's certainly possible.

Garth: likely good direction for 3.2

Ivan: but old URLs never die

<laurentlemeur> who's paying today for the IDPF domain name?

BillM: 3.2 referencing only W3C locations is a good plan
... IDPF.org should be considered more a static archive
... could move into some sort of static archive

<Makoto> We had http://idpf.org/epub/vocab/structure/ (ssv)

<Makoto> But it is redirected to https://idpf.github.io/epub-vocabs/structure/

Ivan: Package namespace is IDPF URI

<Makoto> We cannot change them.

BillM: epubzone isn’t continuing, W3C will be used instead.
... it was never normative, anyhow.

<Makoto> Redirection would work.

Ric: 1) URLs: redirection can help not break specs. 2) epubzone, some has migrated to Readium

Liisa: Noticed that forums on epubzone are still active and might be in need of monitoring

Ivan: Should use W3C blog for publishing stuff

External coordination TF

Luc: Task forces

<wolfgang> s/coordiantion/coordination/

BillK: email to Publishing BG late this week or early next (External Coordination task force) to call for participation
... stay tuned for email

A11y TF

Luc: A11Y TF call tomorrow

<Makoto> A11Y: BillM, did you speak with the W3C management about starting an EPUB accessibility project in ISO/IEC? Japan has created a draft for the required new work item proposal and is waiting.

Avneesh: A11Y awaiting resolution/direction

<Makoto> I think that I need "OK".

<Makoto> That's all.

<Makoto> Why no progress?

Luc: ISO — 3.0.1 now, start on 3.2 thereafter

<Makoto> Why no "OK" from the w3c m about an Iso/IEC project for EPUB A11Y?

<Makoto> No.

<Makoto> Independent.

BillM: 3.2 needs to be set. This should should recommend that “OK”.
... does it make sense to EPUB A11Y at ISO independantly of EPUB 3.2

<Makoto> I agree with Garth.

<Makoto> should be separated.

<dauwhe> scribenick: dauwhe

Avneesh: the proposal of separating epub a11y from EPUB 3.1 was due to the independence of accessibility
... now the situation has changed, and we need to rethink

<BillM> +1 to Avneesh

<Makoto> Yes!

<Makoto> Bye

laudrain: we need a call about ISO and a11y
... thanks all

- DRAFT -

Publishing Business Group Telco

13 Mar 2018

Attendees

Contents