13:03:05 <RRSAgent> RRSAgent has joined #dpub-aria
13:03:05 <RRSAgent> logging to http://www.w3.org/2015/06/25-dpub-aria-irc
13:03:17 <MichaelC> rrsagent, make log world
13:04:42 <tzviya> put out CfCs, positive responses so far
13:05:01 <tzviya> michael will work on status section
13:05:26 <tzviya> mc: status section will mention that this is published by PF with advice from DPUB
13:05:40 <tzviya> ...is an ARIA extension, perhaps point to wiki
13:05:50 <tzviya> ...seeking feedback
13:06:01 <tzviya> ...may ask specific questions
13:06:12 <tzviya> ...such as hyphenspace issue
13:06:23 <tzviya> ...may need feedback from DPUB
13:06:33 <tzviya> s/DPUB/DPUB ARIA TF
13:06:56 <tzviya> mc: need to review abstract especially
13:07:27 <tzviya> current draft: https://rawgit.com/w3c/aria/af35e78947e1ef43229fed197ce01cdc79fdbc3b/aria/dpub.html
13:07:44 <tzviya> mc: still need to update with agreed on definition of ARIA extension
13:08:07 <tzviya> JS: we never formalized definition of extension, and maybe we should
13:08:53 <tzviya> JS: this is the time to get specific questions from DPUB side into the status section
13:09:28 <tzviya> IH: the model for future of extensions of the model and its extensions is the main issue
13:10:13 <tzviya> JS: perhaps we need to state outright that this list is susceptible to further extension
13:10:37 <tzviya> MC: at some point, it might be useful to mention how we expect this list to evolve
13:11:02 <tzviya> IH: this is only FPWD, so we can clarify later
13:11:13 <tzviya> present+ Tzviya_Siegman
13:11:28 <tzviya> present+ markus_gyllinh
13:11:44 <tzviya> present+ Matt_Garrish
13:12:15 <tzviya> IH: We don't need to spell this out now, but it will be important to clarify extension mechanism at some point for groups like IDPF
13:12:29 <tzviya> ...perhaps put an empty "TBD" section in the document?
13:12:54 <tzviya> MC: it is acceptable in FPWD to have TBD or one sentence hook in FPWD
13:13:08 <tzviya> IH: will you try to add that?
13:14:23 <tzviya> ...It is expected that the publishing community will add terms in the future. It is not clear what the mechanism for adding them at this point
13:14:40 <tzviya> JS: I hesitate to add this because it might slow us down
13:15:02 <tzviya> ...if you won't forget about it, then I don't think we should put it in
13:15:19 <tzviya> IH: we won't forget about it
13:16:12 <tzviya> MC: it's awkward that ARIA group is de facto maintainer of these roles. With prefix, this is a little more lax
13:17:00 <tzviya> MC: let's wait until next draft to add this in
13:17:50 <tzviya> ...I'll create a new draft for TR but I won't merge to master yet
13:17:59 <tzviya> ...I've been targeting July 14
13:18:50 <tzviya> discussion of timelines
13:19:51 <tzviya> mc: I will try to get this to Judy this week
13:20:13 <tzviya> ...I need the list of questions from this group to lead with
13:20:27 <tzviya> IH: THE question is Can we live with the hyphen?
13:21:22 <tzviya> mc: is this a full list of terms?
13:22:43 <tzviya> TS: no, these represent basic content structure. We haven't approached concepts like assessments and education terms. Those will be added as a later module or additions to this module
13:24:36 <tzviya> TS: we will likely get a request to show more robust examples, but we can add that later
13:25:08 <tzviya> JS: to set expectations - we need to respond to all comments formally
13:25:38 <tzviya> ... we need to either agree, disagree
13:26:03 <tzviya> mc: comments go to the #PF mailing list
13:26:31 <tzviya> IH: I have bad experience with mixing comments from different sources
13:26:53 <tzviya> ...can we request one, ideally GitHub issues list?
13:27:29 <tzviya> MC: i think we need to offer a mailing list, but we can say that we prefer the GH tracker
13:28:08 <tzviya> JS: GH will be canonical, and someone will be responsible for transferring email issues to GH
13:28:25 <tzviya> IH: we should create a DPUB label in GH
13:30:44 <tzviya> MC: it may fall to me to copy comments to GH
13:30:52 <tzviya> IH: I can help
13:31:58 <tzviya> MC: We can also set up comments just for DPUB
13:32:36 <tzviya> JF: how long do we leave this open for comment?
13:32:48 <tzviya> IH: it's open for comment until it becomes TR
13:32:55 <tzviya> JF/JS
13:33:01 <tzviya> s/JF/JS
13:34:16 <tzviya> MC: I always put in a date so that we can put out new versions
13:35:18 <tzviya> IH: We run it until we are done with comments, then we run a new draft, then do last call
13:35:45 <tzviya> ...timing can vary. It should take about 6 months
13:36:05 <tzviya> ...We can say work is done and look for implementations
13:36:16 <MichaelC> -> https://lists.w3.org/Archives/Public/public-dpub-aria-comments/ DPub ARIA Comments List
13:37:13 <tzviya> TS: it sounds like we don't need a date except to set expectations for ourselves
13:37:46 <tzviya> MC: PF usually sets dates
13:40:06 <tzviya> IH: set a date after summer, 1 Sep
13:40:42 <tzviya> JS: put it to friday of that week
13:41:05 <tzviya> ...which is 11 Sep
13:42:24 <tzviya> mc: I have what I need for transition request
13:43:20 <tzviya> JS and TS will send CfC responses to Michael on Monday morning
13:43:34 <tzviya> next steps?
13:44:21 <tzviya> no meeting next week
13:44:55 <tzviya> 9 July begin dealing with issues on FPWD or begin discussions on mapping
13:45:27 <tzviya> mc: adding 1.0 to doc titlte
13:46:43 <tzviya> RRSAgent, make minutes
13:46:43 <RRSAgent> I have made the request to generate http://www.w3.org/2015/06/25-dpub-aria-minutes.html tzviya
13:48:51 <MichaelC> chair: Tzviya
13:48:54 <MichaelC> present+ Michael
13:49:03 <MichaelC> meeting: DPub ARIA TF
13:49:14 <MichaelC> present+ Ivan, Janina
13:49:23 <MichaelC> scribeOptions: -final
13:49:27 <MichaelC> rrsagent, make minutes
13:49:27 <RRSAgent> I have made the request to generate http://www.w3.org/2015/06/25-dpub-aria-minutes.html MichaelC
15:08:02 <Zakim> Zakim has left #dpub-aria