Skip to content

Meta properties + one or zero cardinality #1121

Closed
@JayPanoz

Description

Hi,

At this point I can’t really tell whether it’s a bug but I guess it’s at least worth opening an issue in case it can be clarified and labeled properly for people in the future in case it’s a wontfix.

So I’m referring to the “meta properties” section of EPUB Packages 3.2.

So let’s start with zero or more cardinality. Obviously, people are aware of alternate-script e.g.

<dc:creator id="creator1">Jane Doe</dc:creator>
<meta property="alternate-script" refines="#creator1" xml:lang="ja">山田花子</meta>
<meta property="alternate-script" refines="#creator1" xml:lang="ar">فُلانة الفُلانيّة</meta>

Which is obviously fine.

But then I have a doubt with zero or one cardinality, as EPUBCheck doesn’t report anything for:

<dc:creator id="creator1">Jane Doe</dc:creator>
<meta property="role" refines="#creator1" scheme="marc:relators">aut</meta>
<meta property="role" refines="#creator1" scheme="marc:relators">edt</meta>

nor:

<dc:title id="t1">Title of the book</dc:title>
<meta property="title-type" refines="#t1">main</meta>
<meta property="title-type" refines="#t1">subtitle</meta>

Is this a bug, is this the spec? I honestly can’t tell at this point – and we have a hard time finding a common interpretation amongst a group of people, hence why I prefer to open this issue too.

Mind you, it would not be unreasonable for a creator or contributor to have different roles in a contribution so OK at least that makes sense. And then I go back to the introduction of the section and there is this:

the Cardinality field indicates the number of times the property MAY be attached to another property.

And now as someone who has to parse that, I must admit I’m not so sure what to make of that anymore. I know of at least one authoring app that will enforce only one meta for role, title-type, etc. (Zero or 1 cardinality) even if you put multiple in its metadata editor but are they right, or wrong?

Anyways, here’s a test file if that happens to be a bug.

refine-role.zip

Metadata

Assignees

No one assigned

    Labels

    spec: EPUB 3.xImpacting the support of EPUB 3.x specificationsstatus: has PRThe issue is being processed in a pull requesttype: false-negativeThis issue is about invalid content being incorrectly accepted

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions