/
package-document.feature
942 lines (744 loc) · 42.6 KB
/
package-document.feature
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
Feature: EPUB 3 ▸ Packages ▸ Package Document Checks
Checks conformance to the EPUB Packages 3.2 specification:
https://www.w3.org/publishing/epub32/epub-packages.html
In the scenarios below, checks are run against single Package Documents.
EPUBCheck is launched in 'opf' mode.
Background:
Given test files located at '/epub3/files/package-document/'
And EPUBCheck configured to check a Package Document
# 3.2 Content Conformance
Scenario: the minimal Package Document is reported as valid
When checking file 'minimal.opf'
Then no errors or warnings are reported
Scenario: a not well-formed Package Document is reported
When checking file 'conformance-xml-malformed-error.opf'
Then fatal error RSC-016 is reported (parsing error)
And error RSC-005 is reported (schema error)
And no other errors or warnings are reported
Scenario: using a not-declared namespace is not allowed
When checking file 'conformance-xml-undeclared-namespace-error.opf'
Then fatal error RSC-016 is reported (parsing error)
And error RSC-005 is reported (schema error)
And no other errors or warnings are reported
# 3.4 Pacakge Document Definition
## 3.4.1 The package element
Scenario: the unique identifier must not be empty
When checking EPUB 'package-unique-identifier-attribute-missing-error.opf'
# FIXME OPF-048 could be removed, as it is already reported as RSC-005
Then the following errors are reported
| RSC-005 | missing required attribute |
| OPF-048 | missing its required unique-identifier attribute |
And no other errors or warnings are reported
Scenario: the 'package' 'unique-identifier' attribute must be a known ID
When checking file 'package-unique-identifier-unknown-error.opf'
Then error RSC-005 is reported
And the message contains "does not resolve to a dc:identifier element"
And no other errors or warnings are reported
Scenario: the 'package' 'unique-identifier' attribute must point to a 'dc:identifier' element
When checking file 'package-unique-identifier-not-targeting-identifier-error.opf'
Then error RSC-005 is reported
And the message contains "does not resolve to a dc:identifier element"
And no other errors or warnings are reported
Scenario: the 'package' element must have a 'metadata' child element
When checking file 'package-no-metadata-element-error.opf'
Then error RSC-005 is reported (missing metadata element)
And the message contains 'missing required element "metadata"'
And error RSC-005 is reported (side effect: missing unique-identifier target)
And no other errors or warnings are reported
Scenario: the 'package' element’s 'metadata' child must be before the 'manifest' child
When checking file 'package-manifest-before-metadata-error.opf'
Then error RSC-005 is reported
And the message contains 'element "manifest" not allowed yet'
And error RSC-005 is reported
And the message contains 'element "metadata" not allowed here'
And no other errors or warnings are reported
## 3.4.2 Shared attributes
Scenario: 'id' attributes can have leading or trailing space
When checking file 'id-with-spaces-valid.opf'
Then no errors or warnings are reported
Scenario: 'id' attributes must be unique
When checking file 'id-duplicate-error.opf'
Then error RSC-005 is reported 2 times (once for each ID)
And no other errors or warnings are reported
Scenario: 'id' attributes must be unique after whitespace normalization
When checking file 'id-duplicate-with-spaces-error.opf'
Then error RSC-005 is reported 2 times (once for each ID)
And no other errors or warnings are reported
Scenario: the `xml:lang` attribute can be empty
When checking file 'lang-empty-valid.opf'
Then no other errors or warnings are reported
## 3.4.3 Metadata
### 3.4.3 The metadata element
#### 3.4.3.2 DCMES Required Elements
Scenario: 'dc:identifier' must not be empty
When checking file 'metadata-identifier-empty-error.opf'
Then error RSC-005 is reported
And the message contains "must be a string with length at least 1"
And no other errors or warnings are reported
Scenario: 'dc:identifier' starting with "urn:uuid:" should be a valid UUID
When checking file 'metadata-identifier-uuid-invalid-warning.opf'
Then warning OPF-085 is reported
And no other errors or warnings are reported
Scenario: 'dc:modified' must be defined
When checking file 'metadata-modified-missing-error.opf'
Then error RSC-005 is reported
And the message contains "dcterms:modified"
And no other errors or warnings are reported
Scenario: 'dc:modified' must be of the form 'CCYY-MM-DDThh:mm:ssZ'
When checking file 'metadata-modified-syntax-error.opf'
Then error RSC-005 is reported
And the message contains "CCYY-MM-DDThh:mm:ssZ"
And no other errors or warnings are reported
Scenario: 'dc:title' must be specified
When checking file 'metadata-title-missing-error.opf'
Then error RSC-005 is reported
And the message contains 'missing required element "dc:title"'
And no other errors or warnings are reported
Scenario: 'dc:title' must not be empty
When checking file 'metadata-title-empty-error.opf'
Then error RSC-005 is reported
And the message contains "must be a string with length at least 1"
And no other errors or warnings are reported
#### 3.4.3.3 DCMES Optional Elements
Scenario: 'dc:date' can be specified as an ISO 8601:2004 value
When checking file 'metadata-date-single-year-valid.opf'
Then no errors or warnings are reported
Scenario: 'dc:date' can be specified as a single year
When checking file 'metadata-date-single-year-valid.opf'
Then no errors or warnings are reported
Scenario: 'dc:date' value can have leading/trailng whitespace
When checking file 'metadata-date-with-whitespace-valid.opf'
Then no errors or warnings are reported
Scenario: 'dc:date' with an invalid ISO 8601:2004 syntax is reported
When checking file 'metadata-date-iso-syntax-error-warning.opf'
Then warning OPF-053 is reported
And the message contains "does not follow recommended syntax"
And no errors or warnings are reported
Scenario: 'dc:date' with an unknown format is reported
When checking file 'metadata-date-unknown-format-warning.opf'
Then warning OPF-053 is reported
And the message contains "does not follow recommended syntax"
And no errors or warnings are reported
Scenario: 'dc:source' valid values are allowed
When checking file 'metadata-source-valid.opf'
Then no errors or warnings are reported
Scenario: 'dc:type' valid values are allowed
When checking file 'metadata-type-valid.opf'
Then no errors or warnings are reported
#### 3.4.3.4 The meta Element
Scenario: a metadata’s property name must be defined
When checking file 'metadata-meta-property-empty-error.opf'
Then error RSC-005 is reported 2 times
And the message contains 'value of attribute "property" is invalid'
And no other errors or warnings are reported
Scenario: a metadata’s property name must not be a list of values
When checking file 'metadata-meta-property-list-error.opf'
Then error RSC-005 is reported (value is not an NMTOKEN)
Then error OPF-025 is reported
And the message contains "only one value must be specified"
And no other errors or warnings are reported
Scenario: a metadata’s property name must be well-formed
When checking file 'metadata-meta-property-malformed-error.opf'
Then error OPF-026 is reported
And no other errors or warnings are reported
Scenario: a metadata’s value must be defined
When checking file 'metadata-meta-value-empty-error.opf'
Then error RSC-005 is reported
And the message contains "must be a string with length at least 1"
And no other errors or warnings are reported
Scenario: 'refines' attribute MUST be a relative URL
When checking file 'metadata-refines-not-relative-error.opf'
Then error RSC-005 is reported
And the message contains "@refines must be a relative URL"
And no other errors or warnings are reported
Scenario: 'refines' attribute should use a fragment ID if refering to a Publication Resource
When checking file 'metadata-refines-not-a-fragment-warning.opf'
Then warning RSC-017 is reported
And the message contains "using a fragment identifier pointing to its manifest item"
And no other errors or warnings are reported
Scenario: 'refines' attribute, when using fragment ID, must target an existing ID
When checking file 'metadata-refines-unknown-id-error.opf'
Then error RSC-005 is reported
And the message contains "@refines missing target id"
And no other errors or warnings are reported
Scenario: 'refines' references cycles are not allowed
When checking file 'metadata-refines-cycle-error.opf'
Then error OPF-065 is reported
And no other errors or warnings are reported
Scenario: 'scheme' can be used to identify the value system
When checking file 'metadata-meta-scheme-valid.opf'
Then no errors or warnings are reported
Scenario: 'scheme' must not be list of values
When checking file 'metadata-meta-scheme-list-error.opf'
Then error RSC-005 is reported (value is not an NMTOKEN)
And error OPF-025 is reported
And no other errors or warnings are reported
Scenario: 'scheme' must not be an unknown value with no prefix
When checking file 'metadata-meta-scheme-unknown-error.opf'
Then error OPF-027 is reported
And no other errors or warnings are reported
#### 3.4.3.5 The link Element
Scenario: 'link' targets must not be manifest items
When checking file 'link-to-publication-resource-error.opf'
Then error OPF-067 is reported
And no other errors or warnings are reported
### 3.4.4 Manifest
#### 3.4.4.1 The manifest Element
#### 3.4.4.2 The item Element
Scenario: a manifest item must declare a media type
When checking file 'item-media-type-missing-error.opf'
Then error RSC-005 is reported
And the message contains 'missing required attribute "media-type"'
And no other errors or warnings are reported
Scenario: item URLs should not contain spaces
When checking file 'item-href-contains-spaces-warning.opf'
Then warning PKG-010 is reported
And no other errors or warnings are reported
Scenario: item URLs must not have a fragment identifier
When checking file 'item-href-with-fragment-error.opf'
Then error OPF-091 is reported
And no other errors or warnings are reported
Scenario: two manifest items cannot represent the same resource
When checking file 'item-duplicate-resource-error.opf'
Then error OPF-074 is reported
And no other errors or warnings are reported
Scenario: one item must have the 'nav' property
When checking file 'item-nav-missing-error.opf'
Then error RSC-005 is reported
And the message contains 'Exactly one manifest item must declare the "nav" property'
And no other errors or warnings are reported
Scenario: at most one item must have the 'nav' property
When checking file 'item-nav-multiple-error.opf'
Then error RSC-005 is reported
And the message contains 'Exactly one manifest item must declare the "nav" property'
And no other errors or warnings are reported
Scenario: the 'nav' property must be on an XHTML Content Document
When checking file 'item-nav-not-xhtml-error.opf'
Then error RSC-005 is reported
And the message contains 'the Navigation Document must be of the "application/xhtml+xml" type'
And error OPF-012 is reported ('nav' undefined for 'application/x+dtbncx+xml')
And no other errors or warnings are reported
#### 3.4.4.3 Manifest Fallbacks
Scenario: Allow non-CMT file to be in the spine if they have an XHTML Content Document fallback
Note: here an audio file is used in the spine
When checking file 'fallback-to-xhtml-valid.opf'
Then no errors or warnings are reported
Scenario: Allow an SVG Content Document to be used as a fallback
Note: here an image file is used in the spine
When checking file 'fallback-to-svg-valid.opf'
Then no errors or warnings are reported
Scenario: Allow a deep fallback chain as long as it contains a Content Document
Note: here a font file is used in the spine
When checking file 'fallback-chain-valid.opf'
Then no errors or warnings are reported
Scenario: Report a cycle in the fallback chain
When checking file 'fallback-cycle-error.opf'
Then error OPF-045 is reported (circular reference)
And error OPF-044 is reported (no Content Document fallback was found)
And no other errors or warnings are reported
Scenario: Report files that aren’t Content Documents (like audio) in spine when they don’t have a fallback
Note: here an audio file is used in the spine
When checking file 'fallback-missing-error.opf'
Then error OPF-043 is reported
And no other errors or warnings are reported
Scenario: Manifest fallback must point to an existing item ID
When checking file 'fallback-to-unknown-id-error.opf'
Then error RSC-005 is reported
And the message contains 'must resolve to another manifest item'
And no other errors or warnings are reported
Scenario: Manifest fallback must point to an existing item ID
When checking file 'fallback-to-self-error.opf'
Then error RSC-005 is reported
And the message contains 'must resolve to another manifest item'
And no other errors or warnings are reported
Scenario: Report usage of the EPUB 2 'fallback-style' attribute
When checking file 'fallback-style-error.opf'
Then error RSC-005 is reported
And the message contains 'fallback-style'
And no other errors or warnings are reported
#### 3.4.4.4 The bindings Element
Scenario: Report usage of the 'bindings' element as deprecated
When checking file 'bindings-deprecated-warning.opf'
Then warning RSC-017 is reported
And no other errors or warnings are reported
Scenario: Report a binding declared for an image resource
When checking file 'bindings-for-image-error.opf'
Then warning RSC-017 is reported (since bindings is deprecated)
And error OPF-008 is reported (to report handler for an image)
And no other errors or warnings are reported
Scenario: Report a bindings handler that is not an XHTML Content Document
When checking file 'bindings-handler-not-xhtml-error.opf'
Then warning RSC-017 is reported (since bindings is deprecated)
And error RSC-005 is reported (to report the non-XHTML handler)
And no other errors or warnings are reported
### 3.4.5 Spine
#### 3.4.5.1 The spine Element
#### 3.4.5.2 The itemref Element
Scenario: An SVG Content Document is allowed in the spine
When checking file 'spine-item-svg-valid.opf'
Then no errors or warnings are reported
Scenario: An unknown 'itemref' ID is reported
When checking file 'spine-item-unknown-error.opf'
Then error OPF-049 is reported (ID not found)
Then error RSC-005 is reported (schema error)
And no other errors or warnings are reported
Scenario: Two spine 'itemref' elements cannot reference the same manifest item
When checking file 'spine-item-duplicate-error.opf'
Then error RSC-005 is reported
And the message contains "Itemref refers to the same manifest entry as a previous itemref"
And no other errors or warnings are reported
### 3.4.6 Collections
Scenario: a collection role can be an absolute URL
When checking file 'collection-role-url-valid.opf'
Then no errors or warnings are reported
Scenario: a collection role must not be an invalid URL
Spec mismatch: this should be reported as an error
When checking file 'collection-role-url-invalid-error.opf'
Then warning OPF-070 is reported
And no other errors or warnings are reported
Scenario: a collection role URL cannot contain 'idpf.org' in its host
When checking file 'collection-role-url-idpf.org-error.opf'
Then error OPF-069 is reported
And no other errors or warnings are reported
Scenario: a collection role must not be an unknown token value
When checking file 'collection-role-unknown-error.opf'
Then error OPF-068 is reported
And no other errors or warnings are reported
Scenario: a 'manifest' collection must be the child of another collection
See http://idpf.org/epub/vocab/package/roles/manifest/
When checking file 'collection-role-manifest-toplevel-error.opf'
Then error RSC-005 is reported
And the message contains "A manifest collection must be the child of another collection"
And no other errors or warnings are reported
### 3.4.7 Legacy
#### 3.4.7.1 The meta Element
#### 3.4.7.2 The guide Element
Scenario: 'guide' should not contain two entries of the same type pointing to the same resource
When checking EPUB 'legacy-guide-duplicates-warning.opf'
Then warning RSC-017 is reported 2 times (once for each entry)
And the message contains 'Duplicate "reference" elements with the same "type" and "href" attributes'
And no other errors or warnings are reported
#### 3.4.7.3 NCX
Scenario: When an NCX document is present, it must be identified in the 'toc' attribute of the spine
When checking file 'legacy-ncx-toc-attribute-missing-error.opf'
Then error RSC-005 is reported
And the message contains "toc attribute must be set"
And no other errors or warnings are reported
Scenario: The 'toc' attribute of the spine must point to an NCX document
When checking file 'legacy-ncx-toc-attribute-not-ncx-error.opf'
Then error OPF-050 is reported
Then error RSC-005 is reported (duplicate schema error)
And no other errors or warnings are reported
# 4. Package Metadata
## 4.1 Publication Identifiers
## 4.2 Vocabulary Association Mechanisms
Scenario: the 'prefix' attribute can be used to define new prefix mappings
When checking file 'property-prefix-declaration-valid.opf'
Then no errors or warnings are reported
Scenario: reserved prefixes can be explicitly declared
When checking file 'property-prefix-declaration-reserved-explicit-valid.opf'
Then no errors or warnings are reported
Scenario: syntax errors in the 'prefix' attribute are reported
When checking file 'property-prefix-declaration-syntax-error.opf'
Then error OPF-004c is reported 2 times (the test file contains 2 syntax errors)
And no other errors or warnings are reported
Scenario: reserved prefixes should not be overridden to other vocabularies
When checking file 'property-prefix-declaration-reserved-overridden-warning.opf'
Then warning OPF-007 is reported 8 times (once for each reserved prefix)
And no other errors or warnings are reported
Scenario: default vocabularies must not be assigned a prefix
Note: This should be an error, but is currently reported as a warning
See issue 522: https://github.com/w3c/epubcheck/issues/522
When checking file 'property-prefix-declaration-default-vocabs-error.opf'
Then warning OPF-007b is reported 4 times (once for each default vocabulary)
And no other errors or warnings are reported
Scenario: A metadata property with an unknown prefix is reported
When checking file 'property-prefix-declaration-missing-error.opf'
Then error OPF-028 is reported
And no errors or warnings are reported
Scenario: The 'schema' prefix can be used in metadata properties without being declared
When checking file 'property-prefix-schema-not-declared-valid.opf'
Then no errors or warnings are reported
## 4.3 Package Rendering Metadata
### 4.3.3 General Properties
Scenario: the 'rendition:flow' property can be used to define the global flow preference
When checking file 'rendition-flow-global-valid.opf'
Then no errors or warnings are reported
Scenario: a 'rendition:flow' property with an unknown value is reported
When checking file 'rendition-flow-global-unknown-value-error.opf'
Then error RSC-005 is reported
And the message contains 'The value of the "rendition:flow" property must be'
And no other errors or warnings are reported
Scenario: the 'rendition:flow' property cannot be declared more than once
When checking file 'rendition-flow-global-duplicate-error.opf'
Then error RSC-005 is reported
And the message contains 'The "rendition:flow" property must not occur more than one time'
And no other errors or warnings are reported
Scenario: the 'rendition:flow' property cannot be used in a 'meta' element to refine a publication resource
When checking file 'rendition-flow-global-refines-error.opf'
Then error RSC-005 is reported
And the message contains "refines"
And no other errors or warnings are reported
Scenario: the 'rendition:flow' property can be used as a spine override
When checking file 'rendition-flow-itemref-valid.opf'
Then no errors or warnings are reported
Scenario: the 'rendition:flow' spine overrides values are mutually exclusive
When checking file 'rendition-flow-itemref-conflict-error.opf'
Then error RSC-005 is reported
And the message contains "are mutually exclusive"
And no other errors or warnings are reported
### 4.3.4 Fixed-Layout Properties
Scenario: the 'rendition:layout' property can be used to define the global layout preference
When checking file 'rendition-layout-global-valid.opf'
Then no errors or warnings are reported
Scenario: a 'rendition:layout' property with no value is reported
See also issue #727
When checking file 'rendition-layout-global-empty-error.opf'
Then the following errors are reported (one for the empty element, one for the consequently unexpected value)
| RSC-005 | character content of element "meta" invalid |
| RSC-005 | The value of the "rendition:layout" property must be |
And no other errors or warnings are reported
Scenario: a 'rendition:layout' property with an unknown value is reported
When checking file 'rendition-layout-global-unknown-value-error.opf'
Then error RSC-005 is reported
And the message contains 'The value of the "rendition:layout" property must be'
And no other errors or warnings are reported
Scenario: the 'rendition:layout' property cannot be declared more than once
When checking file 'rendition-layout-global-duplicate-error.opf'
Then error RSC-005 is reported
And the message contains 'The "rendition:layout" property must not occur more than one time'
And no other errors or warnings are reported
Scenario: the 'rendition:layout' property cannot be used in a 'meta' element to refine a publication resource
When checking file 'rendition-layout-global-refines-error.opf'
Then error RSC-005 is reported
And the message contains "refines"
And no other errors or warnings are reported
Scenario: the 'rendition:layout' property can be used as a spine override
When checking file 'rendition-layout-itemref-valid.opf'
Then no errors or warnings are reported
Scenario: the 'rendition:layout' spine overrides values are mutually exclusive
When checking file 'rendition-layout-itemref-conflict-error.opf'
Then error RSC-005 is reported
And the message contains "are mutually exclusive"
And no other errors or warnings are reported
Scenario: the 'rendition:page-spread-*' properties can be used without the prefix
When checking file 'rendition-page-spread-itemref-unprefixed-valid.opf'
Then no errors or warnings are reported
Scenario: the 'rendition:page-spread-*' properties values are mutually exclusive
When checking file 'rendition-page-spread-itemref-conflict-error.opf'
Then error RSC-005 is reported
And the message contains "are mutually exclusive"
And no other errors or warnings are reported
Scenario: the 'rendition:orientation' property can be used to define the global orientation preference
When checking file 'rendition-orientation-global-valid.opf'
Then no errors or warnings are reported
Scenario: a 'rendition:orientation' property with an unknown value is reported
When checking file 'rendition-orientation-global-unknown-value-error.opf'
Then error RSC-005 is reported
And the message contains 'The value of the "rendition:orientation" property must be'
And no other errors or warnings are reported
Scenario: the 'rendition:orientation' property cannot be declared more than once
When checking file 'rendition-orientation-global-duplicate-error.opf'
Then error RSC-005 is reported
And the message contains 'The "rendition:orientation" property must not occur more than one time'
And no other errors or warnings are reported
Scenario: the 'rendition:orientation' property cannot be used in a 'meta' element to refine a publication resource
When checking file 'rendition-orientation-global-refines-error.opf'
Then error RSC-005 is reported
And the message contains "refines"
And no other errors or warnings are reported
Scenario: the 'rendition:orientation' property can be used as a spine override
When checking file 'rendition-orientation-itemref-valid.opf'
Then no errors or warnings are reported
Scenario: the 'rendition:orientation' spine overrides values are mutually exclusive
When checking file 'rendition-orientation-itemref-conflict-error.opf'
Then error RSC-005 is reported
And the message contains "are mutually exclusive"
And no other errors or warnings are reported
Scenario: the 'rendition:spread' property can be used to define the global spread preference
When checking file 'rendition-spread-global-valid.opf'
Then no errors or warnings are reported
Scenario: a 'rendition:spread' property with an unknown value is reported
When checking file 'rendition-spread-global-unknown-value-error.opf'
Then error RSC-005 is reported
And the message contains 'The value of the "rendition:spread" property must be'
And no other errors or warnings are reported
Scenario: the 'rendition:spread' property cannot be declared more than once
When checking file 'rendition-spread-global-duplicate-error.opf'
Then error RSC-005 is reported
And the message contains 'The "rendition:spread" property must not occur more than one time'
And no other errors or warnings are reported
Scenario: the 'rendition:spread' property cannot be used in a 'meta' element to refine a publication resource
When checking file 'rendition-spread-global-refines-error.opf'
Then error RSC-005 is reported
And the message contains "refines"
And no other errors or warnings are reported
Scenario: the 'rendition:spread' property can be used as a spine override
When checking file 'rendition-spread-itemref-valid.opf'
Then no errors or warnings are reported
Scenario: the 'rendition:spread' spine overrides values are mutually exclusive
When checking file 'rendition-spread-itemref-conflict-error.opf'
Then error RSC-005 is reported
And the message contains "are mutually exclusive"
And no other errors or warnings are reported
Scenario: the 'rendition:spread' 'portrait' value is deprecated as a global value
When checking file 'rendition-spread-portrait-global-deprecated-warning.opf'
Then warning RSC-017 is reported
And the message contains "is deprecated"
And no other errors or warnings are reported
Scenario: the 'rendition:spread' 'spread-portrait' value is deprecated as a spine override
When checking file 'rendition-spread-portrait-itemref-deprecated-warning.opf'
Then warning RSC-017 is reported
And the message contains "is deprecated"
And no other errors or warnings are reported
Scenario: the 'rendition:viewport' property is deprecated
When checking file 'rendition-viewport-deprecated-warning.opf'
Then warning RSC-017 is reported
And the message contains "is deprecated"
And no other errors or warnings are reported
Scenario: the 'rendition:viewport' property syntax errors are reported
When checking file 'rendition-viewport-syntax-error.opf'
Then warning RSC-017 is reported (since 'viewport' is deprecated)
And error RSC-005 is reported
And the message contains 'The value of the "rendition:viewport" property must be of the form'
And no other errors or warnings are reported
Scenario: the 'rendition:viewport' property cannot be declared more than once
When checking file 'rendition-viewport-duplicate-error.opf'
Then warning RSC-017 is reported 2 times (since 'viewport' is deprecated)
And error RSC-005 is reported
And the message contains 'The "rendition:viewport" property must not occur more than one time as a global value'
And no other errors or warnings are reported
# C. Meta Properties Vocabulary
Scenario: 'authority' metadata can refine a subject expression
When checking file 'metadata-meta-authority-valid.opf'
Then no errors or warnings are reported
Scenario: 'authority' metadata can only refine a subject expression
When checking file 'metadata-meta-authority-refines-disallowed-error.opf'
Then error RSC-005 is reported
And the message contains 'Property "authority" must refine a "subject" property'
Then no errors or warnings are reported
Scenario: 'authority' metadata must be associated to a term
When checking file 'metadata-meta-authority-no-term-error.opf'
Then error RSC-005 is reported
And the message contains "A term property must be associated"
And no other errors or warnings are reported
Scenario: 'authority' metadata must not be defined more than once
When checking file 'metadata-meta-authority-cardinality-error.opf'
Then error RSC-005 is reported
And the message contains "Only one pair of authority and term properties"
And no other errors or warnings are reported
Scenario: 'belongs-to-collection' metadata can identify the publication’s collection
When checking file 'metadata-meta-collection-valid.opf'
Then no errors or warnings are reported
Scenario: 'belongs-to-collection' metadata can only refine other 'belongs-to-collection' metadata
When checking file 'metadata-meta-collection-refines-non-collection-error.opf'
Then error RSC-005 is reported
And the message contains 'Property "belongs-to-collection" can only refine other "belongs-to-collection" properties'
And no other errors or warnings are reported
Scenario: 'collection-type' cannot be used as a primary metadata
When checking file 'metadata-meta-collection-type-refines-missing-error.opf'
Then error RSC-005 is reported
And the message contains 'Property "collection-type" must refine a "belongs-to-collection" property'
And no other errors or warnings are reported
Scenario: 'collection-type' metadata can only refine a 'belongs-to-collection' property
When checking file 'metadata-meta-collection-type-refines-non-collection-error.opf'
Then error RSC-005 is reported
And the message contains 'Property "collection-type" must refine a "belongs-to-collection" property'
And no other errors or warnings are reported
Scenario: 'collection-type' metadata cannot be defined more than once to refine the same expression
When checking file 'metadata-meta-collection-type-cardinality-error.opf'
Then error RSC-005 is reported
And the message contains '"collection-type" cannot be declared more than once'
And no other errors or warnings are reported
Scenario: 'display-seq' metadata is allowed
When checking file 'metadata-meta-display-seq-valid.opf'
Then no errors or warnings are reported
Scenario: 'display-seq' metadata cannot be defined more than once to refine the same expression
When checking file 'metadata-meta-display-seq-cardinality-error.opf'
Then error RSC-005 is reported
And the message contains '"display-seq" cannot be declared more than once'
And no other errors or warnings are reported
Scenario: 'file-as' metadata is allowed
When checking file 'metadata-meta-file-as-valid.opf'
Then no errors or warnings are reported
Scenario: 'file-as' metadata cannot be defined more than once to refine the same expression
When checking file 'metadata-meta-file-as-cardinality-error.opf'
Then error RSC-005 is reported
And the message contains '"file-as" cannot be declared more than once'
And no other errors or warnings are reported
Scenario: 'group-position' metadata is allowed
When checking file 'metadata-meta-group-position-valid.opf'
Then no errors or warnings are reported
Scenario: 'group-position' metadata cannot be defined more than once to refine the same expression
When checking file 'metadata-meta-group-position-cardinality-error.opf'
Then error RSC-005 is reported
And the message contains '"group-position" cannot be declared more than once'
And no other errors or warnings are reported
Scenario: 'identifier-type' metadata can only refine a 'source' or 'identifier' property
When checking file 'metadata-meta-identifier-type-refines-disallowed-error.opf'
Then error RSC-005 is reported
And the message contains 'Property "identifier-type" must refine an "identifier" or "source" property'
And no other errors or warnings are reported
Scenario: 'identifier-type' metadata cannot be defined more than once to refine the same expression
When checking file 'metadata-meta-identifier-type-cardinality-error.opf'
Then error RSC-005 is reported
And the message contains '"identifier-type" cannot be declared more than once'
And no other errors or warnings are reported
Scenario: 'meta-auth' metadata is deprecated
When checking file 'metadata-meta-meta-auth-deprecated-warning.opf'
Then warning RSC-017 is reported
And the message contains "the meta-auth property is deprecated"
And no other errors or warnings are reported
Scenario: 'role' metadata can be used once or more to refine a creator, contributor, or publisher
When checking file 'metadata-meta-role-valid.opf'
Then no errors or warnings are reported
Scenario: 'role' metadata cannot be used to refine properties other than creator, contributor, or publisher
When checking file 'metadata-meta-role-refines-disallowed-error.opf'
Then error RSC-005 is reported
And the message contains '"role" must refine a "creator", "contributor", or "publisher" property'
And no other errors or warnings are reported
Scenario: 'source-of' metadata can be used to refine the pagination source
When checking file 'metadata-meta-source-of-valid.opf'
Then no errors or warnings are reported
Scenario: 'source-of' metadata value must be "pagination"
When checking file 'metadata-meta-source-of-value-unknown-error.opf'
Then error RSC-005 is reported
And the message contains 'The "source-of" property must have the value "pagination"'
And no other errors or warnings are reported
Scenario: 'source-of' metadata cannot be used as a primary metadata
When checking file 'metadata-meta-source-of-refines-missing-error.opf'
Then error RSC-005 is reported
And the message contains 'The "source-of" property must refine a "source" property'
And no other errors or warnings are reported
Scenario: 'source-of' metadata must refine a 'dc:source' metadata entry
When checking file 'metadata-meta-source-of-refines-not-dcsource-error.opf'
Then error RSC-005 is reported
And the message contains 'The "source-of" property must refine a "source" property'
And no other errors or warnings are reported
Scenario: 'source-of' metadata cannot be defined more than once to refine the same expression
When checking file 'metadata-meta-source-of-cardinality-error.opf'
Then error RSC-005 is reported
And the message contains '"source-of" cannot be declared more than once'
And no other errors or warnings are reported
Scenario: 'term' metadata can refine a subject expression
When checking file 'metadata-meta-term-valid.opf'
Then no errors or warnings are reported
Scenario: 'term' metadata can only refine a subject expression
When checking file 'metadata-meta-term-refines-disallowed-error.opf'
Then error RSC-005 is reported
And the message contains 'Property "term" must refine a "subject" property'
Then no errors or warnings are reported
Scenario: 'term' metadata must be associated to an authority
When checking file 'metadata-meta-term-no-authority-error.opf'
Then error RSC-005 is reported
And the message contains "An authority property must be associated"
And no other errors or warnings are reported
Scenario: 'term' metadata must not be defined more than once
When checking file 'metadata-meta-term-cardinality-error.opf'
Then error RSC-005 is reported
And the message contains "Only one pair of authority and term properties"
And no other errors or warnings are reported
Scenario: 'title-type' metadata can be used to refine a title expression
When checking file 'metadata-meta-title-type-valid.opf'
Then no errors or warnings are reported
Scenario: 'title-type' metadata can only refine a 'title' expression
When checking file 'metadata-meta-title-type-refines-disallowed-error.opf'
Then error RSC-005 is reported
And the message contains 'Property "title-type" must refine a "title" property'
And no other errors or warnings are reported
Scenario: 'title-type' metadata cannot be defined more than once to refine the same expression
When checking file 'metadata-meta-title-type-cardinality-error.opf'
Then error RSC-005 is reported
And the message contains '"title-type" cannot be declared more than once'
And no other errors or warnings are reported
# D. Metadata Link Vocabulary
Scenario: the link 'rel' attribute can have multiple properties
When checking file 'link-rel-multiple-properties-valid.opf'
Then no errors or warnings are reported
Scenario: an 'acquire' link can identify the full version of the publication
When checking file 'link-rel-acquire-valid.opf'
Then no errors or warnings are reported
Scenario: an 'alternate' link can identify an alternate version of the Package Document
When checking file 'link-rel-alternate-valid.opf'
Then no errors or warnings are reported
Scenario: an 'alternate' link must not be paired with other keywords
When checking file 'link-rel-alternate-with-other-keyword-error.opf'
Then error OPF-089 is reported
And no other errors or warnings are reported
Scenario: a 'record' link can point to a local record
When checking file 'link-rel-record-local-valid.opf'
Then no errors or warnings are reported
Scenario: a 'record' link can point to a remote record
When checking file 'link-rel-record-remote-valid.opf'
Then no errors or warnings are reported
Scenario: 'record' link can be paired with other keywords
When checking file 'link-rel-record-with-other-keyword-valid.opf'
Then no errors or warnings are reported
Scenario: a 'record' link must have a 'media-type' attribute
When checking file 'link-rel-record-mediatype-missing-error.opf'
Then error RSC-005 is reported
And the message contains "media-type"
And no other errors or warnings are reported
Scenario: a 'record' link type can be further identified with a 'properties' attribute
When checking file 'link-rel-record-properties-valid.opf'
And no errors or warnings are reported
Scenario: a 'record' link with an unknown identifier property is reported
When checking file 'link-rel-record-properties-undefined-error.opf'
Then error OPF-027 is reported
And no other errors or warnings are reported
Scenario: a 'record' link with an empty identifier property is reported
When checking file 'link-rel-record-properties-empty-error.opf'
Then error RSC-005 is reported
And the message contains 'value of attribute "properties" is invalid'
And no other errors or warnings are reported
Scenario: a 'record' link cannot refine another property or resource
When checking file 'link-rel-record-refines-error.opf'
Then error RSC-005 is reported
And the message contains 'must not have a "refines" attribute'
And no other errors or warnings are reported
Scenario: '*-record' links are deprecated
When checking file 'link-rel-record-deprecated-warning.opf'
Then the following warnings are reported
| OPF-086 | "marc21xml-record" is deprecated |
| OPF-086 | "mods-record" is deprecated |
| OPF-086 | "onix-record" is deprecated |
| OPF-086 | "xmp-record" is deprecated |
And no other errors or warnings are reported
Scenario: a 'voicing' link can identify the aural representation of metadata
When checking file 'link-rel-voicing-valid.opf'
Then no errors or warnings are reported
Scenario: a 'voicing' link must refine another property or resource
When checking file 'link-rel-voicing-as-publication-metadata-error.opf'
Then error RSC-005 is reported
And the message contains 'must have a "refines" attribute'
And no other errors or warnings are reported
Scenario: a 'voicing' link must have a 'media-type' attribute
When checking file 'link-rel-voicing-mediatype-missing-error.opf'
Then error RSC-005 is reported
And the message contains 'must have a "media-type" attribute'
And no other errors or warnings are reported
Scenario: a 'voicing' link resource must have an audio media type
When checking file 'link-rel-voicing-mediatype-not-audio-error.opf'
Then error RSC-005 is reported
And the message contains 'must have a "media-type" attribute identifying an audio MIME type'
And no other errors or warnings are reported
Scenario: 'xml-signature' links are deprecated
When checking file 'link-rel-xml-signature-deprecated-warning.opf'
Then warning OPF-086 is reported
And the message contains '"xml-signature" is deprecated'
And no other errors or warnings are reported
# E. Manifest Properties Vocabulary
Scenario: An unknown item property in the default vocab is reported
When checking file 'item-property-unknown-error.opf'
Then error OPF-027 is reported
And no errors or warnings are reported
Scenario: The 'cover-image' item property must occur at most once
When checking file 'item-property-cover-image-multiple-error.opf'
Then error RSC-005 is reported
And the message contains "cover-image"
And no other errors or warnings are reported
Scenario: The 'cover-image' item property must only be used on images
When checking file 'item-property-cover-image-wrongtype-error.opf'
Then error OPF-012 is reported
And no other errors or warnings are reported
# F. Spine Properties Vocabulary