<Avneesh> chair: Avneesh
+present
<tzviya> Chair: Avneesh
<Julian_Calderazi> +present
scribe+
<Avneesh> https://w3c.github.io/publ-a11y/UX-Guide-Metadata/principles/
<Avneesh> https://w3c.github.io/publ-a11y/UX-Guide-Metadata/principles/
Avneesh: How's the document looking?
Laudrain: please add me to the reviewers
Avneesh: Yes
<Avneesh> https://w3c.github.io/publ-a11y/UX-Guide-Metadata/techniques/
Avneesh: Techniques document
<Avneesh> https://github.com/w3c/publ-a11y/issues/8
Laudrain: it isn't all schema techniques
Madeleine: Schema and more? Schema plus? It is useful to reference Schema.org for name recognition
Avneesh: Embedded metadatat techniques? but it is good to have schema.org in the name
Bill: Techniques for displaying Schema.org and other standard accessibility metadata
Avneesh: too broad?
... expect to keep separate docs for internal and external
metadata
Charles: Internal with a11y, schema, and epub metadata
Tzviya: not internal vs external.
hope to have wider usage
... Prefer to have fewer documents, although I understand why
we have schema techniques separate
Tviya: master document that links all of them
Avneesh: linking is good
... schema.org is not complete and so we need dc:conformsTo and
epub terms
<CharlesL> https://w3c.github.io/publ-a11y/UX-Guide-Metadata/techniques/
CharlesL: this link is the overarching techniques doc that links the others
Madeleine: be sure we promote the central techniques doc that links to all of them
Avneesh: useful to have editor for each kind of metadata have their own doc to edit
Madeleine: and easier for implementors to read their own examples without others mixed in
Mattg: if it is about package documents metadata, why not say that?
Madeleine: who is the audience and what will they find most recognizable or persuasive?
Tzviya: the ones added to schema are to enable the use of schema.org, so we could call it that
George: marketing and
communications around this area need intro document to explain
the principles.
... link to other techniques is good, but one thing to bookmark
for finding again
Bill_Kasdorf: encourage publishers to put it right on their web site
Laudrain: Retailer needs to read ONIX doc. If getting EPUB, needs to understand to look in the package document
<laudrain> https://www.epagine.fr/list-53692/livres-numeriques-accessibles/
Laudrain: French retailer epagine
is linking to accessible books. Using ONIX feed.
... will ask contact there to look at these documents and ask
if it is clear. Should also localize to French, Italian,
etc.
<tzviya> +1 to mattg
<CharlesL> +1 as well
Mattg: Techniques for display of schema.org metadata, not techniques FOR schema.org metadata
laudrain: MARC will be transfered from national library, outside the book
<CharlesL> or External: ONIX, External: MARC etc.
George: Name consistently.
Madeleine: Techniques for the display of schema.org and (others) accessibility metadata
Techniques for the display of ONIX accessibility metadata
etc.
<Avneesh> https://github.com/w3c/publ-a11y/issues/6
Avneesh: finish naming decision on issue tracker
<mattg> https://www.w3.org/publishing/epub3/
Charles: that isn't a w3c standard page
Tzviya: agreed that we need to follow w3c style.
Mattg: can use a simpler style link this one for epub3
<CharlesL> agree with Matt
<Avneesh> https://github.com/w3c/publ-a11y/issues/4
Avneesh: yes, let's use that style that Matt suggested
<Avneesh> Accessibility Conformance: EPUB Accessibility (WCAG AA)
<CharlesL> +1
<laudrain> +1
Madeleine: that is the specific
term for epub acc
... section 2.4 of the techniques doc is called "EPUB Acc
Conformance" which shouldn't be the section title
Tzviya: People mostly have heard of WCAG and that's what they know best
Laudrin: publishers in epub production don't know wcag, but people building web sites know wcag better than epub
Tzviya: general publishing staff know wcag or 508 but not epub standard
<CharlesL> So instead of:
<CharlesL> 2.4.1.2 UI
<CharlesL> EPUB Accessibility Conformance: http://www.idpf.org/epub/a11y/accessibility-20170105.html#wcag-aa
<CharlesL> we should have just:
<CharlesL> Accessibility Conformance: http://www.idpf.org/epub/a11y/accessibility-20170105.html#wcag-aa
<MURATA> +present
Avneesh: if wcag conforming: accessibility conformance: wcag aa
if epub conforming, dont' put wcag, just put epub
Naomi: could it have two lines showing conformance to wcag and epub separately
<Avneesh> ackgeorge
George: wcag is a high level
publication. it is abstract and applies to any kind of page or
doc
... but i've never seen a pdf that claimed wcag conformance
Madeleine: are we discussing the section title for 2.4, or the contents of conformsTo statements, or the user-friendly UI for a given conformsTo statement?
Avneesh: how to make the UI less
confusing for the statement.
... change heading for 2.4 to Accessibility conformance, have
discussion about UI on issues tracker
... MARC coordination
... This will be a slow process.
... Marco from Finnish library will be liaison and will join
future calls. After 24 March, another person will be
appointed
Madeleine: who created the crosswalk?
<MURATA> Ando-san?
Avneesh: Japanese member.
... project plan is being prepared, and then a new liaison will
be appointed
Laudrain: There are several MARC
standards. There is UniMARC and MARC21 but I hope they will
converge
... I am not in touch with IFLA people but would be happy to
be
George: How big is that working group?
Avneesh: 5 or 6, but clearer after March meeting
George: Lots of interest in Canada. Could they get involved?
Avneesh: I will follow up
... Google metadata followup
George: CharlesL and Gregorio and I met with Google staff. Kiran Kahja, couple others
CharlesL: they think this has
value but they don't want to misrepresent what a reading system
can do
... if some of the acc features aren't available on this
reading system they would need to edit the presentation of
metadata
George: inside play book environment, they want to expose acc metadata, but also in general search
Laudrain: play books receives
metadata from publishers in ONIX. uses for prices and titles
and so on
... keen to store acc metadata from onix, hope to use it so
when users search for a book and get a knowledge card
... knowledge card has a module that links to where you can buy
the book
... they could have a checkbox in the module to find the book
where acc metadata is displayed, for example
... but if it is on those websites selling the book it is
probably in schema.org!
<Bill_Kasdorf> It's the Crossref Books Advisory Group
Madeleine: you can use acc
metadata to describe the features of the reading system so that
you can automatically know how to filter metadata
... Is it OK if Bill K and I present these docs as work in
progress to the Crossref books advisory group?
Avneesh: yes, but emphasize work
in progress
... next meeting March 6?
... doodle poll to see if this works for everyone. CSUN, london
book fair, ebook craft, etc.
<CharlesL> thanks
March is busy
Bye!
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/Laudrin/laudrain/ Present: Avneesh Julian_Calderazi tzviya Naomi laudrain alexgrover George Bill_Kasdorf No ScribeNick specified. Guessing ScribeNick: Madeleine Inferring Scribes: Madeleine WARNING: No "Topic:" lines found. WARNING: Could not parse date. Unknown month name "02": 2020-02-14 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: 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.)[End of scribe.perl diagnostic output]