Matt Garrish

> I've taken this language [from HTML](https://html.spec.whatwg.org/multipage/urls-and-fetching.html#content-type-sniffing). Which says you must "obtain and interpret". That's the precision lacking here. "Determine" speaks to process, not outcome.

The problem is getting an erratum for 1.0. We have a page for it at https://idpf.org/epub/a11y/errata/, but it'll take getting the old IDPF site updated, or getting a redirect on...

The web schemas wiki needs updating. Notice it doesn't list the "none" value. We agreed to add it while developing the accessibility specification to avoid having to list three instances...

If this wants to be a discussion about changing the schema.org property, it should be transferred to the vocab group. Like @clapierre, I'm not a big fan of changing names...

As conceived: > * Should it highlight the important information which is provided in the machine readable accessibility metadata? Yes. > * Should it provide the information which is not...

> On one hand I hate duplication I think this is key. The summary shouldn't be a simple rote restating of all the other properties. You shouldn't be listing every...

I expect the best we could do here is recommend key information that should be in the report, sort of like what WCAG has for making claims: https://www.w3.org/TR/WCAG21/#conformance-claims Given that...

> [Authorized Translations](http://www.w3.org/2005/02/TranslationPolicy) follow a formal review process and are endorsed by W3C. This is a community group. All it can produce are community group reports which have no standing...

> and I believe it is perfectly fine to do so with a translation. Right, I guess it depends on whether the whole documents are being translated or only the...

> However, we would also like to define a control process for figuring out who can publish a localization in the repository. Well, that's where maintaining translations becomes a headache....