14:03:28 RRSAgent has joined #epub 14:03:28 logging to https://www.w3.org/2020/12/18-epub-irc 14:03:30 RRSAgent, make logs Public 14:03:31 please title this meeting ("meeting: ..."), ivan 14:03:51 ivan has changed the topic to: Meeting Agenda 2020-12-18: https://www.w3.org/mid/9F21D1E8-E174-49D2-BE12-BC0951CA67D4@gmail.com 14:03:52 Chair: wendy 14:03:52 Date: 2020-12-18 14:03:52 Agenda: https://www.w3.org/mid/9F21D1E8-E174-49D2-BE12-BC0951CA67D4@gmail.com 14:03:52 Meeting: EPUB 3 Working Group Telco 14:52:12 dauwhe has joined #epub 14:52:18 tzviya has joined #epub 14:54:53 present+ 14:58:00 MasakazuKitahara has joined #epub 14:58:52 CircularKen has joined #epub 14:58:56 LauraB__ has joined #epub 14:58:57 Avneesh has joined #epub 14:59:26 present+ 14:59:39 present+ 14:59:44 present+ 14:59:51 toshiakikoike has joined #epub 14:59:58 present+ 15:00:05 present+ 15:00:17 present+ 15:01:09 present+ 15:01:10 present+ 15:01:17 join later in video 15:01:26 present+ george 15:01:28 present+ zhengxu 15:01:34 CharlesL has joined #epub 15:01:37 present+ brady 15:01:45 duga has joined #epub 15:01:49 present+ laurent 15:01:54 present+ 15:01:56 present+ 15:01:58 present+ LauraB__ 15:02:08 laurent_ has joined #epub 15:02:13 present+ 15:02:53 George has joined #epub 15:03:01 zakim, pick a victim 15:03:01 Not knowing who is chairing or who scribed recently, I propose george 15:03:04 present+ 15:03:23 scribe: 15:03:38 scribe+ 15:04:05 dauwhe: I will chair. Any new people? 15:04:28 wendyreid has joined #epub 15:04:38 ivan: Admin stuff about rejoining 15:04:58 present+ 15:05:11 ... Grace period still in place for 45 days, but pull requests from orgs that have not rejoined will be flagged 15:05:14 q+ 15:05:26 Bill_Kasdorf has joined #epub 15:05:26 ... So please rejoin if you do actual work in the group 15:05:35 I hope it is not flagging Matt's PR 15:05:41 ack ge 15:05:41 dauwhe: This is due to the new patent policy change 15:05:58 George: Who does this? Personal or AC rep? 15:06:07 ivan: AC rep does it. 15:06:35 topic: in preperation to html5 in epub3 15:06:54 dauwhe: Reading systems and xhtml vs html 15:07:26 ... Thanks to those that already responded to their uses of xhtml vs html 15:07:41 Hadrien has joined #epub 15:07:46 ... Other RS vendors, please provide this information 15:07:48 present+ hadrien 15:08:18 present+ billk 15:08:25 q+ 15:08:27 ... I have tried a few via side loading and some of them work, but want a proper answer from everyone 15:08:31 ack geor 15:08:35 ... this is to inform discussion next year 15:08:57 George: DAISY contacted devs and asked about support of features 15:09:32 q+ 15:09:33 ... "we" [DAISY or the WG?] could take the list of known RSes and ask them about xhtml vs html 15:09:34 q+ 15:09:37 gpellegrino has joined #epub 15:09:41 ... or do we just want a feel 15:09:56 present+ 15:10:14 dauwhe: Just trying to get a feel to understand cost 15:10:18 ... so might be too soon 15:10:22 q+ 15:10:30 q+ 15:11:10 Garth has joined #epub 15:11:17 ivan: A little worried that DAISY might end up in the middle of a discussion it doesn't want to be in 15:11:21 ack ivan 15:11:51 ... it would be helpful if those contacts could be disclosed to the WG so we could contact them 15:11:56 q? 15:12:25 George: No problem, we can hand out the list, may need to ask a couple of people, but not a big deal 15:12:33 ack dug 15:12:54 duga: I don't think this is too early to start asking 15:12:54 duga: I don't think this is too early to start asking 15:12:57 :) 15:13:01 ... there's not too many RSs in this group 15:13:19 ... it's worthwhile to check in and let people know we're having this discussion 15:13:34 ... we need to reach out to the community 15:13:36 scribe+ 15:13:37 q? 15:13:41 ack laur 15:13:44 scribe+ 15:13:44 q? 15:14:09 Laurent_: this is a big change and we really need to ask about it now 15:14:11 q+ 15:14:39 ack tz 15:14:39 q? 15:14:42 ... less RSes can even support html5. The issue may not be cost, but will be RSes left behind that will never support html5 15:15:04 tzviya: Coming at this as publisher and dev experience from epubcheck 15:15:48 q+ 15:15:48 ... don't want to muddy the waters about content, but would be helpful to understand if the issue is supporting two types of books, or if it is making tools, etc 15:15:51 ack ha 15:15:55 ... want to know where the issues are 15:16:14 Hadrien: Worried about the consistency 15:16:36 ... We can either be more aligned with the web to make it easier to use html tools to build content, etc 15:16:44 ... or are we being conservative? 15:16:52 q+ 15:16:53 ... We seem to be doing both 15:17:20 ... We have been very conservative, now we are not with this discussion 15:17:41 ack gar 15:17:46 scribejs, issue 636 15:17:57 dauwhe: Good point, we aren't making a decisiion here, just want to understand where we are and where we might want to go 15:18:24 Garth: HTML serialization won't work out of the box, but doesn't mean we are against it 15:18:39 ... The issue about stuck in time RSes is a good one 15:18:57 q+ to comment on EPUBCheck 15:18:58 ... As is the issue about direction 15:19:10 ... But we also need to talk to publishers and see if they care 15:19:29 ack dau 15:19:37 ... Need to understand if RSes are willing to adapt, not understand what they do now 15:20:02 dauwhe: Let's get back on track. We aren't discussing the issue now, we are just preparing to discuss it 15:20:12 ack avn 15:20:12 Avneesh, you wanted to comment on EPUBCheck 15:20:45 Avneesh: Also please remember there is project to move epubcheck to the w3c html validator 15:21:06 ... if that prototype works, then it solves the problem of epubcheck not working with html5 15:21:17 ... second, it is good to start collecting data now 15:22:00 dauwhe: Need to do some boring stuff called work 15:22:02 topic: release identifier construction @issue 1440 15:22:02 https://github.com/w3c/epub-specs/issues/1440 15:22:29 zhengxu has joined #epub 15:22:41 ... The release identifier comes up from time to time (id + release time) 15:22:50 ... So you can figure out new vs update 15:23:11 ... This is really just advice to RSes on how to distinguish books 15:23:26 q+ 15:23:27 ... So really hard to test. How do you determine if there was an error? 15:23:31 q? 15:23:32 present+ zhengxu 15:23:42 q+ 15:23:45 ... Should this be in the appendix non-normatively? 15:23:46 ack ivan 15:23:57 q+ 15:24:05 ivan: Is it used ever by anyone? 15:24:19 q+ 15:24:22 dauwhe: That is my favorite question 15:24:22 ack had 15:24:41 Hadrien: Partial reply: There are roughly 2 groups of RSes 15:25:00 ... one where content always comes from a controlled warehouse (eg big retailers) 15:25:21 ... second is more generic that can support any type of epub 15:25:23 similar issue: https://github.com/w3c/epub-specs/issues/1310 15:25:37 ... this id makes more sense for the second group 15:26:17 q+ 15:26:17 q- 15:26:18 ... We are talking about unique id, but also saying maybe it isn't unique, so maybe don't rely on it. Very confusing for RS 15:26:23 q+ 15:26:31 ... we are building a spec that should work for all types of RSes 15:26:48 ... Personally know that some RSes in the second group do use that id 15:27:17 ack garth 15:27:19 ... Recs about looking at title is often wrong (eg if the change was to fix the title) 15:27:49 q+ 15:27:51 Garth: We are mostly a retailer, but also allow side loading. We ignore it. 15:27:52 ack iv 15:28:19 ivan: Need to be careful, there are two notions the UID and the release ID 15:28:35 ... This creates an identifier based on some info in the epub 15:28:42 q? 15:28:47 ... this issue is whether that algo makes sense 15:29:09 ack dau 15:29:16 Hadrien: If this is specifically about release id, then I don't know who is using it 15:29:23 ... UID is different answer 15:29:38 s/We ignore it./We ignore both the UID and the mod date-time./ 15:29:39 dauwhe: Not discussing removal of id or release date 15:29:58 q+ 15:30:26 ... This is about uniqueness of UID, what happens when two books have the same UID, etc 15:30:40 q+ 15:30:44 ... We probably don't want to start dictating how RSes present their libraries 15:30:47 ack ken 15:30:50 ack circ 15:31:01 ... I would say we remove this concept since it can't really be tested 15:31:05 +1 15:31:08 +1 to dauwhe 15:31:20 ken: Maybe have a revision number? 15:31:33 ... to make it clear there is id and version explicitly 15:31:49 s/ken/circularken/ 15:32:03 ack ha 15:32:13 Hadrien: But that is the issue at stake 15:32:18 q? 15:32:24 ... epub 2 only had uid 15:32:35 ... this was added in epub 3, but isn't really used 15:32:51 ... first group doesn't really care, and second group doesn't handle versioning at all 15:33:02 q+ to not go down the version/revision rabbit hole 15:33:28 ... don't think we should be in the business of specifying how these are used 15:33:43 q? 15:33:55 ack zhe 15:33:55 q+ 15:34:00 ... Would like to not say anything about UID, just say what it is and leave it to the RS implementors to figure it out 15:34:39 q+ To propose that it seems we're on the same page re mod date/time; baby step remove that? 15:34:45 ack tz 15:34:45 tzviya, you wanted to not go down the version/revision rabbit hole 15:34:49 jeff: Will be very difficult to test something that is undefined 15:35:07 tzviya: Want to caution about versions and revisions 15:35:11 q+ 15:35:29 ... Not changing too much in the spec is good guidance 15:35:46 ack gp 15:35:52 ... There has been a lot of discusion about rev vs version, don't want to take it up here 15:35:57 q+ 15:36:10 gpellegrino: Publishers don't seem to use this, we use ISBN and file hashes 15:36:13 ack gar 15:36:13 Garth, you wanted to propose that it seems we're on the same page re mod date/time; baby step remove that? 15:36:51 Garth: We seem to agree that release ID is not really used, and even if it is doesn't need to be in the spec 15:37:08 ... So we seem to agree on this issue 15:37:58 dauwhe: Makes sense. We won't comment on metadata construction in the specs 15:38:18 ack ivan 15:38:19 ... proposal would be to remove that language without touching required metadata 15:38:43 ivan: Need to be careful about how this is phrased 15:39:05 ack dau 15:39:06 ... are we proposing removal or moving to non-normative section/document 15:39:20 ... Also DC terms has a version term, so we have that too 15:39:44 ... May want to mention it, but no reason why it couldn't just be used 15:40:02 ... But I propose that dauwhe propose something 15:40:23 dauwhe: [typing noises] 15:40:37 Proposal: remove language around the concept of a release identifier, while retaining the mandatory unique ID and dcterms:modified metadata 15:40:51 ... I don't there is a compat issue here 15:41:14 ... don't think there is any testable change here 15:41:17 +1 15:41:38 +1 15:41:39 ivan: We can say any valid 3.2 will be valid with 3.3, this change does not alter that 15:41:46 +1 15:41:50 dauwhe: This is basically editorial 15:41:50 +1 15:41:51 +1 15:41:55 +1 15:42:05 +1 15:42:07 +π 15:42:07 ... Doesn't change behavior or authoring 15:42:15 +1 15:42:24 +1 15:42:29 +1 15:42:33 +1 15:43:08 +1 15:43:14 dauwhe: Resolved! 15:43:29 Resolved: remove language around the concept of a release identifier, while retaining the mandatory unique ID and dcterms:modified metadata 15:43:44 https://github.com/w3c/epub-specs/issues/1310 15:43:51 ... next 1310 15:44:02 Topic: Non-unique unique identifiers and reading system conformance @issue 1310 15:44:31 dauwhe: the spec says "Reading Systems MUST NOT depend on the Unique Identifier being unique to one and only one EPUB Publication. Determining whether two EPUB Publications with the same Unique Identifier represent different versions of the same publication (see Release Identifier), or different publications, might require inspecting other metadata, such as the titles or authors." 15:44:39 q? 15:44:44 q+ 15:44:56 ... Has no idea how to test this 15:45:24 ... Just make two books with the same UID and see what happens? 15:45:31 q+ 15:45:34 q+ 15:45:37 ... Seems like implementation advice 15:45:50 ... Would not be sad to see this go away 15:45:58 q+ 15:46:14 ack gar 15:46:38 ack iva 15:46:51 Garth: Concept is useful, maybe turn must to should, remove ref to release id and declare victory 15:47:13 ivan: Need to be careful about testability being the only criteria 15:47:16 +1 to ivan 15:47:50 ... when it comes to metadata, we can't necessarily depend on testability 15:48:02 q+ 15:48:08 q+ 15:48:16 q- 15:48:16 ... since eg libraries want metadata for their purposes we can't test, but we may still want to require it 15:48:32 ack wen 15:48:37 ... That is a general comment on using testable as a criteria 15:49:06 wendyreid: Think it is the case that we have more bad uids than correct ones 15:49:39 ... Create our own uids since they are better than what we get 15:49:44 q+ 15:50:01 dauwhe: Maybe move to a note? 15:50:02 q- 15:50:08 ... non-normatively 15:50:17 q+ 15:50:22 ... Which also solves the testing issue 15:50:37 +1 to Dave for making it a note (the 2 paragraphs, one about the "static" aspect and one about RS) 15:50:37 ack dauw 15:50:42 ack Bill 15:50:49 ... And cleans up the spec a bit 15:50:50 +1 to Dave 15:51:09 Bill_Kasdorf: We have a combo of a spec with recommended practice 15:51:45 ... These are often kept separate, prefer that since it keeps the spec only a spec, and allows for updating recs more easily 15:51:50 +1 to Bill / Dave 15:52:09 ack ivan 15:52:10 ivan: Trying to reconcile this. We have to be consistent with all the metadata 15:52:27 ... For instance author must be correct, but that is also untestable 15:53:12 q+ 15:53:19 ... May need to clarify for all metadata that it is required, and there is an implicit must, and give a blanket statement that any of it could be wrong 15:53:33 q+ For quick AOB at the end. 15:53:39 Proposal: make statement about reading systems not depending on uniqueness of unique ID a note rather than a normative statement 15:53:45 ack tz 15:54:03 tzviya: As a publisher, the way the metadata is currently is very clear 15:54:24 ... and while it is processed in different ways, this is a very easy part of the spec to understand 15:54:44 ... One major complaint is the spec is already too broken up 15:54:45 ack gar 15:54:45 Garth, you wanted to quick AOB at the end. 15:54:48 ... don't want to add to that 15:54:51 q+ 15:54:58 ack ha 15:55:15 Hadrien: prefer to make non-normative and also revisit the text overall 15:55:32 ... don't think it needs to exist at all 15:55:49 George_ has joined #epub 15:56:01 dauwhe: Two proposals - 1 make it non-normative or 2 remove entirely 15:56:48 Garth: If we make it non-normative it might be rewritten 15:57:05 +1 15:57:12 1 15:57:13 2 15:57:16 1 15:57:19 dauwhe: vote 1 for non-normative, 2 for remove, 0 to abstain 15:57:24 0 15:57:25 1 15:57:26 1 for George 15:57:26 2 15:57:27 George: 2 15:57:27 1 15:57:29 +1 (make non-normative; shrink hopefully; but retain at least the concept) 15:57:32 1 15:57:36 +1 15:57:40 1 15:57:43 1 15:57:44 1 15:57:45 +1 to Garth 15:57:56 +1 15:58:07 q+ 15:58:14 ack iva 15:58:40 +1 to Ivan 15:58:52 ivan: Can we agree to make non-normative and request new, shorter text? 15:59:02 ... then vote on the new text later 15:59:18 all: rumblings of assent 15:59:32 Resolved: make statement about uniqueness of unique ID in #1310 non-normative 16:00:11 Garth: Volunteer audio books time slot. Something about moving back two hours 16:00:24 dauwhe + wendyreid: chairs will discuss 16:00:40 dauwhe: Thanks for actual progress! 16:01:16 LauraB__ has left #epub 16:01:27 zakim, end meeting 16:01:27 As of this point the attendees have been dauwhe, ivan, LauraB__, MasakazuKitahara, CircularKen, toshiakikoike, Avneesh, zhengxu, tzviya, george, brady, laurent, CharlesL, duga, 16:01:30 ... laurent_, wendyreid, hadrien, billk, gpellegrino, π 16:01:30 RRSAgent, please draft minutes 16:01:30 I have made the request to generate https://www.w3.org/2020/12/18-epub-minutes.html Zakim 16:01:32 I am happy to have been of service, ivan; please remember to excuse RRSAgent. Goodbye 16:01:36 Zakim has left #epub 16:01:41 laurent_ has left #epub 16:14:46 gpellegr_ has joined #epub 16:24:18 gpellegrino has joined #epub 16:29:10 CharlesL has left #epub 17:27:29 zhengxu has joined #epub 17:30:10 dauwhe has joined #epub 18:08:37 ivan_ has joined #epub 20:40:32 dauwhe has joined #epub 22:25:59 dauwhe has joined #epub