Changes to Principles from August 16 call

[GeorgeKerscher]

This improves the language in navigation supported by the page list. Also softened language around conformance to an unknown specification. I did not mention an optimized specification because I did not think most people would know what that means. Added the note before the examples in additional information that there many features and we should some. Complete list in techniques. I removed sign language which were associated with closed captions. Close captions will be common and sing language videos will be rare.

[GeorgeKerscher]

We know that ONIX does not have a code for an unknown specification and it was considered and they decided not to have a code at this time.

Removing this and the example would resolve the issue for ONIX.

We have PDF/UA in ONIX code 05. I don't know that we have similar metadata in EPUB accessibility I think we thought our guidelines would apply to PDF as well.

If we have a value in schema.org for PDF/UA or can create one in our vocabulary, should we put this into the examples of conformance?

It is probably not the right time to add more specifications, but if libraries serving people with disabilities will use this, we should add DAISY 2.202 and 3 to the list of known specifications.

[mattgarrish]

If we have a value in schema.org for PDF/UA or can create one in our vocabulary

No, conformance claims aren't part of the schema.org metadata. I think it's outside the scope of our work here, too, as it would necessitate a PDF techniques document, as there'd have to be a way to read the conformance from the PDF file.

[avneeshsingh]

we can remove example of conformance to unknown standard. We can revisit it when we have something concrete in ONIX.