<Avneesh> https://github.com/w3c/publ-a11y/issues/9

<scribe> scribe: George

<scribe> scribe: George

<Avneesh> https://github.com/w3c/publ-a11y/issues/9

MR: going through 9

We could be more specific about which issues we are talking about, or we could leave it vague.

Avneesh: Broad statements are fine.

MR: Proposes that the language changes, "Inside the EPUB package."
... I proposed a shorter pargraph about the mappint.

<Bill_Kasdorf> +1 to Madeleine's update

MR: read through the paragraph recommendation.

<gpellegrino> +1

Avneesh: no objections, approved.

<Avneesh> https://github.com/w3c/publ-a11y/issues/4

GP: I will make the changes and close the issue.

Avneesh: issue 4

<Avneesh> Accessibility conformance: EPUB Accessibility, WCAG A

<gpellegrino> +1 to Luc

Luc: I like the two values, because it is more precise.

<Bill_Kasdorf> +1

Avneesh: No objections, approved.

<Avneesh> https://github.com/w3c/publ-a11y/issues/11

GP: I will comment the issue with our thoughts. Then modify the document and close the issue.

Issue 11

<Avneesh> https://github.com/w3c/publ-a11y/issues/10

<Bill_Kasdorf> I'd like the calendar invite too. I didn't get one this time either.

<Avneesh> https://github.com/w3c/publ-a11y/issues/8

Issue 8:

AS: Discussion?

GP: At first it was in one document. We then thought it should be split, because we could add other medadata standards.

We also split it into principles and techniques. This way we would be able to update them independently.

AS: Decision maintain a tecniques document for each metadata standard.

BK: Most people only pay atention to the one they care about and so those won't go obsolete when a different one changes.

AS: About the name, it currently says Schema.org, but it is a combination of EPUB and Schema.

GP: What about EPUB package metadata.

AS: Last time most people objected to using metadata in the package.

<wendyreid> scribe+

<wendyreid> George: I think the only objection was using the EPUB metadata to infer information about the accessibility

<wendyreid> ... this was in the transformability conversation

<wendyreid> ... most of the time people are going to grab the accessibility metadata we specify

<wendyreid> ... not grabbing the reflow statement from the EPUB, if we had to replicate that, it would be better than looking at other metadata

<wendyreid> ... I thought the objection was about using the word "package"

Scribe+

<gpellegrino> +1!

MR: What about EPUB Accessibility metadata?

<Bill_Kasdorf> +1

<wendyreid> +1

<laudrain> +1

AS: Let's put this in in the issue tracker.

<scribe> ACTION: item to Avneesh to add this to the issue tracker.

AS: Next call we will figure out after we have the discussion on the issue tracker.

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/fague/vague/
Succeeded: s/card about/care about and so those won't go obsolete when a different one changes/
Present: Avneesh laudrain AlexGrover George gpellegrino wendyreid Naomi Bill_Kasdorf Madeleine_
Found Scribe: George
Inferring ScribeNick: George
Found Scribe: George
Inferring ScribeNick: George

WARNING: No "Topic:" lines found.


WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


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: item

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


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.)