14:13:38 <RRSAgent> RRSAgent has joined #dpub
14:13:38 <RRSAgent> logging to http://www.w3.org/2015/09/28-dpub-irc
14:13:40 <trackbot> RRSAgent, make logs public
14:13:40 <Zakim> Zakim has joined #dpub
14:13:42 <trackbot> Zakim, this will be dpub
14:13:42 <Zakim> I do not see a conference matching that name scheduled within the next hour, trackbot
14:13:43 <trackbot> Meeting: Digital Publishing Interest Group Teleconference
14:13:43 <trackbot> Date: 28 September 2015
14:13:48 <ivan> zakim, code?
14:13:48 <Zakim> I have been told this is WebEx https://mit.webex.com/mit/j.php?MTID=m09c698f2da7d2f28d301b85cf2d76b08 with password dpub, dial in 644 278 410
14:14:08 <ivan> Agenda: http://www.w3.org/mid/5605A7A8.8090603@gmail.com
14:14:18 <ivan> Chair: Markus
14:15:06 <ivan> Regrets: Tzviya, Leonard, Vladimir, Alan, Jeff, Luc
14:20:14 <rego> rego has joined #dpub
14:31:15 <rego> rego has joined #dpub
14:42:15 <rego> rego has joined #dpub
14:51:16 <rego> rego has joined #dpub
14:53:10 <mgylling> mgylling has joined #dpub
14:57:25 <brady_duga> brady_duga has joined #dpub
14:57:50 <dauwhe> dauwhe has joined #dpub
14:58:50 <dauwhe> present+ Dave_Cramer
14:59:08 <pkra> pkra has joined #dpub
14:59:13 <brady_duga> present+ duga
14:59:59 <HeatherF> HeatherF has joined #dpub
15:00:17 <rego> rego has joined #dpub
15:00:29 <HeatherF> present+ Heather_Flanagan
15:00:37 <dkaplan3> dkaplan3 has joined #dpub
15:00:58 <ivan> Present+ ivan
15:01:20 <dkaplan3> present+ Deborah_Kaplan
15:01:20 <mgylling> Present+ Markus
15:01:38 <pkra> Present+ Peter Krautzberger
15:02:44 <Bill_Kasdorf> Bill_Kasdorf has joined #dpub
15:03:14 <mgylling> zakim, pick a victim
15:03:14 <Zakim> Not knowing who is chairing or who scribed recently, I propose Markus
15:03:22 <dauwhe> LOL
15:03:26 <pbelfanti> pbelfanti has joined #dpub
15:03:28 <pkra> O:-)
15:03:31 <mgylling> zakim, pick a victim
15:03:31 <Zakim> Not knowing who is chairing or who scribed recently, I propose Dave_Cramer
15:03:47 <Bert> Bert has joined #dpub
15:03:54 <ivan> zakim, who is here?
15:03:54 <Zakim> Present: Dave_Cramer, duga, Heather_Flanagan, ivan, Deborah_Kaplan, Markus, Peter, Krautzberger
15:03:56 <Zakim> On IRC I see Bert, pbelfanti, Bill_Kasdorf, dkaplan3, HeatherF, pkra, dauwhe, brady_duga, mgylling, Zakim, RRSAgent, shepazu, Karen, ivan, liam, iank, astearns, plinss, trackbot
15:03:57 <dauwhe> scribenick: dauwhe
15:04:01 <pbelfanti> Present+
15:04:07 <Bert> Present+ Bert
15:04:07 <dauwhe> mgylling: let's get going
15:04:08 <Bill_Kasdorf> Present+
15:04:14 <mgylling>  http://www.w3.org/2015/09/21-dpub-minutes.html
15:04:16 <dauwhe> ... first order of business is to approve minutes
15:04:22 <TimCole> TimCole has joined #dpub
15:04:22 <ivan> zakim, who is here?
15:04:22 <Zakim> Present: Dave_Cramer, duga, Heather_Flanagan, ivan, Deborah_Kaplan, Markus, Peter, Krautzberger, pbelfanti, Bert, Bill_Kasdorf
15:04:22 <dauwhe> ... any objections?
15:04:24 <Zakim> On IRC I see TimCole, Bert, pbelfanti, Bill_Kasdorf, dkaplan3, HeatherF, pkra, dauwhe, brady_duga, mgylling, Zakim, RRSAgent, shepazu, Karen, ivan, liam, iank, astearns, plinss,
15:04:24 <Zakim> ... trackbot
15:04:27 <dauwhe> [silence]
15:04:35 <dauwhe> ... minutes are approved
15:05:02 <dauwhe> ... we'd spend one of these telecons on the glossary (foreboding music plays in background)
15:05:17 <dauwhe> ... we want to get to a FPWD
15:05:25 <mgylling> http://www.w3.org/dpub/IG/wiki/Glossary
15:05:27 <dauwhe> ... the intent is it will be an IG note eventually
15:05:46 <dauwhe> ... Ivan, what's your view of where we're at?
15:06:01 <ivan> -> http://w3c.github.io/dpub-pwd/ Editor's draft of the new EPUB+WEB document
15:06:05 <Julie_Morris> Julie_Morris has joined #dpub
15:06:12 <dauwhe> ivan: So, where should we start?
15:06:15 <Karen> present+ Karen
15:06:16 <Julie_Morris> present + Julie_Morris
15:06:28 <dauwhe> ... there were two reasons
15:06:34 <HeatherF> He fades in and out for me, too
15:06:49 <dauwhe> ... why this issue on glossary was important
15:06:49 <TimCole> Present+ Tim_Cole
15:07:03 <dauwhe> ... one is what Markus said; we had to produce a new version of EPUB+WEB document
15:07:11 <dauwhe> ... since it will be a public note of the IG
15:07:19 <dauwhe> ... but there was also another issue
15:07:32 <dauwhe> ... this is more coming from the web community rather than the community here
15:07:45 <dauwhe> ... from webdevs and browser folk
15:07:53 <dauwhe> ... why do we need anything at all?
15:08:06 <dauwhe> ... why do publishers need anything else other than what the web already provides?
15:08:16 <dauwhe> ... we have been publishing web pages for 20 years!
15:08:28 <dauwhe> ... we have to be very clear in what we are talking about
15:08:38 <dauwhe> ... we are not talking about gmail pages
15:08:51 <dauwhe> ... difference between publishing and web at large
15:09:00 <dauwhe> ... so this led to the discussion I started a while ago
15:09:08 <dauwhe> ... and that's what's now in the glossary page
15:09:16 <rego> rego has joined #dpub
15:09:27 <dauwhe> ... I put up some initial things
15:09:50 <dauwhe> ... I naively put up some definitions for document / publication
15:09:59 <dauwhe> ... that led to a thread
15:10:18 <dauwhe> .. with more than a hundred emails on a specific topic
15:10:41 <dauwhe> ... talking about portable web things
15:10:54 <dauwhe> ... we did reach equilibrium when talking about portable web documents
15:11:04 <dauwhe> ... do we want to get into details?
15:11:10 <dauwhe> mgylling: yes, we should get into details
15:11:29 <dauwhe> ivan: the goal was to define a class of documents
15:11:40 <dauwhe> ... web pages or collection of web pages that work on and offline
15:11:54 <dauwhe> ... we had start with more fundamental things
15:12:00 <dauwhe> ... started with concept of web resource
15:12:03 <dauwhe> ... a very general thing
15:12:15 <dauwhe> ... a thing on the web that can be identified by a URI
15:12:29 <dauwhe> ... and can be accessed by various protocols
15:12:42 <dauwhe> ... we also needed something called essential content
15:12:56 <dauwhe> ... dkaplan was great in finding out these terms were defined in a11y
15:13:10 <dauwhe> ... part of web pages are really important for the message
15:13:19 <dauwhe> ... some parts are "nice to have" but less important
15:13:25 <dauwhe> ... example:
15:13:49 <dauwhe> ... font statements. In most cases it's OK if the user agent picks one of the fonts
15:13:59 <dauwhe> ... but if book is on typography the font might be essential
15:14:12 <dauwhe> ... the next step is we define a web document
15:14:28 <dauwhe> ... we don't concentrate on one single file
15:14:39 <dauwhe> ... but a set of resources that together is an identifiable thing
15:14:45 <dauwhe> ... like a scholarly article or a book
15:14:54 <dauwhe> ... one or more html pages, svg, js, etc
15:15:01 <dauwhe> ... it's that set which is the central notion
15:15:11 <dauwhe> ... has it's own URI
15:15:17 <dauwhe> ... that's one of the central concepts
15:15:22 <mgylling> q?
15:15:38 <dauwhe> ... there are a number of qualifiers of what web doc should look like
15:15:43 <dauwhe> ... if the tech around us changes
15:15:56 <dauwhe> ... so we get poorer environment or smaller screen
15:16:08 <dauwhe> ... we should get graceful degradation but keep essential content
15:16:26 <dauwhe> ... there are smaller discussions between Bill K. and I around web document vs web publication
15:16:33 <brady_duga> q+
15:16:33 <dauwhe> mgylling: there's an issue in the tracker
15:16:41 <dauwhe> ivan: there are some minor forumulation issues
15:16:54 <dauwhe> ... final point is that we define what it means to be portable
15:17:05 <dauwhe> ... because a web doc can be a collection of all kinds of resources
15:17:26 <dauwhe> ... I may have a dependency on some CSS file on the other side of the globe
15:17:33 <dauwhe> ... so there's an issue of portability
15:17:46 <dauwhe> ... the user agent can render the essential content of the document in such situations
15:17:49 <mgylling> q+
15:17:52 <dauwhe> ... then there's a portable web document
15:18:06 <dauwhe> ... this is where we are carving out the things that are on the web
15:18:16 <dauwhe> ... there is an equilibrium point on these terms
15:18:17 <rego> rego has joined #dpub
15:18:23 <dauwhe> ... there are some details to be discussed
15:18:28 <mgylling> q?
15:18:35 <dauwhe> ... before we get into the questions
15:18:47 <dauwhe> ... Deborah was a great participant in this discussion
15:18:55 <dauwhe> ... Leonard has sent regrets
15:19:05 <dauwhe> dkaplan3: that was a good summary
15:19:06 <ivan> q?
15:19:09 <mgylling> ack brady
15:19:11 <dauwhe> ... and of the points that are still pending
15:19:32 <dauwhe> brady_duga: how is our definition of web document different from other definitions
15:19:43 <dauwhe> ivan: which other definition are you referring to?
15:19:46 <dauwhe> brady_duga: OK
15:19:59 <dauwhe> ... if you just google web document wikipedia points to an old w3c spec
15:20:02 <dkaplan3> q+
15:20:09 <Bill_Kasdorf> q+
15:20:10 <dauwhe> ... and it sounds a lot of what we already did
15:20:22 <dauwhe> ivan: I think I remember dkaplan3 went through those
15:20:31 <dauwhe> dkaplan3: the problem is that it's not the same
15:20:31 <mgylling> ack dkaplan
15:20:39 <dauwhe> ... we're dealing with 2 industries
15:20:49 <dauwhe> ... with two different meanings for documents
15:20:56 <dauwhe> ... publishing is diff. than web at large
15:21:07 <dauwhe> ... the terms we came up with are not the same as what w3c has
15:21:16 <dauwhe> ... document as a resource
15:21:27 <dauwhe> ... a way of defining a particular package of bits
15:21:50 <dauwhe> ... document has intention, some intellectual thing attached unlike w3c definition
15:22:10 <dauwhe> ... we are doing this because we are publishers who use English in this way
15:22:22 <dauwhe> ... the web uses the same words in different ways
15:22:42 <dauwhe> ... so our definition should be different than w3c definition
15:22:52 <dauwhe> ivan: there is no widely accepted w3c definition
15:22:58 <dauwhe> ... they are not fundamental to w3c
15:22:59 <mgylling> ack mgylling
15:23:06 <dauwhe> mgylling: two questions
15:23:11 <dauwhe> ... web documents
15:23:30 <dauwhe> ... it strikes me that if you read it quickly it's not a very specific difference
15:23:42 <dauwhe> ... we should highlight identifiability
15:23:55 <dauwhe> ... you point it out, but only implicitly
15:24:06 <dauwhe> ... maybe one of the bullets should call that out
15:24:19 <dauwhe> ... "one URI" used to reference all the resources within the document
15:24:25 <dauwhe> ... that's quite explosive stuff
15:24:37 <dauwhe> ... there are 200 web pages that should be addressable by one URI
15:24:40 <mgylling> ack Bill
15:24:57 <dauwhe> Bill_Kasdorf: so pleased to hear Brady and Deborah say those things
15:25:03 <dauwhe> ... I'm coming from publishing side
15:25:11 <dauwhe> ... from the web side
15:25:26 <dauwhe> ... whether or not there's an authoriatiive definition from w3c
15:25:29 <dauwhe> ... the word is used a lot
15:25:37 <dauwhe> ... when we talk about heirarchy of headings
15:25:46 <dauwhe> ... the top level section is an h1
15:25:49 <dauwhe> ... the next is h2
15:25:53 <dauwhe> ... and that's in your document
15:25:59 <dauwhe> ... when you have a book with 20 chapters
15:26:05 <dauwhe> ... and each chapte is a document
15:26:14 <dauwhe> ... or a magazine with 20 independent articles
15:26:22 <dauwhe> ... the h1 has to be the title of the book
15:26:33 <dauwhe> ... I say no, my document is my chapter or article
15:26:36 <dauwhe> ... now we have a problem
15:26:43 <dauwhe> ... i think the web is saying
15:26:58 <dauwhe> ... that s the document but not the publication
15:27:10 <mgylling> q?
15:27:17 <rego> rego has joined #dpub
15:27:17 <dauwhe> ivan: just to make it clear
15:27:32 <dauwhe> ... what you would prefer
15:27:42 <dauwhe> ... is that we talk about web publications as a collection of resources
15:27:50 <dauwhe> Bill_Kasdorf: documents are parts of publications
15:28:01 <dauwhe> ... but a web pub could be a single document
15:28:07 <dauwhe> ivan: I am ok with both
15:28:22 <dauwhe> ... we need order in how we make such a decision
15:29:05 <dauwhe> ivan: I haven't seen any major change
15:29:16 <dauwhe> ... after a hundred emails I don't just make a change on the fly
15:29:33 <dauwhe> mgylling: we do have a quorum here today; we can barge ahead
15:30:18 <TimCole> q+
15:30:26 <pkra> dauwhe: tend to think of these things as: we make publications and split them up for historic reasons (limitations)
15:30:32 <pkra> ... mostly technical limitations.
15:30:34 <dkaplan3> q+
15:30:43 <pkra> ... e.g., html5 files
15:31:06 <dauwhe> Bill_Kasdorf: I know lots of people who make an entire book with a single content document
15:31:06 <pkra> (took over scribing a bit)
15:31:13 <mgylling> q?
15:31:29 <dauwhe> Bill_Kasdorf: it's clearer with magazines, where they are indepenent
15:31:30 <mgylling> ack TimC
15:31:43 <dauwhe> TimCole: with regards to bills last comment
15:31:52 <dauwhe> ... it's not just the way the content provider thing
15:32:02 <dauwhe> ... it's what needs to have identity
15:32:09 <dauwhe> ... like http URIs
15:32:28 <dauwhe> ... there may be a subsequent edition with a URI
15:32:46 <dauwhe> ... and there will people who will think of the two things together as a thing
15:32:56 <Bill_Kasdorf> +1 to the identity concept as critical
15:33:04 <mgylling> ack dkap
15:33:05 <dauwhe> ... we have to be careful
15:33:21 <dauwhe> dkaplan3: searching for the perfect word is not going to work
15:33:31 <dauwhe> ... just make it clear we define our terms in our namespace
15:33:40 <dauwhe> ... we'll be dealing with people who use terms different
15:33:46 <dauwhe> ... web folk will read "webbily"
15:34:00 <dauwhe> ... publisher who does lots of anthologies will look at collections
15:34:15 <dauwhe> ... the author of one essay will define their contribution as a document
15:34:36 <dauwhe> ... we can't find a word that will work across all the horizontals
15:34:44 <Bill_Kasdorf> q+
15:34:50 <mgylling> q?
15:34:54 <dauwhe> ... any product of DPUB uses the terms as definedd in this glossary
15:35:02 <dauwhe> ... this is a namespace problem
15:35:22 <mgylling> ack BillK
15:35:29 <dauwhe> Bill_Kasdorf: I agree with dkaplan3
15:35:44 <dauwhe> ... but if you agree we use it one way we can't use it the other way
15:35:50 <dauwhe> ... you invite confusion
15:35:53 <mgylling> q+
15:36:00 <ivan> ack Bill_Kasdorf
15:36:10 <dauwhe> ... the word document creates so much confusion
15:36:14 <mgylling> ack mgylling
15:36:17 <rego> rego has joined #dpub
15:36:21 <dauwhe> ... use publication as the aggretation
15:36:27 <dauwhe> mgylling: I agree with you dkaplan3
15:36:38 <dauwhe> ... in my world document is very loaded already
15:36:43 <dauwhe> ... a very specific thing in html
15:36:55 <dauwhe> ... we are maybe inviting more confusion than necessary
15:37:10 <dauwhe> ... but we should be very clear it's in our namespec
15:37:24 <dauwhe> ivan: if there is anyone who will mildly criticize me if I change to publication?
15:37:29 <TimCole> +1
15:37:30 <dkaplan3> +1
15:37:31 <pkra> +1
15:37:31 <ivan> +1
15:37:31 <HeatherF> +1
15:37:32 <mgylling> +1
15:37:33 <Bill_Kasdorf> +1 to publication
15:37:34 <brady_duga> +1
15:37:39 <dauwhe> mgylling: IRC poll--plus one if you want to change to publication
15:37:46 <Julie_Morris> +1
15:37:57 <dauwhe> ... why did we argue for ten minutes if we all agree? ;)
15:38:00 <pkra>  because Ivan is awesome.
15:38:00 <dauwhe> ivan: can i move on?
15:38:14 <dauwhe> ... what I also did is that I took the epubweb document
15:38:16 <david_stroup> david_stroup has joined #dpub
15:38:19 <mgylling> http://w3c.github.io/dpub-pwd/
15:38:26 <dauwhe> ... and I tried to use the new terminology
15:38:43 <dauwhe> ... we do want a FPWD
15:38:49 <dauwhe> ... it's no longer a white paper
15:39:13 <dauwhe> ... it would be helpful if you all could review this document and provide feedback and/or pull request
15:39:23 <dauwhe> ... havinga  stake in the ground is important
15:39:30 <dauwhe> ... the next term is not yet closed
15:39:42 <dauwhe> ... what is identifier
15:39:51 <dauwhe> ... do we mean URI
15:39:55 <dauwhe> ... do we mean something else
15:40:00 <dauwhe> ... how do we use these terms
15:40:06 <dauwhe> ... Bill_Kasdorf will love this topic
15:40:10 <dauwhe> ... let's not start now
15:40:18 <dauwhe> ... there is also the issue of semantics
15:40:24 <dauwhe> ... my background is in semantics
15:40:42 <dauwhe> ... maybe we want to have a clear idea of what we mean by semantics, metadata...
15:40:47 <dauwhe> ... even in world of metadata
15:41:02 <Bill_Kasdorf> Re "semantics," I think we should clearly make the distinction between "structural semantics" and "content semantics."
15:41:22 <dauwhe> ... the pub world using the term reading system
15:41:30 <dauwhe> ... web world talks about browsers
15:41:50 <dauwhe> ... we should settle this for the future
15:42:05 <dauwhe> ... state of a portable web publication
15:42:10 <dauwhe> ... we talked about offline and online
15:42:15 <Bill_Kasdorf> Re reading system vs. browser, how about "renderer" or "rendering agent"?
15:42:22 <dauwhe> ... we realize that there are two dimensions
15:42:43 <dauwhe> ... one is whether we talk about a set of web resrouces spread over filesystem or URI
15:42:53 <dauwhe> ... or whether they are packaged into one format/package
15:43:06 <dauwhe> ... for millions of reasons the notion of packageing is important
15:43:11 <dauwhe> ... for distribution etc
15:43:23 <dauwhe> ... the portable web is packaged or unpackaged... that's one dimension
15:43:34 <Bill_Kasdorf> e.g. a Braille rendering agent renders the publication in Braille (i.e., rendering doesn't need to mean visual, and we could define it as such in the glossary)
15:43:38 <dauwhe> ... the other area is online vs offline and what it really means
15:43:54 <dauwhe> ... its not clear what we mean by offline and online
15:44:10 <dauwhe> ... could be http online vs no http offline but that's not true
15:44:14 <dauwhe> ... I could use localhost
15:44:26 <dauwhe> ... how do these things relate?
15:44:35 <dauwhe> ... if we use on/offline we run into issue
15:44:54 <dauwhe> ... I say what's important we HTTP-based protocols or filesystem protocols
15:45:05 <dauwhe> ... whether HTTP is local or not is less interesting
15:45:06 <Bill_Kasdorf> +1 to the distinction between http vs. file system access
15:45:22 <dauwhe> ... I would ask brady_duga
15:45:22 <mgylling> q?
15:45:29 <dauwhe> ... in both cases we had Leonard
15:45:46 <dauwhe> brady_duga: why is it important to determine which protocol accesses things
15:45:59 <dauwhe> ... as a user the question is whether the pub is completely available
15:46:05 <dauwhe> ...how I access that doesn't matter
15:46:27 <dauwhe> ... you could have a remote publication
15:46:40 <dauwhe> ... I don't know what this distinction is important
15:46:44 <dauwhe> ivan: my feeling is
15:46:50 <dauwhe> ... when it comes to user agent side
15:46:58 <dauwhe> ... the architecture of the user agent
15:47:03 <dauwhe> ... things like service workers
15:47:08 <dauwhe> ... when we think about identifiers
15:47:17 <dauwhe> ... that's where the difference comes in
15:47:27 <dauwhe> ... i agree the distinction is unimportant for reader
15:47:33 <dauwhe> ... but important in how things are realized
15:47:41 <dauwhe> brady_duga: yes, for a browser that is true
15:47:47 <dauwhe> ... for a reading system
15:47:52 <dauwhe> ... there will be access issues
15:47:59 <dauwhe> ... they will have to do different things
15:48:03 <dauwhe> ivan: that's what I concentrate on
15:48:07 <mgylling> q?
15:48:07 <dauwhe> mgylling: OK
15:48:31 <dauwhe> ... what are pain thresold for FPWD?
15:48:40 <dauwhe> ... how much do we want to settle before FPWD
15:48:42 <dauwhe> ivan: two issues
15:48:54 <dauwhe> ... publication vs document, we solved that
15:49:20 <dauwhe> ... in the document I have added some additional wording on the kind of issue dkaplan3 alluded to, about context
15:49:25 <dauwhe> ... there is another aspect
15:49:41 <dauwhe> ... orthogonal to what we already did
15:49:58 <dauwhe> ... I tried to make the whole concept independant of EPUB
15:50:16 <dauwhe> ... the criticism was that it was describing EPUB4
15:50:43 <dauwhe> ... so I tried to make this weaker, although the dependance on EPUB is still there
15:50:53 <dauwhe> ... we don't want to provide a bad message to the industry
15:50:58 <dauwhe> ... there is a fine line there
15:51:25 <dauwhe> ... we don't know what Leonard wants to do
15:51:31 <dauwhe> ... that will happen this week
15:51:33 <mgylling> q?
15:51:39 <dauwhe> ... that's probably the biggest remaining issue
15:52:05 <dauwhe> ... once this is done we can publish a FPWD
15:52:06 <Bill_Kasdorf> fyi in discussions on the magazine side and separately on the journals side there is a strong desire to include file types in a publication that EPUB currently doesn't allow
15:53:15 <dauwhe> mgylling: for the other IG members, what kind of inputs would you want between now and FPWD?
15:53:25 <dauwhe> ivan: for FPWD, general review is good
15:53:32 <dauwhe> ... nothing specific
15:53:51 <dauwhe> mgylling: do we want to look at time here, given pub moratoriums around TPAC?
15:54:02 <dauwhe> ivan: I would love if there was an agreement on the content at the meeting next week
15:54:20 <dauwhe> ... because it's a fpwd the IG must resolve to publish
15:54:34 <dauwhe> ... we'll see if it can be done by next Monday
15:54:41 <dauwhe> ... still OK if it goes to the next Monday
15:55:13 <mgylling> q?
15:55:37 <pkra> non-benevolent?
15:55:46 <dauwhe> mgylling: since we have a few minutes left
15:55:56 <dauwhe> ... I'm looking at wiki
15:56:04 <dauwhe> ... next-to-last bullet confuses me
15:56:06 <mgylling> “A Web Resource in a Web Document is Portable if an OWP compliant user agent can render its essential content by relying essentially on the Web Resources within the same Web Document”
15:56:16 <dauwhe> ... this line confuses me
15:56:25 <dauwhe> ... the trailing end... what does it mean
15:56:36 <dauwhe> ivan: this means that when I produce a PWP
15:56:53 <dauwhe> ... all the things that are essential like CSS and JS are part of that portable publication
15:57:21 <dauwhe> ... an extreme case would be everything should be in the PWP, but things like fonts are perhaps not as essential
15:57:23 <dauwhe> mgylling: ok
15:57:44 <dauwhe> ... can a web resource be "without" a web document rather than "within"
15:57:51 <dauwhe> ivan: the web doc might refer to fonts
15:58:05 <dauwhe> ... are the font files themselves part of the web doc, or elsewhere on the web?
15:58:20 <dauwhe> ... it should be portable even if the fonts aren't with it
15:58:35 <dauwhe> ... but in some cases the font file must be part of the doc
15:58:40 <dauwhe> ... an epub example
15:58:44 <dauwhe> ... for some epubs
15:58:48 <dauwhe> ... a scientific book
15:59:01 <dauwhe> ... the data might have to be part of the book because I interact with it
15:59:08 <dauwhe> ... in other cases it's ok if the data is on the web
15:59:11 <dauwhe> mgylling: of course
15:59:28 <dauwhe> ... so you have a portable web doc exploded online
15:59:33 <dauwhe> ... so what does it mean then
15:59:41 <dauwhe> ivan: is it part of the set or not?
15:59:55 <dauwhe> ... everything that's necessary for that web document must be part of the set
16:00:06 <dauwhe> Bill_Kasdorf: can some be offline or online?
16:00:25 <dauwhe> ivan: then it's not portable
16:00:32 <dauwhe> mgylling: I'll try to clarify in an email
16:01:02 <dauwhe> All: thanks and bye
16:01:06 <dauwhe> [beep]
16:04:45 <brady_duga> brady_duga has joined #dpub
16:04:51 <ivan> rrsagent, draft minutes
16:04:51 <RRSAgent> I have made the request to generate http://www.w3.org/2015/09/28-dpub-minutes.html ivan
16:05:30 <ivan> trackbot, end telcon
16:05:30 <trackbot> Zakim, list attendees
16:05:30 <Zakim> As of this point the attendees have been Dave_Cramer, duga, Heather_Flanagan, ivan, Deborah_Kaplan, Markus, Peter, Krautzberger, pbelfanti, Bert, Bill_Kasdorf, Karen, Tim_Cole
16:05:38 <trackbot> RRSAgent, please draft minutes
16:05:38 <RRSAgent> I have made the request to generate http://www.w3.org/2015/09/28-dpub-minutes.html trackbot
16:05:39 <trackbot> RRSAgent, bye
16:05:39 <RRSAgent> I see no action items