Re: Proof of use of EPUB and Accessibility specification properties

Hi Matt,

On behalf of Pearson, I have updated these tables as requested and created
a Pull Request for both.

I note that while you did not ask, for what it is worth we are also
routinely using the following optional Dublin Core terms as well:

   - dc:creator
   - dc:date
   - dc:type
   - dc:description
   - dc:format
   - dc:publisher
   - dc:rights
   - dc:source
   - dcterms:modified
   - dcterms:dateCopyrighted


JF

On Tue, Jun 21, 2022 at 8:46 AM Matt Garrish <matt.garrish@gmail.com> wrote:

> Hi folks,
>
>
>
> As you may or may not be aware, part of moving the EPUB 3.3 and
> Accessibility 1.1 specifications to recommendation requires showing that
> publishers are using the various package document metadata properties
> defined in those specifications.
>
>
>
> To that end, we’re asking for publishers to formally acknowledge the
> properties they use in our candidate recommendation exit reports. The
> properties do not have to be included in all your publications; the
> requirement is only that you actively use them in your workflows.
>
>
>
> For those who are comfortable using GitHub and markdown, the EPUB 3.3
> specification report is at [1] and the Accessibility 1.1 specification
> report is at [2]. Please feel free to create a new pull request that adds
> your organization’s name to the lists for each property you use. For those
> who have access rights, you can also edit the files directly from the
> GitHub interface (click the pencil icon at the top right of the markdown
> text).
>
>
>
> If you’re not comfortable with GitHub, I’m attaching a text file with the
> values from those pages, as well as pasting the values below my signature
> in case anyone has the attachment blocked. You can return the list of
> properties you use to me and/or Ivan to add to the report pages (you don’t
> need to reply to the group email lists). Feel free to reply however best
> suits you – send the list back in a response body or as an attachment,
> delete the values you don’t use or check off the ones you do, etc. Whatever
> makes this as painless for you as possible!
>
>
>
> Please feel free to forward this request to anyone else who might be
> interested; it’s not only for W3C members.
>
>
>
> [1]
> https://github.com/w3c/epub-specs/blob/main/epub33/reports/epub-properties-use.md
>
> [2]
> https://github.com/w3c/epub-specs/blob/main/epub33/reports/a11y-properties-use.md
>
>
>
> Many thanks in advance for your help!
>
>
>
> Matt
>
>
>
>
> ----------------------------------------------------------------------------------------
>
>
>
> Meta Properties Vocabulary
>
> Manifest properties are expressed in the meta element's property attribute.
>
>
>
> alternate-script
>
> authority
>
> belongs-to-collection
>
> collection-type
>
> display-seq
>
> file-as
>
> group-position
>
> identifier-type
>
> role
>
> source-of
>
> term
>
> title-type
>
>
>
>
>
>
> ----------------------------------------------------------------------------------------
>
>
>
> Link Vocabulary
>
>
>
>
> ----------------------------------------------------------------------------------------
>
>
>
> Link Relationships
>
> Link relationships are expressed in the link element's rel attribute.
>
>
>
> acquire
>
> alternate
>
> record
>
> voicing
>
>
>
>
> ----------------------------------------------------------------------------------------
>
>
>
> Link Properties
>
> Link properties are expressed in the link element's properties attribute.
>
>
>
> onix
>
> xmp
>
>
>
>
> ----------------------------------------------------------------------------------------
>
>
>
>
>
> Package Rendering Vocabulary
>
>
>
>
> ----------------------------------------------------------------------------------------
>
>
>
> General Properties
>
> General package rendering properties are expressed both globally in the
> meta element's property attribute and as overrides in the itemref element's
> properties attribute.
>
>
>
> rendition:flow
>
> rendition:align-x-center
>
>
>
>
> ----------------------------------------------------------------------------------------
>
>
>
> Fixed-Layout Properties
>
> Fixed-layout properties are expressed both globally in the meta element's
> property attribute and as overrides in the itemref element's properties
> attribute.
>
>
>
> rendition:layout
>
> rendition:layout-pre-paginated
>
> rendition:layout-reflowable
>
> rendition:orientation
>
> rendition:orientation-auto
>
> rendition:orientation-landscape
>
> rendition:orientation-portrait
>
> rendition:spread
>
> rendition:spread-auto
>
> rendition:spread-both
>
> rendition:spread-landscape
>
> rendition:spread-none
>
> rendition:page-spread-center
>
> rendition:page-spread-left
>
> rendition:page-spread-right
>
>
>
>
> ----------------------------------------------------------------------------------------
>
>
>
> Manifest Properties Vocabulary
>
> Manifest properties are expressed in the item element's properties
> attribute.
>
>
>
> cover-image
>
> mathml
>
> nav
>
> remote-resources
>
> scripted
>
> svg
>
> switch
>
>
>
>
> ----------------------------------------------------------------------------------------
>
>
>
> Spine properties vocabulary
>
> Spine properties are expressed in the itemref element's properties
> attribute.
>
>
>
> page-spread-left
>
> page-spread-right
>
>
>
>
> ----------------------------------------------------------------------------------------
>
>
>
> Media Overlays Vocabulary
>
> Media Overlays properties are expressed in the meta element's property
> attribute.
>
>
>
> active-class
>
> duration
>
> narrator
>
> playback-active-class
>
>
>
>
>
>
> ----------------------------------------------------------------------------------------
>
>
>
> EPUB Accessibility Vocabulary
>
>
>
>
> ----------------------------------------------------------------------------------------
>
>
>
> Schema.org discovery metadata
>
> Discovery properties are expressed in the meta element's property
> attribute.
>
>
>
> schema:accessibilityFeature
>
> schema:accessibilityHazard
>
> schema:accessibilitySummary
>
> schema:accessMode
>
> schema:accessModeSufficient
>
>
>
>
> ----------------------------------------------------------------------------------------
>
>
>
> Conformance metadata
>
> Conformance properties are expressed in the meta element's property
> attribute and in the link element's rel attribute.
>
>
>
> dcterms:conformsTo
>
> a11y:certifiedBy
>
> a11y:certifierCredential
>
> a11y:certifierReport
>
>
>


-- 
*John Foliot* |
Senior Industry Specialist, Digital Accessibility |
W3C Accessibility Standards Contributor |

"I made this so long because I did not have time to make it shorter." -
Pascal "links go places, buttons do things"