<George> scribe+

<George> No new people.

<dauwhe> https://docs.google.com/document/d/1CTwQIhmsyXh0tpS6RLmLLeGDkO5JKHV1FdaXoh3CdXI/edit#heading=h.laz4kpa8h78l

<dauwhe> https://docs.google.com/document/d/1CTwQIhmsyXh0tpS6RLmLLeGDkO5JKHV1FdaXoh3CdXI/edit#heading=h.xibptsjp8k3e

<George> New EPUB feature incubation.

<George> It is useful to get us in what we need right now. The survey that is planned that should also help.

<George> These features are listed without judgement.

<George> Tzviya: process question.

<George> What would go with the incubator and what in the general publishing?

<George> Dave: Things that belong in EPUB should be here. It would be confusing to have it split across groups.

<Bill_Kasdorf> +1 to keeping EPUB issues including incubation in the EPUB3 CG

<dauwhe> scribe+ dauwhe

<dauwhe> George: one thing in my mind is virtual pages

<dauwhe> ... with textbooks that have a print equiv the page numbers are great

<dauwhe> ... but even if a book does not have a print equivalent

<dauwhe> ... it's useful to have those page references, and have an idea of how big the book is

<dauwhe> ... pages seem to be a good measure

<dauwhe> ... I think virtual pages is something that should be considered.

<dauwhe> ... Secondly, we should have a clear idea of how to do a bibliographic reference in an EPUB

<dauwhe> ... we're having to do print page numbers in bibliographies

<dauwhe> ... I'd want a way to do that with EPUB

<George> Dave: Virtual page numbers each reading system has something, but they are not interoperable.

<dauwhe> George: in some applications, when there is a pagelist you can tap on the item and it will switch from number of screens to showing the page numbers

<dauwhe> ... and in indexes I've seen, there are print page numbers that's linked to the page anchor

<dauwhe> ... by virtual page number I'm not talking about screens

<George> Dave: We would need some interoperable to do this.

<George> Bill: George's two suggestions are related. What George said as bibliographic reference is really formally called a citation.

<George> This would be extremely valuable.

<Zakim> tzviya, you wanted to recommend adding to list

<George> How we would put a fixed locator that is interoperable. We need a meaningful place in the document.

<George> Tzviya: Good idea, but add it as a place holder.

<George> Naomi:

<George> How large the chunks are should not be spected out.

<George> Avneesh: This discussion may not be so much about specification, but reusing what we already have. It may just require some speaking. It can then go in to best practices.

<George> Other thoughts about new features?

<George> Tzviya: Some are about systems support, do we plan to this as part of the spec?

<George> Dave: Some are in another working group, like CSS.

<George> So, it depends on where the work might take place.

<George> Rachel: We need to add other organizations on collaboration. IEEE for example is trying to develop standards.

<George> Naomi : Fixed layout and pop ups are an issue.

<George> Wolfgang:We want a RS to pop up a definition of a word.

<George> Naomi : There are RS built in dictionaries, and there are dictionaries that are title specific.

<Bill_Kasdorf> one of the satellite specs is about dictionaries and glossaries

<George> The title specific glossary should be supported.

<George> Tzviya: Pop ups and how to include them and making them accessible and we may need to interact with the ARIA WG.

<George> Dave: There is the satellite spec for dictionaries. It is already part of the charter to figure out what to do with these things.

<dauwhe> https://docs.google.com/document/d/1CTwQIhmsyXh0tpS6RLmLLeGDkO5JKHV1FdaXoh3CdXI/edit#heading=h.x1f9jp5q27fk

<George> Other deliverables

<tzviya> aria annnotations https://github.com/w3c/aria/issues/1109

<George> Test suite, how to help people who have questions, and best practices.

<dauwhe> George: in our epub and higher ed group

<dauwhe> ... we did a qa bot using Microsoft Azure

<dauwhe> ... this was focused on people who had general questions about epub, looking at adoption

<dauwhe> ... I think that tech is very interesting

<dauwhe> ... for solving the problem about people asking about EPUB

<dauwhe> ... and it helps create a database of questions which could be answered specifically

<dauwhe> ... just something interesting

<dauwhe> ... I could find a link to what we've done

<George> Dave: we need need somebody with a budget to help with these kinds of things.

<George> Tzviya: I am responsible with MDN.

<George> George is having problems with his computer, can somebody else scribe?

scribe+

dauwhe: Coordination with other groups
... the rest of the charter is more boilerplate stuff about participation
... how do we communicate
... text about W3C decision policy, patent policy for community groups, the idea of transparency
... conduct our technical work in public, internal email list
... how to choose chairs
... copy pasted from the prototype charter
... how we amend the charter
... less exciting things than virtual page numbers and pop-ups
... any comments?
... There's not much exciting stuff in the policy sections
... we've had a ton of great feedback on this document in general
... I've been working through the comments
... I will try to address the remainder
... not sure what the next steps are
... two external factors
... one is the results of the survey, and the other is decision on if EPUB should be rec track
... interest here and in the PBG
... where do we go from here?
... can we add more clarity to this or just address comments as they come up

Rachel: Our next step is to finalize this

dauwhe: We could absolutely go forward with this
... we do have a process for changing it

garth: You would think we finalize this and get it approved, get going, and then tune for any results from the survey and BG decisions?
... seems like a fine approach

Avneesh: I think this exercise has brought us key objectives
... from the community
... many things may change
... we have the meeting on the 24th of Feb
... we may go to rec track or remain with the CG, there's decisions that will influence this
... this document is a beautiful collection of objectives, and when we have clarity on the rec track, we can work from there

George: Having this as a draft, so we can refer to it
... so anyone contributing the survey doesn't feel that we aren't listening
... at least people could look at a more stable document
... help make the decisions on rec track
... having it semi-complete would be helpful

Rachel: That makes sense

dauwhe: Thanks everyone for participating
... I sent an email about EPUBCheck error codes, please help the developers

<garth> Thank you!

dauwhe: have a good day!

<dauwhe> RRSAgent: draft minutes

<dauwhe> RRSAgent: make logs public

<dauwhe> RRSAgent: make logs public

<dauwhe> RRSAgent: draft minutes

<dauwhe> RRSAgent: make logs public

This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/incubater/incubator/
Succeeded: s/are are/are/
Succeeded: s/locater/locator/
Succeeded: s/Namoe:/Naomi:/
Succeeded: s/tobest/to best/
Succeeded: s/aatelite/satellite/
Succeeded: s/infpluence/influence/
Default Present: George, dauwhe, wolfgang, toshiakikoike, Alex_Grover, tzviya, gpellegrino, Bill_Kasdorf, dkaplan, Avneesh, Naomi, CharlesL, Rachel, Garth, wendyreid
Present: George dauwhe wolfgang toshiakikoike Alex_Grover tzviya gpellegrino Bill_Kasdorf dkaplan Avneesh Naomi CharlesL Rachel Garth wendyreid dkaplan3
No ScribeNick specified.  Guessing ScribeNick: wendyreid
Inferring Scribes: wendyreid

WARNING: No "Topic:" lines found.


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

WARNING: Could not parse date.  Unknown month name "01": 2020-01-30
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: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


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.)