00:33:55 <darobin> darobin has joined #dpub
01:53:37 <darobin> darobin has joined #dpub
07:56:28 <rego> rego has joined #dpub
09:27:48 <ivan> ivan has joined #dpub
09:41:48 <Guest_> Guest_ has joined #dpub
09:58:48 <Guest> Guest has joined #dpub
10:02:19 <rego> rego has joined #dpub
12:03:34 <rego> rego has joined #dpub
12:14:09 <ivan> ivan has joined #dpub
13:02:19 <Karen> Karen has joined #dpub
13:53:41 <Karen_> Karen_ has joined #dpub
13:53:50 <JakeA> JakeA has joined #dpub
13:54:17 <iank> iank has joined #dpub
13:55:21 <leaverou_away> leaverou_away has joined #dpub
13:56:03 <bigbluehat> bigbluehat has joined #dpub
13:56:39 <dauwhe_> dauwhe_ has joined #dpub
13:56:54 <liam> liam has joined #dpub
13:57:10 <Karen> Karen has joined #dpub
13:58:12 <astearns> astearns has joined #dpub
14:17:32 <darobin> darobin has joined #dpub
14:37:42 <ShaneM> ShaneM has joined #dpub
14:47:41 <tzviya> tzviya has joined #dpub
14:56:00 <ivan> ivan has joined #dpub
15:00:27 <ivan> trackbot, start telcon
15:00:29 <trackbot> RRSAgent, make logs public
15:00:29 <Zakim> Zakim has joined #dpub
15:00:31 <trackbot> Zakim, this will be dpub
15:00:31 <Zakim> I do not see a conference matching that name scheduled within the next hour, trackbot
15:00:32 <trackbot> Meeting: Digital Publishing Interest Group Teleconference
15:00:32 <trackbot> Date: 07 December 2015
15:00:39 <ivan> Chair: Tzviya
15:00:51 <ivan> Regrets+ Vladimir, Alan, Luc, Ben
15:01:17 <ivan> Agenda: http://www.w3.org/mid/97b55c50231d41969ce99f9144ca4e5a@CAR-WNMBP-006.wiley.com
15:52:00 <mattg> mattg has joined #dpub
15:53:03 <tzviya> present+ Tzviya
15:56:57 <clown> clown has joined #dpub
15:58:38 <brady_duga> brady_duga has joined #dpub
15:58:38 <clapierre1> clapierre1 has joined #DPUB
15:59:42 <dkaplan3> dkaplan3 has joined #dpub
15:59:53 <clapierre1> present+ Charles_LaPierre
16:00:05 <pkra> pkra has joined #dpub
16:00:31 <clown> present+ Joseph_Scheuhammer
16:00:47 <TimCole> TimCole has joined #dpub
16:00:56 <nickbarreto> nickbarreto has joined #dpub
16:01:25 <pkra> +present Peter Krautzberger.
16:01:37 <dkaplan3> present+ Deborah_Kaplan
16:01:47 <ivan> present+ Ivan
16:01:51 <NickRuffilo> NickRuffilo has joined #dpub
16:01:52 <TimCole> present+ Tim_Cole
16:01:52 <nickbarreto> present+ nick_barreto
16:01:59 <NickRuffilo> scribenick: NickRuffilo
16:02:00 <brady_duga> present+ duga
16:02:15 <Bill_Kasdorf> Bill_Kasdorf has joined #dpub
16:02:26 <danielweck> danielweck has joined #dpub
16:02:35 <tzviya> agenda: https://lists.w3.org/Archives/Public/public-digipub-ig/2015Dec/0061.html
16:02:38 <AylaStein> AylaStein has joined #DPUB
16:02:58 <Karen> present+ Karen
16:03:08 <Bill_Kasdorf> present+ Bill_Kasdorf
16:03:38 <tzviya> http://www.w3.org/2015/11/30-dpub-minutes.html
16:03:53 <NickRuffilo> Tzviya: "Comments on last week's minutes?  None...  Approved."
16:03:56 <dauwhe> present+ dauwhe
16:04:07 <ivan> Topic: DPUB Accessibility API mapping
16:04:24 <HeatherF> HeatherF has joined #dpub
16:04:33 <NickRuffilo> ...: "Digital publishing accessibilty API mapping"
16:04:41 <lrosenth> lrosenth has joined #dpub
16:04:47 <HeatherF> present+ Heather_Flanagan
16:04:58 <lrosenth> present+ Leonard_Rosenthol
16:05:02 <pkra> :)
16:05:07 <Bert> present+
16:06:40 <NickRuffilo> Tzviya: "Joseph does a lot of work for ARIA working group on the accessibility API."
16:06:43 <AylaStein> * So what is the password?
16:06:51 <AylaStein> thanks!
16:07:13 <AylaStein> * facepalms
16:08:32 <NickRuffilo> Tzviya: "The roles in any of the ARIA document.  It's a list of terms with ARIA 1.1.  The DPUB we just point to ARIA for the items.  We reference navigation which points to the ARIA role...  What the API mappings do is say how the accessibility API mapping should utilize this.  It functions as the layer between the HTML/SVG/etc and the user.  So that's the broad overview of what happens here."
16:09:07 <tzviya> q?
16:09:11 <NickRuffilo> Joseph: "You said it's what interacts between HTML/SVG/user - it's there for the Assistive technologies.  It acts as an intermediary between the document and the assistive technology."
16:09:16 <tzviya> http://www.smashingmagazine.com/2015/03/web-accessibility-with-accessibility-api/
16:09:51 <NickRuffilo> Tzviya: "I have an article about how ARIA works.  The posted article explains that well.  It has the accessibility object model and where the markup language fits in, and where things that aren't ARIA fit in.  I recommend reading it."
16:10:24 <tzviya> q?
16:10:39 <NickRuffilo> ...: "Any accessibility API mappings, they are fairly complicated documents because there is not a specific API - Apple, Microsoft, Linux -- ok Edge, MSAA, and Internet Explorer..."
16:11:13 <lrosenth> but remember that these are platform centric - not generalized
16:11:28 <liam> present+ Liam
16:11:41 <dkaplan3> this is the best overview I've seen: https://www.marcozehe.de/2013/09/07/why-accessibility-apis-matter/
16:12:03 <dkaplan3> q+
16:12:08 <tzviya> ack dk
16:12:33 <jeff_xu> jeff_xu has joined #dpub
16:12:57 <NickRuffilo> Deborah: "I posted a URL with a really good roundup of the accessibility APIs - and explains what the browsers and APIs do."
16:13:18 <tzviya> http://www.w3.org/TR/2015/WD-dpub-aam-1.0-20151203/
16:13:43 <jeff_xu> present + jeff_xu
16:14:12 <NickRuffilo> Tzviya: "Here's the link to the AAM.  There's role-mapping at the bottom.  If you take a look at the roles, there is a section that explains in detail what the API is supposed to do with each one of these roles."
16:14:18 <clown> http://www.w3.org/TR/2015/WD-dpub-aam-1.0-20151203/#mapping_role_table
16:14:35 <tzviya> q?
16:14:47 <ivan> q+
16:14:51 <tzviya> ack liam
16:14:51 <Zakim> liam, you wanted to note it needs affordances
16:15:44 <tzviya> ack ivan
16:15:55 <NickRuffilo> Tzviya: "There has been quite a bit of work in the ARIA Github"
16:16:19 <NickRuffilo> Ivan: "When I look at the cells in the table, I'm not sure what it is they say.   Can you give a high-level overview of what's happening?"
16:17:18 <NickRuffilo> Joseph: "Using doc-abstract as an example.  If you're a browser running on windows, and you're using i-accessable2, you take the string .abstract and it'll be a role-system grouping in the accessibilty tree.  We will also store xml:.abstract.  It's a property of the accessible object."
16:17:48 <lrosenth> q+
16:18:15 <NickRuffilo> Joseph: "An accessible object is a tree-structure in the accessible API.  Similar to a DOM element, but not actually in the DOM.  So it extracts (subsets) the DOM and creates a new tree item.  From there you will have nodes in the new tree that has a role, a name, possibly a description, and a whole bunch of states and attributes."
16:18:20 <dkaplan3> here's a good link for the accessibility tree: https://www.paciellogroup.com/blog/2015/01/the-browser-accessibility-tree/
16:18:39 <NickRuffilo> Joseph: "So this note will have a grouping, xml:docabstract."
16:18:47 <NickRuffilo> Ivan: "So this isn't microsoft specific?"
16:19:28 <NickRuffilo> Joseph: "If you're using the MS-only apis then they are.  There is ATK/ASPI - that's for linux. The last is for Mac OS X.  "
16:19:46 <NickRuffilo> Ivan: "So they have a different API with different items?"
16:19:47 <tzviya> q?
16:20:18 <NickRuffilo> Joseph: "If you're running Safari on a mac, then safari creates it's own DOM.  It also creates it's own accessibility tree according to AXAPI.  It doesn't create the others."
16:20:23 <tzviya> axk lr
16:20:28 <tzviya> ack lr
16:20:34 <tzviya> s/axk/
16:21:24 <NickRuffilo> Leonard: "The thing you have to keep in mind about the APIs is that they aren't web-specific.  They are on the OS level so that everything on the screen is accessible.  The Accessibility DOM actually goes beyond the web itself.  Only at the end of the tree is the document that you're looking at."
16:22:12 <NickRuffilo> Joseph: "Adding to that - accessbility APIs were invented way before the web.  Browsers were initially just documents, and they fit in to the word-processors api."
16:22:25 <lrosenth> q+
16:22:33 <ivan> q+
16:22:43 <NickRuffilo> Joseph: "As web-development got more complex, there was a need to fit things correctly, which is where ARIA comes in."
16:22:44 <NickRuffilo> q+
16:22:54 <tzviya> ack lr
16:23:28 <NickRuffilo> Leonard: "Going back to the content - this looks good - but what strikes me as odd, is why - for 2 of the 4 - the value is doc- and in the others you remove the doc-?  Shouldn't it be consistent across APIs"
16:23:50 <shepazu> shepazu has joined #dpub
16:24:22 <NickRuffilo> Joseph: "In the two cases that have XML roles : that's a string.  The XMLroles: is not a namespace or a prefix, it's a name.  In this case it's a name value pair."
16:24:33 <NickRuffilo> Tzviya: "It's up to the API itself."
16:24:59 <NickRuffilo> Ivan: "Leonards question was not on the XML role it was the naming itself.  We use the original term doc-aspect, but we later drop doc-..."
16:25:10 <NickRuffilo> Joseph: "I'm not sure why they did it in the one API."
16:25:21 <NickRuffilo> Tzviya: "It's a question for the people at apple..."
16:25:40 <NickRuffilo> Joseph: "The description is a user-friendly string.  Would you say doc-abstract or abstract?"
16:26:20 <lrosenth> it would much better if we could have it consistent for all APIs
16:26:24 <tzviya> q?
16:26:32 <NickRuffilo> ...: "The UIA one is a piece of data, not really a string.  You could actually view it as...  So it's saying treat it like a control type abstract."
16:26:33 <tzviya> ack iv
16:26:55 <NickRuffilo> Ivan: "So, we have here, a view of various types of windows, linux, and OSX.  What about mobile?"
16:27:14 <NickRuffilo> Joseph: "XPI is whats being using on IOS."
16:27:17 <danielweck> doc-biblioref => Control type/role is 'bibliography references' in UIA, so this looks like a human-readable string (or maybe it's an editing error in this spec. document?)
16:27:20 <NickRuffilo> Ivan: "Android?"
16:27:28 <tzviya> q?
16:27:34 <NickRuffilo> Joseph: "I think it's using ATK... the linux one..."
16:27:35 <tzviya> ack ni
16:28:17 <Karen> Nick: If I understand it, ARIA creates tags and markup to make HTML doc happily inserted into whatever OS it needs
16:28:33 <Karen> …so I need to care about correct ARIA tags, roles,etc. so that whatever OS can do what it needs to do
16:28:37 <Karen> …is that correct?
16:28:50 <Karen> Joseph: First approximation, yes
16:28:55 <Karen> …authors should care about markup
16:29:11 <Karen> Nick: Is object model mainly for people creating accessibility applications
16:29:26 <Karen> …or is it expected that reading system creates its own accessibility
16:29:49 <Karen> Joseph: Core is to tell browsers…this is what you are supposed to do with the markup and how you are supposed to expose it within the accesibility API
16:29:57 <Karen> Ivan: And reading system in this respect is just a browser
16:30:09 <Karen> Joseph: can also be used by screen reader vendors to see what is coming out of the browker
16:30:13 <Karen> s/browser
16:30:20 <Karen> Nick: they are familiar that things are verklempt
16:30:24 <Karen> …ok, thanks
16:30:25 <clapierre1> q+
16:30:39 <Karen> Bill They are not using the original markup but how it has been interpreted into these API schemes
16:30:44 <Karen> Joseph: That is what they are supposed to be doing
16:30:56 <Karen> …some use the APIs but they also look at the DOM
16:30:59 <Karen> …very confusing
16:31:10 <Karen> Tzviya: Some of what it looks at is @
16:31:23 <Karen> Joseph: Is an HTML AAM; how to map
16:31:27 <Karen> …and one for SVG element
16:31:36 <tzviya> ack cl
16:31:40 <NickRuffilo> scribenick: nickruffilo
16:31:44 <Karen> …to extent that the mapping is complete and accurate the AT should not have to look at the DOM
16:32:26 <NickRuffilo> Charles: "Quick q: looking at doc-abstrct... we have role-system grouping, but there is none in the acknowledgements.  So there's nothing that maps this new role?  So now the AT has to look at the new role pair?"
16:32:48 <NickRuffilo> Joseph: "So the AT has to have a map to how to display something."
16:33:21 <tzviya> q?
16:33:21 <NickRuffilo> Tzviya: "There are no roles that do not have a super-class in ARIA 1.1 - a superclass means it's points to a parent.  it's better to look at the DPUB roles document."
16:33:47 <NickRuffilo> Ivan: "The table - shouldn't it include in the cell whatever the superclass maps to?"
16:34:00 <NickRuffilo> ...: "Any implementation needs to look at both documents at the same time?"
16:34:30 <NickRuffilo> Tzviya:" If you look at the ATK roles, they are just strings.  In acknowledgements for exmaple, it will say: 'expose role landmark'."
16:34:43 <NickRuffilo> Ivan: "I would expect something similar in the first line."
16:34:51 <NickRuffilo> Ivan.: " It feels incomplete."
16:35:18 <NickRuffilo> ...: "It's something we have to see with Rich - as he's the one who created these tables.  Lets make sure these questions flow back to him."
16:35:33 <NickRuffilo> Tzviya:" Great, and now we have a topic to discuss on the meeting on thursday."
16:36:07 <shepazu> present+ shepazu
16:36:19 <tzviya> if you have comments, plesae post to https://github.com/w3c/aria/issues with flag "dpub"
16:36:26 <NickRuffilo> Bill: "There are quite a few typos that should be addressed..."
16:36:43 <NickRuffilo> Tzviya: "Additional comments/questions/suggestions..."
16:36:57 <NickRuffilo> Doug: "I saw you were talking about SVG stuff.  Do you have any questions?"
16:37:12 <NickRuffilo> Tzviya:" We were talking about APIs in general - and just noted there is a mapping for SVG"
16:37:23 <NickRuffilo> Doug: "Ok, thanks..."
16:37:47 <rego> rego has joined #dpub
16:38:18 <NickRuffilo> Tzviya: "Tim followed up with me - which is wonderful.  Tim got together with people about archiving."
16:38:24 <ivan> Topic:archiving
16:39:20 <NickRuffilo> Tim: "This came up in the call 2 weeks ago.  we discussed next steps for PWP whitepaper.  The question of how to address archiving of these types of structures and what's already being done about archiving came up.  Breif discussion came up.  We discussed and here's a brief summary from where we are."
16:39:52 <tzviya> q?
16:40:57 <NickRuffilo> ...: "The whitepaper needs to be extended a bit in 3.7 which has placeholder text - possibly 5.2, where it mentions archiving.  We wanted to mention porticode and clocks.  It has lots of things that are being archived using those systems.  How do the things we wish to do with PWP impact on that."
16:41:01 <dkaplan3> s/clocks/CLOCKSS/
16:41:17 <tzviya> http://w3c.github.io/dpub-pwp/#package
16:41:19 <ivan> -> https://w3c.github.io/dpub-pwp/#libraries-and-archival-services current section in the PWP
16:41:20 <lrosenth> q+
16:41:50 <dkaplan3> http://www.portico.org/digital-preservation/join-portico/for-libraries
16:42:05 <dkaplan3> http://www.clockss.org/clockss/Home
16:42:07 <dauwhe> s/porticode/Portico/ ?
16:42:16 <ivan> q+
16:42:27 <Bill_Kasdorf> Yes
16:42:54 <NickRuffilo> ...: "There are efforts on premise in the library space.  There's an ISO standard on arcitle versioning.  We need to formulate the questions and get answers.  We also need to make sure the PWP document reflects though.  There are broader questions: should we strategically engage the parts of the library community that is dealing with archiving.  The special library association is dealing with
16:42:54 <NickRuffilo> this area - there are preservation coallitions.  Do we need to worry about archiving in our testing and demonstrations?  Bill/heather - do you have a little more deifintion on what you want to get done?"
16:43:10 <Bill_Kasdorf> q+
16:43:23 <tzviya> ack lr
16:43:23 <NickRuffilo> ...: "Do we need a taskforce?  if so, how do we get more volunteers.  And that's what we'd like a little more clarity on."
16:44:33 <NickRuffilo> Leonard: "I'm happy to participate in this group.  I'm the ISO project leader on PDF-A - the long-term standard for archiving PDF.  What I don't hear is what is meant by archiving?  Who's doing it?  Longitivity?  The things we talk about - and what archivist talk about - is that there are w whole lot of properties and concerns.  Can you talk more about the background/goals of archiving a PWP."
16:44:50 <NickRuffilo> Tzviya: "I think that's part of the taskforce is to figure out the goals themselves - the group needs to get going befroe we can answer that."
16:45:47 <NickRuffilo> Tim: "we don't want to re-invent what PDF-A has done.  For exmaple, there are CSS items that needs to be archived.  If there are thousands of documents that use the same versioned CSS archive - do you save that in all documents, or just some."
16:46:13 <NickRuffilo> Leonard: "You need to ask what the requirements are - not the implementation questions.  I think Tzviya is right, and take up these questions in a meeting."
16:46:15 <tzviya> ack iv
16:47:49 <lrosenth> ivan - depends entirely on what your requirements are, which is why I started there...
16:47:52 <NickRuffilo> Ivan: "It would be interesting to know...  You said libraries already archive large amounts of epubs.  It would be interesting to find out if they have run into technical issues - missing information - from doing so.  Even with epub 3.1 or PWP - what should be provided to making archiving easier.  It's the question I always repeat - what is missing - from a technical point of view - and what is
16:47:52 <NickRuffilo> necessary - for PWP to make the job of archivers easier.  If the answer is 'nothing really' then maybe we don't need to do more."
16:48:22 <NickRuffilo> Tim: "The point is, is to take advantage of what is already being done.  What are the implications of what we want to do.  And how do we adapt?"
16:48:25 <tzviya> q?
16:49:28 <NickRuffilo> Ivan: "It so happens that in about a month I will have a meeting with the head of the numerical department of bilbiotech national de france, that does archiving on a national level.  I will try to ask these questions.  Between now and then.  That's in January."
16:49:33 <AylaStein> q +
16:49:35 <tzviya> ack bill
16:50:00 <ivan> s/bibliotech national/bibliothèque nationale/
16:51:06 <NickRuffilo> Bill: "What I want from this group is a clear definition of scope.  On the one hand there are archiving services - that are sector specific - and have entirely opposite approaches.  Then you have national libraries - that also have very active and very different archiving things.  On the opposite side of the scale, you have an archive that a publisher would want to create to have a canonical item
16:51:06 <NickRuffilo> that they would want to use for the publication.  Is our scope all of that, some of that.  Are we supposed to point this out?"
16:51:15 <lrosenth> +1 to Bill_Kasdorf
16:51:29 <NickRuffilo> ...: "PDF-A is mainly for publishers to have a canonical items?"
16:51:39 <NickRuffilo> Tzviya: "We're slowly defining exactly what it is..."
16:51:42 <NickRuffilo> q+
16:51:54 <AylaStein> oops
16:52:12 <NickRuffilo> Ayla: "I wanted to push back on the 'we can get this done in a week'"
16:52:25 <NickRuffilo> Ivan: "That was a joke :) "
16:52:39 <NickRuffilo> ...: "Whatever finidng you have between now and january - if you send it to me, that would be helpful"
16:52:44 <tzviya> ack nick
16:53:10 <lrosenth> q+
16:53:55 <NickRuffilo> Leonard: "Depends on who you're sending the content to and their purposes.  Everybody has different requirements.  There are commonalities - but who are we trying to address and why?"
16:53:59 <tzviya> q?
16:54:22 <NickRuffilo> Tim: "Archives have different levels of re-use (what they saw VS simply saving bit/bytes)"
16:54:37 <tzviya> ack lr
16:54:38 <NickRuffilo> Leonard: "Thats part of the question - long term vs short-term"
16:54:43 <tzviya> ack li
16:54:43 <Zakim> liam, you wanted to say no, versioning is a separate issue
16:55:11 <NickRuffilo> Liam: "We've had a symposium on long-term archiving of documents in the XML world - and we should connect into some of that."
16:55:58 <Bill_Kasdorf> q+
16:56:50 <tzviya> ack bill
16:56:58 <NickRuffilo> Liam: "Another way to look at versioning - is that if you have two different versions, then you have two documents, which would mean you have two different formats...  To document the exact version of every spec, it's an enormous task.  If you come back in 50 years and you need to get something that uses javascript working.  To see how large it is, you should see what the LOC has had trying to
16:56:58 <NickRuffilo> get versions of hypercard working that require very specific versions of items working.  "
16:57:02 <Bill_Kasdorf> Please sign up for Locators TF: https://www.w3.org/dpub/IG/wiki/Task_Forces/locators
16:57:31 <lrosenth> From the Library of Congress - http://www.digitalpreservation.gov/formats/intro/intro.shtml
16:57:32 <tzviya> http://www.w3.org/2015/12/01-tag-nominations
16:57:32 <NickRuffilo> Bill: "We are bringing up a locators task force - those interested in working on the locators - please add your name to that roster as the starting point."
16:57:51 <lrosenth> EPUB - http://www.digitalpreservation.gov/formats/fdd/fdd000308.shtml
16:58:02 <NickRuffilo> Tzviya: "Please VOTE in the TAG elections.  These are the people who make the high-level architecture decisions.  Look at the link I just sent."
16:58:10 <tzviya> q?
16:58:20 <HeatherF> q+
16:58:28 <tzviya> ack he
16:58:37 <NickRuffilo> Heather: "Did we come to resolution - do we need a taskforce?"
16:58:37 <AylaStein> gotta go to another meeting, thanks!
16:58:58 <NickRuffilo> Tzviya: "Yes, it seems we need a task-force for archiving."
16:59:20 <NickRuffilo> Tzviya: "We're meeting for the next two weeks, then take a week off."
16:59:22 <pkra> thx
16:59:25 <NickRuffilo> Thank you everyone!
16:59:25 <HeatherF> thanks all!
16:59:36 <jeff_xu> jeff_xu has left #dpub
17:00:44 <ivan> rrsagent, draft minutes
17:00:44 <RRSAgent> I have made the request to generate http://www.w3.org/2015/12/07-dpub-minutes.html ivan
17:01:23 <ivan> trackbot, end telcon
17:01:23 <trackbot> Zakim, list attendees
17:01:23 <Zakim> As of this point the attendees have been Tzviya, Charles_LaPierre, Joseph_Scheuhammer, Deborah_Kaplan, Ivan, Tim_Cole, nick_barreto, duga, Karen, Bill_Kasdorf, dauwhe,
17:01:27 <Zakim> ... Heather_Flanagan, Leonard_Rosenthol, Bert, Liam, shepazu
17:01:31 <trackbot> RRSAgent, please draft minutes
17:01:31 <RRSAgent> I have made the request to generate http://www.w3.org/2015/12/07-dpub-minutes.html trackbot
17:01:32 <trackbot> RRSAgent, bye
17:01:32 <RRSAgent> I see no action items