<dauwhe> RRSAgent: make logs public
<dauwhe> title: Publishing Business Group Telecon
<RickJ> excellent!
<RickJ> in the spirit of worldcup, dauwhe needs to yell SCORE when it happens!
<dauwhe> scribenick: dauwhe
liisamk: epubcheck RFP
... we're working on the website, we're working on funding
levels
questions?
makoto: have you received applications or questions yet?
RickJ: I haven't heard of any questions
liisamk: we heard there were
three or four parties interested in responding
... has anyone heard of any more?
[silence]
brian: we had done three things
to promote the rfp
... 1. repost Rachel's update as part of our email feed
... 2. mentioned in a webinar that Tzviya led on
DPUB-ARIA
... so we've raised awareness in the US market
liisamk: any other Qs on the RFP?
dmitry: on subject of RFP, we
became aware last week, so we're a bit behind but trying to
catch up
... Evident Point has been working with BillM and Readium since
the beginning
... one of the largest contributors to readium
... we're excited to contribute to EPUBcheck if we can
... I'm compiling a list of questions, but it's not ready
yet
... who should I contact?
liisamk: you could send it to Luc, Rick, and I, and we will make sure it gets to the right folks
makoto: we have started to
receive registrations, but no submissions yet
... I will contact japanese publishers to encourage
presentations
... and I've heard about a taxonomy of visual effects in
Manga
... so things are moving, but we need to attract more attendees
and presentations
liisamk: do you think you'll get enough participation from other parts of the world?
MURATA: we should publish some
early programs when we receive submissions
... Florian has contacted CSS experts about inviting them to
Japan
<brian> BISG is happy to promote the program in the U.S.
MURATA: I hope to have more
people from US and European publishers
... are there events in the US around these topics?
... if you present at such a conference, please mention this
workshop
liisamk: can international coordination can help?
Bill_Kasdorf: I'm on the agenda later, I can discuss then
liisamk: any other questions?
<liisamk> dauwhe: draft has gone well and ready to get comments from all over the world
<liisamk> ... at the stage where we need outside input
<liisamk> ... hoping to have a months long formal review period to collect feedback and respond individually
<liisamk> ... then ask the business group to publish as a formal community group note
<MURATA> +q
<liisamk> ... then EPUB 3.2 will be a thing
MURATA: I posted an email about
further maintenance of the EPUB 3.X family
... in my opinion we should publish errata or in-place
revisions or even 3.3, for example for adding core media types,
fixing bugs, etc.
... I would like to have a maintenance plan
<liisamk> dauwhe: agree and community group will continue to maintain it and need to figure out that process
<liisamk> ... interest from several quarters about possibly moving the work to a rec track
<liisamk> ... short term goal is to move to finishing 3.2 and publishing as a community group note
<MURATA> +1
RickJ: On this topic, it's going
to be critical to sync up with the epub roadmap
conversations
... get people to move to 3.2, and to understand the time frame
of 4.0
<MURATA> +q
RickJ: these conversations should be syncronous, and syncronicity-ish :)
MURATA: responding to Rick's question, I think we should announce our plan for maintenence and development of both the EPUB 3 family and the EPUB 4 family
<brian> We are living in a synchronicity-ish world
MURATA: for some remaining issues for epub 3.2, we can't make a sensible decision without knowing the future plans. For example, adding core media type (such as OPUS)
RickJ: I agree :)
... EPUB 3.2 is an announcement to the world of the maintence
of EPUB 3 family
... and that we will keep going
dauwhe: we don't know what EPUB 4 is going to be like
<MURATA> +q
liisamk: any further comments?
MURATA: the future of the PWG is
not quite clear
... we can announce something about parallel development to the
world. We will work on 3 and 4 simultaneously
liisamk: we agree
... we can add things to 3 as needed before 4 comes out
Bill_Kasdorf: another elephant in
the room is that EPUB 4 will not be backward compatible with
EPUB 3.X
... in the future both will exist
... there's some disagreement on whether EPUB 4 should replace
EPUB 3
dauwhe: that's not the working group's choice. It's the market's choice, as with EPUB 2
Bill_Kasdorf: It's likely EPUB 3.X will persist
liisamk: much depends on whether
what we develop with 4 can be upgraded
... that you can picture how you can transition content from 3
to 4
... any further comments?
<brian> scribenick: brian
liisa mk: update on the audio TF
[silence]
liisamk conversation with steering committee- working on standards and packaging
scribe: light lift to make pub
package out of files received
... concern expressed that the business model may not be fully
developed
... encourages anyone interested to join the audio TF
bill_kasdorf observation that audio standards are 'chaotic'
brian: will work this into the BISG metadata recipient summit in Nashville on July 25
liisamk: update on EPUB roadmap
TF
... why EPUB 2 is obsolete
... then, focus on value of EPUB 3
... EPUBCheck support for EPUB 2 may be discontinued
... white paper in development; looking for resources and
channels to spread the word
... synchronize release of white paper with update and move to
EPUB 3.2
... EPUB 3.2, white paper, release of EPUBCheck released more
or less at the same time this fall
<RickJ> +1
liisamk: update on external coordination TF
bill_kasdorf: real progress on
objectives
... promote RFP and fundraising appeal
... developed a spreadsheet of relevant orgs by geography and
areas of interest
... identified contacts, TF member to 'own' the
relationship
... request to share spreadsheet with PBG; some disagreement
within TF on doing that
... have added members and country contacts in last few
weeks
... question: should the contacts be made available to PBG
chairs?
... other approach: relationship owners can reach out.
Bill_Kasdorf leaning in that direction
... additional information: Manga workshop, EPUB 3.2 review.
How to best handle communication?
... PBG preference on how to do outreach?
liisamk: pros and cons for both
centralized = faster
liisamk: OTOH, respond better/faster to outreach from someone you know
bill_kasdorf: centralizing means you know when it is all done
liissamk: agreed
bill_kasdorf: may be an argument
to do both, on a case-by-case basis
... fundraising and RFP from PBG chairs
... external communications TF to follow up with personal
appeal
liisamk: like this idea
... awareness from PBG, then follow up
<RickJ> +1 to "both"
bill_kasdorf: any disagreements?
[silence, except for maybe a canine]
bill_kasdorf: will communicate support for two-part approach to the external outreach TF
juninho_yoshii: agrees with bill_kasdorf
bill_kasdorf: feels the external outreach TF was a good investment. Asks makoto to put together a call for proposals that can be sent to other organizations
<MURATA> https://www.w3.org/publishing/events/tokyo18-workshop/cfp
murata: suggests sending the link to interested/potentially interested parties
liissamk: any other questions
[none]
... any other topics [none]
... have a lovely day/evening. Happy Independence Day for those
who celebrate
... end}
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Present: dauwhe RickJ liisamk jyoshii Bill_Kasdorf brian makoto Found ScribeNick: dauwhe Found ScribeNick: brian Inferring Scribes: dauwhe, brian Scribes: dauwhe, brian ScribeNicks: dauwhe, brian WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting WARNING: Could not parse date. Unknown month name "07": 2018-07-03 Format should be like "Date: 31 Jan 2004" WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 People with action items: WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]