scribe+
<wendyreid> https://www.w3.org/publishing/groups/publ-wg/Meetings/Minutes/2019/2019-09-09-pwg
Wendy: Minutes from 3 weeks
ago
... minutes approved.
RESOLUTION: minutes of 3 weeks ago approved
<wendyreid> https://www.w3.org/publishing/groups/publ-wg/Meetings/Minutes/2019/2019-09-16-pwg
<wendyreid> https://www.w3.org/publishing/groups/publ-wg/Meetings/Minutes/2019/2019-09-17-pwg
TPAC minutes (2 days)
RESOLUTION: TPAC meeting minutes approved
scribe: Benjamin created
them
... approved
Wendy: 2 days of meeting, goal to get a plan for testing / implmentation
talked about Da-Future!
talked about DPUB-ARIA
scribe: talked to the MathML
folks about native mathML in chrome
... talked to the PING folks on Privacy/Security all in the
minutes
... publication manifest 2 prong approach web platform tests to
test all the must/should in audio books and publication
manifest based on schema 1 part, and will get updates in a
min.
... not in audio book spec yet but we will need to write some
manual tests for user agent implementations
... like what happens when non-audio appears in the reading
order.
... if you are interested in writing tests or to implement the
manifest formats on production side please let us know.
... Benjamin can you give an update?
... Two major things coming out of TPAC, Web Annotations looked
at all must/should created schema tests which we could do as
well, but maybe we could just do 1 large test instead of a lot
of small tests. There were some issues before on implementing
this but maybe that has been resolved. waiting for an
update.
... looking for some tool to to pull out must/shoulds that
RESPEC might be able to do.
Ivan: I am not sure there is a
Pull request that is outstanding that may need to be
reviewed.
... we don't want to wait on each other.
Wendy: adding to the agenda, we
want to look at the issues to see what we can close. Checklist
for CR need to have # of issues closed.
... Ivan, do you want to look at checklist?
... cr what we need to do to get to CR.
Ivan: interesting thing at TPAC Thur/Fri and some breakout groups. old issue on base direction, now JSONLD new spec will include features that were missing so far.
<ivan> https://github.com/w3c/pub-manifest/issues/75
Ivan: language similar level
JSONLD base direction we can modify our pub manifest, changes
that are necessary
... I will prepare a pull request with detailed changes and
then we can discuss it later. look at the issue I put in
IRC
... questions?
Wendy: this could solve most of the I18N folks were asking for.
Ivan: created a wiki page
Ivan: pattern used to submit a CR
req. shows what we need to complete.
... some admin stuff but we need to look at charter req. we
need to answer.
... we will need to come up with a response to that. wide
review to HR which we will need to add for APA & PING
review and we are done and we are fine, and Brady did PING but
we will need to have all pointers to the wiki page.
Avneesh: We had a discussion with APA meeting and they will do a voting on the mailing list, and Janina said they will do this by the end of September and I sent a reminder today.
Wendy: for PING we didn't get formal approval but this was more about an initial discussion
Ivan: but answers/references need
to go to the wiki
... wiki page added URLs which are searches into the open
issues, / postponed and list for all the closed issues.
... beyond audio profile and pub manifest I added the web
publication issues as well.
... we will have to close all the issues, so far no formal
objectives and implementation part which we will talk about and
document what we intend to do and how we will report and what
implementations we plan to have.
... we dont' have to have the full test suite before we ask for
transition but more we have the better.
... look at wiki for things to add to it. Careful about: once
CR has been published the document itself can not change in
terms of technical content, editorial changes are fine.
... if we do a technical change in CR then we will have to go
through the same process described here again.
... if you have a technical issue that you want solved in CR
then speak up now or so hold your peace!
Wendy: Called for Closing at TPAC
unless someone has an objection.
... most of the remaining issues seem to be editorial
<wendyreid> CharlesL: Just a question for the testing and writing tests for MUSTs and SHOULDs, in the past I know that Tzviya would go with the other chairs and draw up a spreadsheet of who would do what
<ivan> scribe+ wendyreid
scribe+
Wendy: I have my own spreadsheet who is responsible for what but that is a good idea.
<Avneesh> Issue #13, I suggsted some improvements but it looks that I do not have rights to reopen it.
<Avneesh> https://github.com/w3c/audiobooks/issues/13
Ivan: Vocabularies in the past
was to prove that terms in the vocabulary are useful either
used or publishers may plan to use it for audio books or
others. Is this the kind of test for the dpub manifest, some of
them may be used in the audio manifest.
... feedback from publisher that they would need this term for
their publications. Many of the terms are coming from
schema.org so those I am not sure they are normative in our
case.
... with manifest is processing into an internal data
structure, but maybe we want test to the implementations.
Matt: normative/non normative values EPUB- Manifest mapping would be useful?
Ivan: that would be useful. indirectly that terms the community uses.
Matt: that isn't hard to do, but just needs to be done.
Ivan: good idea!
Wendy: interesting Test how well
we conform to EPUB.
... any other questions about CR or the tests?
<silence>
Wendy: Ok, I will create a spreadsheet with general roles of people, I will create once I get an idea from Benjamin / Laurent how to structure the tests single vs. multiple.
Gregoria: I can help Matt with the EPUB
Ivan: should have formal
procedures tests accepted by everyone, reviewed by the
WG.
... light weight procedure submit PR so interested folks can
review before merge.
Wendy: that works for me.
... test folders in each of the pub manifest / audio manifest
directories. everyone can submit PRs or comment on them.
... I will work on this this week, and will get in touch with
folks on their various jobs.
... any other business questions? TPAC?
Avneesh: regarding I don't think
any comment was #30 closed issue I don't have the rights.
... alternate HTML .. sync media
Ivan: when I read the minutes
demos from Marissa which is great, has their been discussions
refer to /combined with audio book spec or the other spec.
wouldn't be normative but we should refer to it, it wasn't
clear from the minutes.
... published as a separate note, keep it related to audio
books but could be applied to anything pub manifest text/audio
linked via json
Marissa: standalone note to any HTML document, let me know what works for you to refer to it.
Ivan: a WG Note? or a report of
the Task Force.
... if its a stand alone doc. then CG Note.
... You are a CG right?
Marisa: Yes CG.
Ivan: so a CG can create a CG Report and is what should it be.
Avneesh: Yes we discussed this a year ago and decided this would be a CG Report.
Wendy: yes this will be a
Non-Normative reference to that
... we are covered and all is good.
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/to/about/ Succeeded: s/talked/… talked/ Succeeded: s/Wendy:/…/ Succeeded: s/../…/ Succeeded: s/Marissa/Marisa/ Default Present: franco, ivan, wendyreid, gpellegrino, Nellie, CharlesL, \, BenSchroeter, marisa, romain, Avneesh, Bill_Kasdorf, Garth, duga Present: franco ivan wendyreid gpellegrino Nellie CharlesL \ BenSchroeter marisa romain Avneesh Bill_Kasdorf Garth duga mgarrish Regrets: Luc Rachel dauwhe george teenya geoff laurent No ScribeNick specified. Guessing ScribeNick: CharlesL Inferring Scribes: CharlesL Agenda: https://lists.w3.org/Archives/Public/public-publ-wg/2019Sep/0021.html WARNING: Could not parse date. Unknown month name "09": 2019-09-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: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. 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.)[End of scribe.perl diagnostic output]