~user-none/lebookread/trunk : revision 1

1

<?xml version="1.0" encoding="utf-8"?>

2

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

3

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

4

5

<head>

6

7

content="HTML Tidy for Mac OS X (vers 1st December 2004), see www.w3.org" />

8

<title>

9

Open Packaging Format (OPF) 2.0 v1.0

10

</title>

11

12

content="text/html; charset=utf-8" />

13

14

/*<![CDATA[*/

15

del {

16

display:none

17

}

18

19

ins {

20

text-decoration:none

21

}

22

23

a {

24

color: #4ca721;

25

background: transparent;

26

}

27

28

a:VISITED {

29

color: #4ca721;

30

background: transparent;

31

}

32

33

a:HOVER {

34

color: Red;

35

background: transparent;

36

}

37

38

a.SectionTitle {

39

color: Black;

40

background: transparent;

41

text-decoration: underline;

42

}

43

44

a.SectionTitle:VISITED {

45

color: Black;

46

background: transparent;

47

text-decoration: underline;

48

}

49

50

a.SectionTitle:HOVER {

51

color: Black;

52

background: transparent;

53

text-decoration: underline;

54

}

55

56

a.SubsectionTitle {

57

color: Black;

58

background: transparent;

59

text-decoration: none;

60

}

61

62

a.SubsectionTitle:VISITED {

63

color: Black;

64

background: transparent;

65

text-decoration: none;

66

}

67

68

a.SubsectionTitle:HOVER {

69

color: Black;

70

background: transparent;

71

text-decoration: none;

72

}

73

74

a.TOC {

75

color: #4ca721;

76

background: transparent;

77

text-decoration: none;

78

}

79

80

a.TOC:VISITED {

81

color: #4ca721;

82

background: transparent;

83

text-decoration: none;

84

}

85

86

a.TOC:HOVER {

87

color: Red;

88

background: transparent;

89

text-decoration: none;

90

}

91

92

body {

93

padding-top: 2em;

94

padding-right: 1em;

95

padding-bottom: 2em;

96

padding-left: 3em;

97

margin: 0;

98

font-family: sans-serif;

99

color: black;

100

background: white;

101

background-position: top left;

102

background-attachment: fixed;

103

background-repeat: no-repeat;

104

}

105

106

div.Actors {

107

margin-bottom: 2em;

108

}

109

110

div.DefinitionList {

111

display: block;

112

}

113

114

div.Head {

115

116

}

117

118

div.InlineDefinitionList {

119

display: block;

120

margin-left: 1.5em;

121

margin-bottom: 1em;

122

}

123

124

div.Section {

125

padding-top: 0em;

126

padding-bottom: 0em;

127

padding-left: 0em;

128

padding-right: 0em;

129

margin-left: 1em;

130

margin-top: 1.5em;

131

margin-bottom: 0.5em;

132

}

133

134

div.TOC {

135

padding-top: 1.5em;

136

padding-bottom: 1em;

137

}

138

139

div.TOCSection {

140

padding-top: 0em;

141

padding-bottom: 0.5em;

142

}

143

144

h1.SectionTitle {

145

font-size: 140%;

146

font-family: sans-serif;

147

color: Black;

148

padding: 0px;

149

margin-top: 0.5em;

150

margin-bottom: 0.2em;

151

font-weight: bold;

152

text-decoration: underline;

153

}

154

155

h1.AppendixTitle {

156

font-size: 170%;

157

font-family: sans-serif;

158

color: Black;

159

padding: 0px;

160

margin-top: 0.5em;

161

margin-bottom: 0.5em;

162

font-weight: bold;

163

text-decoration: underline;

164

}

165

166

h2.SectionTitle {

167

font-size: 140%;

168

font-family: sans-serif;

169

color: Black;

170

padding: 0px;

171

margin-top: 0.5em;

172

margin-bottom: 0.2em;

173

font-weight: bold;

174

text-decoration: underline;

175

}

176

177

h2.SubsectionTitle {

178

font-size: 120%;

179

font-family: sans-serif;

180

color: Black;

181

padding: 0px;

182

margin-top: 0.5em;

183

margin-bottom: 0.2em;

184

font-weight: bold;

185

text-decoration: underline;

186

}

187

188

h3.SubsectionTitle {

189

font-size: 120%;

190

font-family: sans-serif;

191

color: Black;

192

padding: 0px;

193

margin-top: 0.5em;

194

margin-bottom: 0.2em;

195

font-weight: bold;

196

text-decoration: underline;

197

}

198

199

h3.SubsubsectionTitle {

200

font-size: 100%;

201

font-family: sans-serif;

202

color: Black;

203

padding: 0px;

204

margin-top: 0.5em;

205

margin-bottom: 0.2em;

206

font-weight: bold;

207

text-decoration: none;

208

}

209

210

h4.SubsubsectionTitle {

211

font-size: 100%;

212

font-family: sans-serif;

213

color: Black;

214

padding: 0px;

215

margin-top: 0.5em;

216

margin-bottom: 0.2em;

217

font-weight: bold;

218

text-decoration: none;

219

}

220

221

h4.SubsubsubsectionTitle {

222

font-size: 100%;

223

font-family: sans-serif;

224

color: Black;

225

padding: 0px;

226

margin-top: 0.5em;

227

margin-bottom: 0.2em;

228

font-weight: bold;

229

text-decoration: none;

230

font-style: italic;

231

}

232

233

h5.SubsubsubsectionTitle {

234

font-size: 100%;

235

font-family: sans-serif;

236

color: Black;

237

padding: 0px;

238

margin-top: 0.5em;

239

margin-bottom: 0.2em;

240

font-weight: bold;

241

text-decoration: none;

242

font-style: italic;

243

}

244

245

h5.SubsubsubsubsectionTitle {

246

font-size: 100%;

247

font-family: sans-serif;

248

color: Black;

249

padding: 0px;

250

margin-top: 0.5em;

251

margin-bottom: 0.2em;

252

text-decoration: none;

253

font-weight: bold;

254

}

255

256

h6.SubsubsubsubsectionTitle {

257

font-size: 100%;

258

font-family: sans-serif;

259

color: Black;

260

padding: 0px;

261

margin-top: 0.5em;

262

margin-bottom: 0.2em;

263

text-decoration: none;

264

font-weight: bold;

265

}

266

267

h6.SubsubsubsubsubsectionTitle {

268

font-size: 100%;

269

font-family: sans-serif;

270

color: Black;

271

padding: 0px;

272

margin-top: 0.5em;

273

margin-bottom: 0.2em;

274

font-weight: normal;

275

text-decoration: none;

276

font-style: italic;

277

}

278

279

h7.SubsubsubsubsubsectionTitle {

280

font-size: 100%;

281

font-family: sans-serif;

282

color: Black;

283

padding: 0px;

284

margin-top: 0.5em;

285

margin-bottom: 0.2em;

286

font-weight: normal;

287

text-decoration: none;

288

font-style: italic;

289

}

290

291

img.Head {

292

border: 0px;

293

}

294

295

li {

296

margin-left: 1em;

297

margin-bottom: 0.3em;

298

}

299

300

ol {

301

margin-top: 0.5em;

302

padding-top: 0em;

303

}

304

305

ol.BulletStyle_lower-alpha {

306

list-style-type: lower-alpha;

307

margin-top: 0.5em;

308

padding-top: 0em;

309

}

310

311

ol.BulletStyle_lower-roman {

312

list-style-type: lower-roman;

313

margin-top: 0.5em;

314

padding-top: 0em;

315

}

316

317

ol.BulletStyle_upper-alpha {

318

list-style-type: upper-alpha;

319

margin-top: 0.5em;

320

padding-top: 0em;

321

}

322

323

ol.BulletStyle_upper-roman {

324

list-style-type: upper-roman;

325

margin-top: 0.5em;

326

padding-top: 0em;

327

}

328

329

p.Actor {

330

padding: 0px;

331

margin-top: 0px;

332

margin-left: 0px;

333

margin-right: 0px;

334

margin-bottom: 0.2em;

335

text-indent: 2em;

336

}

337

338

p.ActorSubtitle {

339

font-size: 120%;

340

font-family: sans-serif;

341

color: Black;

342

padding: 0px;

343

margin-top: 0.5em;

344

margin-bottom: 0.5em;

345

font-weight: bold;

346

text-decoration: underline;

347

}

348

349

p.AppendixTitle {

350

font-size: 170%;

351

font-family: sans-serif;

352

color: Black;

353

padding: 0px;

354

margin-top: 0.5em;

355

margin-bottom: 0.5em;

356

font-weight: bold;

357

text-decoration: underline;

358

}

359

360

p.Copy {

361

margin-top: 0.4em;

362

margin-bottom: 0.4em;

363

text-indent: 1.5em;

364

}

365

366

p.DefinitionCopy {

367

text-indent: 1.5em;

368

padding-top: 0.1em;

369

padding-bottom: 0.1em;

370

margin: 0px;

371

}

372

373

p.DefinitionName {

374

color: #1E90FF;

375

font-weight: bold;

376

padding-bottom: 0px;

377

margin-bottom: 0.5em;

378

text-transform: uppercase;

379

}

380

381

p.Copyright {

382

font-size: 60%;

383

font-weight: bold;

384

}

385

386

p.Logo {

387

388

}

389

390

p.SectionTitle {

391

font-size: 140%;

392

font-family: sans-serif;

393

color: Black;

394

padding: 0px;

395

margin-top: 0.5em;

396

margin-bottom: 0.2em;

397

font-weight: bold;

398

text-decoration: underline;

399

}

400

401

p.SubsectionTitle {

402

font-size: 120%;

403

font-family: sans-serif;

404

color: Black;

405

padding: 0px;

406

margin-top: 0.5em;

407

margin-bottom: 0.2em;

408

font-weight: bold;

409

text-decoration: underline;

410

}

411

412

p.SubsubsectionTitle {

413

font-size: 100%;

414

font-family: sans-serif;

415

color: Black;

416

padding: 0px;

417

margin-top: 0.5em;

418

margin-bottom: 0.2em;

419

font-weight: bold;

420

text-decoration: none;

421

}

422

423

p.SubsubsubsectionTitle {

424

font-size: 100%;

425

font-family: sans-serif;

426

color: Black;

427

padding: 0px;

428

margin-top: 0.5em;

429

margin-bottom: 0.2em;

430

font-weight: bold;

431

text-decoration: none;

432

font-style: italic;

433

}

434

435

p.SubsubsubsubsectionTitle {

436

font-size: 100%;

437

font-family: sans-serif;

438

color: Black;

439

padding: 0px;

440

margin-top: 0.5em;

441

margin-bottom: 0.2em;

442

text-decoration: none;

443

font-weight: bold;

444

}

445

446

p.SubsubsubsubsubsectionTitle {

447

font-size: 100%;

448

font-family: sans-serif;

449

color: Black;

450

padding: 0px;

451

margin-top: 0.5em;

452

margin-bottom: 0.2em;

453

font-weight: normal;

454

text-decoration: none;

455

font-style: italic;

456

}

457

458

p.Status {

459

font-size: 140%;

460

font-family: sans-serif;

461

color: #4ca721;

462

padding-top: 0px;

463

padding-bottom: 1em;

464

margin: 0px;

465

}

466

467

p.Title {

468

font-size: 170%;

469

font-family: sans-serif;

470

color: #4ca721;

471

padding: 0px;

472

margin-top: 0px;

473

margin-bottom: 0.3em;

474

font-weight: bold;

475

}

476

477

p.TOCItem {

478

font-size: 120%;

479

font-family: sans-serif;

480

color: #4ca721;

481

padding: 0px;

482

margin-top: 0em;

483

margin-bottom: 0.1em;

484

text-indent: 2em;

485

font-weight: bold;

486

}

487

488

p.TOCItem2 {

489

font-size: 100%;

490

font-family: sans-serif;

491

color: #4ca721;

492

padding: 0px;

493

margin-top: 0px;

494

margin-bottom: 0.1em;

495

text-indent: 4em;

496

font-weight: bold;

497

}

498

499

p.TOCItem3 {

500

font-size: 85%;

501

font-family: sans-serif;

502

color: #4ca721;

503

padding: 0px;

504

margin-top: 0px;

505

margin-bottom: 0.1em;

506

text-indent: 6em;

507

font-weight: bold;

508

}

509

510

p.TOCItem4 {

511

font-size: 85%;

512

font-family: sans-serif;

513

color: #4ca721;

514

padding: 0px;

515

margin-top: 0px;

516

margin-bottom: 0.1em;

517

text-indent: 8em;

518

font-weight: bold;

519

}

520

521

p.TOCItem5 {

522

font-size: 75%;

523

font-family: sans-serif;

524

color: #4ca721;

525

padding: 0px;

526

margin-top: 0px;

527

margin-bottom: 0.1em;

528

text-indent: 12em;

529

font-weight: bold;

530

}

531

532

p.TOCItem6 {

533

font-size: 75%;

534

font-family: sans-serif;

535

color: #4ca721;

536

padding: 0px;

537

margin-top: 0px;

538

margin-bottom: 0.1em;

539

text-indent: 14em;

540

font-weight: bold;

541

font-style: italic;

542

}

543

544

545

p.TOCTitle {

546

font-size: 140%;

547

font-family: sans-serif;

548

color: Black;

549

padding: 0px;

550

margin-top: 0px;

551

margin-bottom: 0.5em;

552

font-weight: bold;

553

text-decoration: underline;

554

}

555

556

pre.Example {

557

font-family: monospace;

558

border: 1px solid #4ca721;

559

background-color: #DCDCDC;

560

white-space: -moz-pre-wrap;

561

padding: 0.5em;

562

margin-left: 1em;

563

margin-top: 1em;

564

margin-bottom: 1em;

565

width: 90%;

566

font-size: 100%;

567

}

568

569

span.Attribute {

570

font-family: monospace;

571

}

572

573

span.AttributeValue {

574

font-family: monospace;

575

font-style: italic;

576

}

577

578

span.Code {

579

font-family: monospace;

580

color: Green;

581

}

582

583

span.CSSProperty {

584

font-family: monospace;

585

font-weight: bold;

586

color: purple;

587

}

588

589

span.CSSPropertyValue {

590

font-family: monospace;

591

font-style: italic;

592

color: Purple;

593

}

594

595

span.Element {

596

font-family: monospace;

597

font-weight: bold;

598

}

599

600

span.Emphasis {

601

font-weight: bold;

602

}

603

604

span.File {

605

font-family: monospace;

606

color: Green;

607

}

608

609

span.FormalName {

610

font-style: italic;

611

}

612

613

span.MIMEType {

614

font-family: monospace;

615

font-style: italic;

616

color: Red;

617

}

618

619

span.Namespace {

620

font-family: monospace;

621

font-style: italic;

622

color: Blue;

623

}

624

625

span.Note {

626

font-style: italic;

627

}

628

629

span.RFC {

630

font-weight: bold;

631

}

632

633

span.Underline {

634

text-decoration: underline;

635

}

636

637

table {

638

width: 100%;

639

border: 1px solid Gray;

640

margin-top: 1em;

641

margin-bottom: 1em;

642

padding: 0px;

643

border-collapse: collapse;

644

}

645

646

thead {

647

font-weight: bold;

648

}

649

650

td {

651

border: 1px solid Gray;

652

vertical-align: top;

653

padding: 0.5em;

654

}

655

656

td.header {

657

font-weight: bold;

658

font-size: 140%;

659

}

660

661

td.MarcName {

662

font-weight: bold;

663

width: 30%;

664

vertical-align: top;

665

border-bottom: 1px solid black;

666

border-left: 0px;

667

border-right: 0px;

668

border-top: 0px;

669

margin-left: 0px;

670

margin-right: 0px;

671

}

672

673

td.MarcValue {

674

width: 70%;

675

vertical-align: top;

676

border-bottom: 1px solid black;

677

border-left: 0px;

678

border-right: 0px;

679

border-top: 0px;

680

}

681

682

td.property {

683

font-family: monospace;

684

font-weight: bold;

685

}

686

687

td.propertyvalue {

688

font-family: monospace;

689

text-indent: 3em;

690

font-style: italic;

691

}

692

693

td.propertyvalue2 {

694

font-family: monospace;

695

text-indent: 0em;

696

font-style: italic;

697

}

698

699

td.subheader {

700

font-weight: bold;

701

font-size: 120%;

702

}

703

704

td.subsubheader {

705

font-weight: bold;

706

font-size: 100%;

707

}

708

709

ul {

710

list-style: disc;

711

margin-top: 0.5em;

712

padding-top: 0em;

713

}

714

715

ul.AuthorList {

716

list-style: none;

717

margin-top: 0.5em;

718

padding-top: 0em;

719

}

720

/*]]>*/

721

</style>

722

</head>

723

<body>

724

725

726

<a href="http://www.idpf.org/"><img class="Head"

727

src=""

728

alt="IDPF Logo"

729

title="International Digital Publishing Forum"

730

height="56"

731

width="125" /></a>

732

733

734

735

Open Packaging Format (OPF) 2.0 v<del>0.987</del><ins>1.0</ins>

736

737

738

739

Recommended Specification <del>July 11, 2007</del><ins>September 11, 2007</ins>

740

741

742

743

744

745

746

747

748

Reproduction and dissemination of this work with changes is prohibited except with the

749

written permission of the International Digital Publishing Forum.

750

751

</div>

752

753

754

755

Table of Contents

756

757

758

759

760

<a class="TOC"

761

href="#Section1.0"

762

id="TOC1.0"

763

name="TOC1.0">1.0: Overview</a>

764

765

766

767

<a class="TOC"

768

href="#Section1.1"

769

id="TOC1.1"

770

name="TOC1.1">1.1: Purpose and Scope</a>

771

772

773

774

<a class="TOC"

775

href="#Section1.2"

776

id="TOC1.2"

777

name="TOC1.2">1.2: Definitions</a>

778

779

780

781

<a class="TOC"

782

href="#Section1.3"

783

id="TOC1.3"

784

name="TOC1.3">1.3: Relationship to Other Specifications</a>

785

786

787

788

<a class="TOC"

789

href="#Section1.3.1"

790

id="TOC1.3.1"

791

name="TOC1.3.1">1.3.1: Relationship to XML</a>

792

793

794

795

<a class="TOC"

796

href="#Section1.3.2"

797

id="TOC1.3.2"

798

name="TOC1.3.2">1.3.2: Relationship to XML Namespaces</a>

799

800

801

802

<a class="TOC"

803

href="#Section1.3.3"

804

id="TOC1.3.3"

805

name="TOC1.3.3">1.3.3: Relationship to Dublin Core</a>

806

807

808

809

<a class="TOC"

810

href="#Section1.3.4"

811

id="TOC1.3.4"

812

name="TOC1.3.4">1.3.4: Relationship to Unicode</a>

813

814

815

816

<a class="TOC"

817

href="#Section1.4"

818

id="TOC1.4"

819

name="TOC1.4">1.4: Conformance</a>

820

821

822

823

<a class="TOC"

824

href="#Section1.4.1"

825

id="TOC1.4.1"

826

name="TOC1.4.1">1.4.1: Package Conformance</a>

827

828

829

830

<a class="TOC"

831

href="#Section1.4.1.1"

832

id="TOC1.4.1.1"

833

name="TOC1.4.1.1">1.4.1.1: Package Conformance</a>

834

835

836

837

<a class="TOC"

838

href="#Section1.4.1.2"

839

id="TOC1.4.1.2"

840

name="TOC1.4.1.2">1.4.1.2: Publication Conformance</a>

841

842

843

844

<a class="TOC"

845

href="#Section1.4.2"

846

id="TOC1.4.2"

847

name="TOC1.4.2">1.4.2: Reading System Conformance</a>

848

849

850

851

<a class="TOC"

852

href="#Section1.4.3"

853

id="TOC1.4.3"

854

name="TOC1.4.3">1.4.3: Compatibility of OPF Version 2.0</a>

855

856

857

858

<del><a class="TOC"

859

href="#Section1.5"

860

id="TOC1.5"

861

name="TOC1.5">1.5: Accessibility</a></del>

862

863

</div>

864

865

866

867

<a class="TOC"

868

href="#Section2.0"

869

id="TOC2.0"

870

name="TOC2.0">2.0: The OPF Package Document</a>

871

872

873

874

<a class="TOC"

875

href="#Section2.1"

876

id="TOC2.1"

877

name="TOC2.1">2.1: Package Identity</a>

878

879

880

881

<a class="TOC"

882

href="#Section2.2"

883

id="TOC2.2"

884

name="TOC2.2">2.2: Publication Metadata</a>

885

886

887

888

<a class="TOC"

889

href="#Section2.2.1"

890

id="TOC2.2.1"

891

name="TOC2.2.1">2.2.1: <title> </title></a>

892

893

894

895

<a class="TOC"

896

href="#Section2.2.2"

897

id="TOC2.2.2"

898

name="TOC2.2.2">2.2.2: <creator>

899

</creator></a>

900

901

902

903

<a class="TOC"

904

href="#Section2.2.3"

905

id="TOC2.2.3"

906

name="TOC2.2.3">2.2.3: <subject>

907

</subject></a>

908

909

910

911

<a class="TOC"

912

href="#Section2.2.4"

913

id="TOC2.2.4"

914

name="TOC2.2.4">2.2.4: <description>

915

</description></a>

916

917

918

919

<a class="TOC"

920

href="#Section2.2.5"

921

id="TOC2.2.5"

922

name="TOC2.2.5">2.2.5: <publisher>

923

</publisher></a>

924

925

926

927

<a class="TOC"

928

href="#Section2.2.6"

929

id="TOC2.2.6"

930

name="TOC2.2.6">2.2.6: <contributor>

931

</contributor></a>

932

933

934

935

<a class="TOC"

936

href="#Section2.2.7"

937

id="TOC2.2.7"

938

name="TOC2.2.7">2.2.7: <date> </date></a>

939

940

941

942

<a class="TOC"

943

href="#Section2.2.8"

944

id="TOC2.2.8"

945

name="TOC2.2.8">2.2.8: <type> </type></a>

946

947

948

949

<a class="TOC"

950

href="#Section2.2.9"

951

id="TOC2.2.9"

952

name="TOC2.2.9">2.2.9: <format> </format></a>

953

954

955

956

<a class="TOC"

957

href="#Section2.2.10"

958

id="TOC2.2.10"

959

name="TOC2.2.10">2.2.10: <identifier>

960

</identifier></a>

961

962

963

964

<a class="TOC"

965

href="#Section2.2.11"

966

id="TOC2.2.11"

967

name="TOC2.2.11">2.2.11: <source>

968

</source></a>

969

970

971

972

<a class="TOC"

973

href="#Section2.2.12"

974

id="TOC2.2.12"

975

name="TOC2.2.12">2.2.12: <language>

976

</language></a>

977

978

979

980

<a class="TOC"

981

href="#Section2.2.13"

982

id="TOC2.2.13"

983

name="TOC2.2.13">2.2.13: <relation>

984

</relation></a>

985

986

987

988

<a class="TOC"

989

href="#Section2.2.14"

990

id="TOC2.2.14"

991

name="TOC2.2.14">2.2.14: <coverage>

992

</coverage></a>

993

994

995

996

<a class="TOC"

997

href="#Section2.2.15"

998

id="TOC2.2.15"

999

name="TOC2.2.15">2.2.15: <rights>

1000

</rights></a>

1001

1002

1003

1004

<a class="TOC"

1005

href="#Section2.3"

1006

id="TOC2.3"

1007

name="TOC2.3">2.3: Manifest</a>

1008

1009

1010

1011

<a class="TOC"

1012

href="#Section2.3.1"

1013

id="TOC2.3.1"

1014

name="TOC2.3.1">2.3.1: Fallback Items</a>

1015

1016

1017

1018

<a class="TOC"

1019

href="#Section2.3.1.1"

1020

id="TOC2.3.1.1"

1021

name="TOC2.3.1.1">2.3.1.1: Items That Are Not OPS Core Media Types</a>

1022

1023

1024

1025

<a class="TOC"

1026

href="#Section2.3.1.2"

1027

id="TOC2.3.1.2"

1028

name="TOC2.3.1.2">2.3.1.2: Items That Are Out-Of-Line XML Islands</a>

1029

1030

1031

1032

<a class="TOC"

1033

href="#Section2.4"

1034

id="TOC2.4"

1035

name="TOC2.4">2.4: Spine</a>

1036

1037

1038

1039

<a class="TOC"

1040

href="#Section2.4.1"

1041

id="TOC2.4.1"

1042

name="TOC2.4.1">2.4.1: Declarative Table of Contents — the NCX</a>

1043

1044

1045

1046

<a class="TOC"

1047

href="#Section2.4.1.1"

1048

id="TOC2.4.1.1"

1049

name="TOC2.4.1.1">2.4.1.1: Introduction</a>

1050

1051

1052

1053

<a class="TOC"

1054

href="#Section2.4.1.2"

1055

id="TOC2.4.1.2"

1056

name="TOC2.4.1.2">2.4.1.2: Key NCX Requirements</a>

1057

1058

1059

1060

<a class="TOC"

1061

href="#Section2.4.2"

1062

id="TOC2.4.2"

1063

name="TOC2.4.2">2.4.2: NCX Exceptions in Usage for Publications</a>

1064

1065

1066

1067

<a class="TOC"

1068

href="#Section2.4.3"

1069

id="TOC2.4.3"

1070

name="TOC2.4.3">2.4.3: XML Islands in the Spine</a>

1071

1072

1073

1074

<a class="TOC"

1075

href="#Section2.5"

1076

id="TOC2.5"

1077

name="TOC2.5">2.5: Tours [Deprecated]</a>

1078

1079

1080

1081

<a class="TOC"

1082

href="#Section2.6"

1083

id="TOC2.6"

1084

name="TOC2.6">2.6: Guide</a>

1085

1086

</div>

1087

1088

1089

1090

<a class="TOC"

1091

href="#AppendixA"

1092

id="AppendixTOCA"

1093

name="AppendixTOCA">Appendix A: The OPF Package Schema</a>

1094

1095

</div>

1096

1097

1098

1099

<a class="TOC"

1100

href="#AppendixB"

1101

id="AppendixTOCB"

1102

name="AppendixTOCB">Appendix B: Contributors</a>

1103

1104

</div>

1105

1106

1107

1108

<a class="TOC"

1109

href="#AppendixC"

1110

id="AppendixTOCC"

1111

name="AppendixTOCC">Appendix C: Acknowledgements</a>

1112

1113

</div>

1114

1115

1116

1117

<a class="TOC"

1118

href="#AppendixD"

1119

id="AppendixTOCD"

1120

name="AppendixTOCD"><ins>Appendix D: Supporting Information & Errata</ins></a>

1121

1122

</div>

1123

</div>

1124

1125

1126

1127

1128

<a class="SectionTitle"

1129

href="#TOC1.0"

1130

id="Section1.0"

1131

name="Section1.0">1.0: Overview</a>

1132

</h1>

1133

1134

1135

1136

<a class="SectionTitle"

1137

href="#TOC1.1"

1138

id="Section1.1"

1139

name="Section1.1">1.1: Purpose and Scope</a>

1140

</h2>

1141

1142

1143

In order for electronic-book technology to achieve widespread success in the

1144

marketplace, Reading Systems need to have convenient access to a large number and

1145

variety of titles. <del>The</del> <ins>Another related specification, the</ins> Open

1146

Publication Structure (OPS) Specification<ins>,</ins> describes a standard for

1147

representing the content of electronic publications and is meant to reduce barriers to

1148

the proliferation of content. Specifically, the specification is intended to:

1149

1150

1151

<ul>

1152

<li>Give publication tool providers and content providers (e.g. publishers, authors,

1153

and others who have content to be displayed) minimal and common guidelines that ensure

1154

fidelity, accuracy, accessibility, and adequate presentation of electronic content over

1155

various Reading Systems; and

1156

</li>

1157

1158

<li>Build on established content format standards; and

1159

</li>

1160

1161

<li>Define a standard means of content description in order for electronic books to

1162

move smoothly through the distribution chain.

1163

</li>

1164

</ul>

1165

1166

1167

This document, the Open Packaging Format (OPF) Specification, defines the mechanism by

1168

which the various components of an OPS publication are tied together and provides

1169

additional structure and semantics to the electronic publication. Specifically, OPF:

1170

1171

1172

<ul>

1173

<li>Describes and references all components of the electronic publication (e.g. markup

1174

files, images, navigation structures).

1175

</li>

1176

1177

<li>Provides publication-level metadata.

1178

</li>

1179

1180

<li>Specifies the linear reading-order of the publication.

1181

</li>

1182

1183

<li>Provides fallback information to use when unsupported extensions to OPS are

1184

employed.

1185

</li>

1186

1187

<li>Provides a mechanism to specify a declarative table of contents (the NCX).

1188

</li>

1189

</ul>

1190

1191

1192

This OPF specification is separate from the OPS markup specification to modularize the

1193

described packaging methodology and the described content. This will help facilitate

1194

the use of this packaging technology by other standards bodies (e.g.

1195

<del>Daisy</del><ins>DAISY</ins>) in non-OPS contexts.

1196

1197

1198

1199

A third specification, the OEBPS Container Format (OCF) Specification, defines the

1200

standard mechanism by which all components of an electronic publication can be packaged

1201

together into a single file for transmission, delivery and archival.

1202

1203

</div>

1204

1205

1206

1207

<a class="SectionTitle"

1208

href="#TOC1.2"

1209

id="Section1.2"

1210

name="Section1.2">1.2: Definitions</a>

1211

</h2>

1212

1213

1214

1215

Content Provider

1216

1217

1218

1219

A publisher, author, or other information provider who provides a publication to one

1220

or more Reading Systems in the form described in this specification and the OPS

1221

specification.

1222

1223

1224

1225

Deprecated

1226

1227

1228

1229

A feature that is permitted, but not recommended, by this

1230

specification. Such features might be removed in future revisions. Conformant Reading

1231

Systems must support deprecated features.

1232

1233

1234

1235

Extended Module

1236

1237

1238

1239

A module of a modularized XML vocabulary (i.e. a set of named modules is defined in

1240

its specification) that is not mandated to be supported by its specification (e.g.

1241

the XHTML ruby or forms modules in the OPS context).

1242

1243

1244

1245

Inline XML Island

1246

1247

1248

1249

An inline XML Island is an XML document fragment using a non-Preferred Vocabulary or

1250

using an Extended Module that exists within an XHTML Preferred Vocabulary document

1251

within an OPS Publication.

1252

1253

1254

1255

NCX

1256

1257

1258

1259

A declarative table of contents (the Navigation Center eXtended or NCX).

1260

1261

1262

1263

OCF

1264

1265

1266

1267

The OEBPS Container Format defines a mechanism by which all components of an OPS

1268

Publication can be combined into a single file-system entity.

1269

1270

1271

1272

OEBPS

1273

1274

1275

1276

The Open <del>Publication</del> Publication Structure. Previous versions of this specification

1277

(OPF) and its related specification, OPS, were unified into the single OEBPS

1278

specification. For this version, OEBPS was broken into separate OPF and OPS

1279

specifications to aid modular adoption of the specifications. OEBPS 1.2 was the

1280

highest version of the previous unified specification.

1281

1282

1283

1284

OPF

1285

1286

1287

1288

The Open Packaging Format — this standard — defines the mechanism by which all

1289

components of a published work conforming to the OPS standard including metadata,

1290

reading order and navigational information are packaged into an OPS Publication.

1291

1292

1293

1294

OPF Package Document

1295

1296

1297

1298

An XML Document that describes an OPS Publication and references all files used by

1299

the OPS Publication that are not part of the OPF Package Document itself. It

1300

identifies all other files in the Publication and provides descriptive information

1301

about them. The OPF Package Document is defined by this specification and is valid to

1302

the OPF Package Schema defined herein.

1303

1304

1305

1306

The "root file" of the OPF Package Document should use the

1307

.opf extension. This XML file may

1308

refer to other XML files via XML’s general entity mechanism, but those files

1309

must not use the .opf file

1310

extension. This construction could be used to simplify the creation of OPF Package

1311

Documents for very large Publications. However, the most common case is for the OPF

1312

Package Document to be a single XML file using the .opf

1313

extension.

1314

1315

1316

1317

OPS

1318

1319

1320

1321

The Open Publication Structure — the sister-standard to this standard — defines the

1322

markup necessary to construct OPS Content Documents.

1323

1324

1325

1326

OPS Content Document

1327

1328

1329

1330

An XHTML, DTBook, or out-of-line XML document that conforms to the OPS specification

1331

that can legally appear in the OPF Package Document <span class=

1332

"Element">spine.

1333

1334

1335

1336

OPS Core Media Type

1337

1338

1339

1340

A MIME media type, defined in the OPS Specification, that all Reading Systems

1341

must support.

1342

1343

1344

1345

OPS Publication

1346

1347

1348

1349

A collection of OPS Content Documents, an OPF Package Document, and other files,

1350

typically in a variety of media types, including structured text and graphics, that

1351

constitute a cohesive unit for publication.

1352

1353

1354

1355

Out-of-Line XML Island

1356

1357

1358

1359

An Out-Of-Line XML Island is an XML document that exists within an OPS Publication

1360

and is either not authored using a Preferred Vocabulary or is authored using a

1361

Preferred Vocabulary but uses Extended Modules. It is an entirely separate, complete,

1362

and valid XML document.

1363

1364

1365

1366

Preferred Vocabulary

1367

1368

1369

1370

XML consisting only of OPS-supported XHTML markup and/or DTBook markup.

1371

1372

1373

1374

Reader

1375

1376

1377

1378

A person who reads a publication.

1379

1380

1381

1382

Reading System

1383

1384

1385

1386

A combination of hardware and/or software that accepts OPS Publications (likely

1387

packaged in an OCF Container) and makes them available to consumers of the content.

1388

Great variety is possible in the architecture of Reading Systems. A Reading System

1389

may be implemented entirely on one device, or it

1390

may be split among several computers. In particular, a

1391

Reading Device that is a component of a Reading System need

1392

not directly accept OPS Publications, but all Reading Systems <span class=

1393

"RFC">must do so. Reading Systems may include

1394

additional processing functions, such as compression, indexing, encryption, rights

1395

management, and distribution.

1396

1397

1398

1399

XML Document

1400

1401

1402

1403

An XML Document is a complete and valid XML document as defined in XML 1.1 (<a href=

1404

"http://www.w3.org/TR/xml11/"

1405

target="_blank"

1406

title="The XML 1.1 specification.">http://www.w3.org/TR/xml11/</a>).

1407

1408

1409

1410

XML Document Fragment

1411

1412

1413

1414

Referred to as either a document fragment or as an XML Document Fragment, as defined

1415

in Document Object Model Level 1 (<a href="http://www.w3.org/TR/REC-DOM-Level-1/"

1416

target="_blank"

1417

title="DOM Level 1 specification.">http://www.w3.org/TR/REC-DOM-Level-1/</a>) but

1418

with the additional requirement that they be well-formed.

1419

1420

1421

1422

XML Island

1423

1424

1425

1426

An Inline XML Island or an Out-of-Line XML island.

1427

1428

1429

1430

XML Namespaces

1431

1432

1433

1434

Referred to as XML namespaces, or just namespaces, these must conform to XML

1435

Namespaces (<a href="http://www.w3.org/TR/xml-names11/"

1436

target="_blank"

1437

title="XML Namespaces specification.">http://www.w3.org/TR/xml-names11/</a>).

1438

1439

</div>

1440

</div>

1441

1442

1443

1444

<a class="SectionTitle"

1445

href="#TOC1.3"

1446

id="Section1.3"

1447

name="Section1.3">1.3: Relationship to Other Specifications</a>

1448

</h2>

1449

1450

1451

This specification combines subsets and applications of other specifications. Together,

1452

these facilitate the construction, organization, presentation, and unambiguous

1453

interchange of electronic documents:

1454

1455

1456

<ol>

1457

<li>

1458

Extensible Markup Language (XML) 1.1 (Second Edition)

1459

specification (<a href="http://www.w3.org/TR/xml11/"

1460

target="_blank"

1461

title="The XML 1.1 specification.">http://www.w3.org/TR/xml11/</a>); and

1462

</li>

1463

1464

<li>

1465

Namespaces in XML 1.0 (Second Edition) (<a href=

1466

"http://www.w3.org/TR/xml-names11/"

1467

target="_blank"

1468

title="The XML Namespaces specification.">http://www.w3.org/TR/xml-names11/</a>);

1469

and

1470

</li>

1471

1472

<li>The OPS Specification (<a href="http://www.idpf.org/ops/ops2.0/download/"

1473

target="_blank"

1474

title=

1475

"The Open Publication Structure specification.">http://www.idpf.org/ops/ops2.0/download/</a>);

1476

and

1477

</li>

1478

1479

<li>

1480

XHTML™ 1.1 - Module-based XHTML - Second Edition

1481

specification (<a href="http://www.w3.org/TR/xhtml11/"

1482

target="_blank"

1483

title="The XHTML 1.1 specification.">http://www.w3.org/TR/xhtml11/</a>); and

1484

</li>

1485

1486

<li>

1487

Specifications for the Digital Talking Book (DTB)

1488

(<a href="http://www.niso.org/standards/resources/Z39-86-2005.html"

1489

target="_blank"

1490

title=

1491

"The DTB specification.">http://www.niso.org/standards/resources/Z39-86-2005.html</a>);

1492

and

1493

</li>

1494

1495

<li>

1496

Dublin Core Metadata Element Set, Version 1.1

1497

specification (<a href="http://dublincore.org/documents/2004/12/20/dces/"

1498

target="_blank"

1499

title=

1500

"The Dublin Core Metadata Element Set specification.">http://dublincore.org/documents/2004/12/20/dces/</a>)

1501

and the MARC relator code list (<a href="http://www.loc.gov/marc/relators/"

1502

target="_blank"

1503

title="MARC Relator codes.">http://www.loc.gov/marc/relators/</a>); and

1504

</li>

1505

1506

<li>

1507

Unicode Standard, Version 4.0. Reading, Mass.:

1508

Addison-Wesley, 2003, as updated from time to time by the publication of new

1509

versions. (See <a href="http://www.unicode.org/unicode/standard/versions/"

1510

target="_blank"

1511

title=

1512

"The Unicode Standard.">http://www.unicode.org/unicode/standard/versions</a> for

1513

the latest version and additional information on versions of the standard and of

1514

the Unicode Character Database); and

1515

</li>

1516

1517

<li>Particular MIME media types (<a href="http://www.ietf.org/rfc/rfc4288.txt"

1518

target="_blank"

1519

title=

1520

"Media Type Specifications and Registration Procedures RFC.">http://www.ietf.org/rfc/rfc4288.txt</a>

1521

and <a href="http://www.iana.org/assignments/media-types/index.html"

1522

target="_blank"

1523

title=

1524

"IANA MIME media types document.">http://www.iana.org/assignments/media-types/index.html</a>);

1525

and

1526

</li>

1527

1528

<li>

1529

Web Content Accessibility Guidelines 1.0 (<a href=

1530

"http://www.w3.org/TR/WCAG10/"

1531

target="_blank"

1532

title="WAI Guidelines.">http://www.w3.org/TR/WCAG10/</a>); and

1533

</li>

1534

1535

<li>

1536

RFC 2119: Key words for use in RFCs to Indicate Requirement

1537

Levels. (<a href="http://www.ietf.org/rfc/rfc2119.txt"

1538

target="_blank"

1539

title="RFC 2119">http://www.ietf.org/rfc/rfc2119.txt</a>).

1540

</li>

1541

</ol>

1542

1543

1544

1545

<a class="SectionTitle"

1546

href="#TOC1.3.1"

1547

id="Section1.3.1"

1548

name="Section1.3.1">1.3.1: Relationship to XML</a>

1549

</h3>

1550

1551

1552

<del>OPS</del><ins>OPF</ins> is based on XML because of XML’s generality and

1553

simplicity, and because XML documents are likely to adapt well to future technologies

1554

and uses. XML also provides well-defined rules for the syntax of documents, which

1555

decreases the cost to implementers and reduces incompatibility across systems.

1556

Further, XML is extensible: it is not tied to any particular type of document or set

1557

of element types, it supports internationalization, and it encourages document markup

1558

that can represent a document’s internal parts more directly, making them amenable to

1559

automated formatting and other types of computer processing.

1560

1561

1562

<ul>

1563

<li>Reading Systems must be XML processors as defined in XML

1564

1.1. All OPF Package Documents must be valid XML documents

1565

according to the OPF Package Schema.

1566

</li>

1567

</ul>

1568

</div>

1569

1570

1571

1572

<a class="SectionTitle"

1573

href="#TOC1.3.2"

1574

id="Section1.3.2"

1575

name="Section1.3.2">1.3.2: Relationship to XML Namespaces</a>

1576

</h3>

1577

1578

1579

Reading Systems must process XML namespaces according to the

1580

XML Namespaces Recommendation at <a href="http://www.w3.org/TR/xml-names11/"

1581

target="_blank"

1582

title="The XML Namespaces specification.">http://www.w3.org/TR/xml-names11/</a>.

1583

1584

1585

1586

Namespace prefixes distinguish identical names that are drawn from different XML

1587

vocabularies. An XML namespace declaration in an XML document associates a namespace

1588

prefix with a unique URI. The prefix can then be employed on element or attribute

1589

names in the document. Alternatively, a namespace declaration in an XML document

1590

may identify a URI as the default namespace, applicable to

1591

elements lacking a namespace prefix. The XML namespace prefix is separated from the

1592

suffix element or attribute name by a colon.

1593

1594

1595

1596

The namespace for the OPF Package Document is <span class=

1597

"Namespace">http://www.idpf.org/2007/opf, and must be

1598

declared at the root of all OPF Package Documents. In addition, to be processed as an

1599

OPF 2.0 package, a version attribute with a value of

1600

2.0 must be specified on

1601

<del>all</del><ins>the</ins> package

1602

element<del>s</del>. A package element that omits the

1603

version attribute must be

1604

processed as an OEBPS 1.2 package.

1605

1606

1607

1608

Example:

1609

1610

1611

1612

1613

...

1614

</package>

1615

</pre>

1616

</div>

1617

1618

1619

1620

<a class="SectionTitle"

1621

href="#TOC1.3.3"

1622

id="Section1.3.3"

1623

name="Section1.3.3">1.3.3: Relationship to Dublin Core</a>

1624

</h3>

1625

1626

1627

<del>The</del> Dublin Core <ins>metadata</ins> is designed to minimize the cataloging

1628

burden on authors and publishers, while providing enough metadata to be useful. This

1629

specification supports the set of Dublin Core 1.1 metadata elements (<a href=

1630

"http://dublincore.org/documents/2004/12/20/dces/"

1631

target="_blank"

1632

title=

1633

"Dublin Core metadata elements specification.">http://dublincore.org/documents/2004/12/20/dces/</a>),

1634

supplemented with a small set of additional attributes addressing areas where more

1635

specific information <del>could be</del><ins>is</ins> useful. For example, the OPF

1636

role attribute added to the Dublin Core

1637

<ins>creator and</ins> <span class=

1638

"Element">contributor element<ins>s</ins> allows for much more detailed

1639

specification of contributors to a publication, including their roles expressed

1640

via relator codes.

1641

1642

1643

1644

Content providers must include a minimum set of metadata

1645

elements, defined in <a href="#Section2.2"

1646

title="Publication Metadata">Section 2.2</a>, and should

1647

incorporate additional metadata to enable readers to discover publications of

1648

interest.

1649

1650

</div>

1651

1652

1653

1654

<a class="SectionTitle"

1655

href="#TOC1.3.4"

1656

id="Section1.3.4"

1657

name="Section1.3.4">1.3.4: Relationship to Unicode</a>

1658

</h3>

1659

1660

1661

OPF Package Documents may use the entire Unicode character

1662

set, in UTF-8 or UTF-16 encodings, as defined by Unicode (see <a href=

1663

"http://www.unicode.org/unicode/standard/versions"

1664

target="_blank"

1665

title=

1666

"The Unicode Standard.">http://www.unicode.org/unicode/standard/versions</a>). The

1667

use of Unicode facilitates internationalization and multilingual documents.

1668

However, Reading Systems are not required to provide

1669

glyphs for all Unicode characters.

1670

1671

1672

1673

Reading Systems must parse all UTF-8 and UTF-16 characters

1674

properly (as required by XML). Reading Systems may decline

1675

to display some characters, but must be capable of signaling

1676

in some fashion that undisplayable characters are present. Reading Systems

1677

must not display Unicode characters merely as if they were

1678

8-bit characters. For example, the biohazard symbol (0x2623) need

1679

not be supported by including the correct glyph, but must

1680

not be parsed or displayed as if its component bytes were the two characters

1681

"&#" (0x0026 0x0023).

1682

1683

1684

1685

To aid Reading Systems in implementing consistent searching and sorting behavior it

1686

is required that Unicode Normalization Form C (NFC) be used

1687

(See <a href="http://www.w3.org/TR/charmod-norm/"

1688

target="_blank"

1689

title="Unicode Normalization Form C.">http://www.w3.org/TR/charmod-norm/</a>).

1690

1691

</div>

1692

</div>

1693

1694

1695

1696

<a class="SectionTitle"

1697

href="#TOC1.4"

1698

id="Section1.4"

1699

name="Section1.4">1.4: Conformance</a>

1700

</h2>

1701

1702

1703

The keywords "must", "must not",

1704

"required", "shall", "<span class=

1705

"RFC">shall not", "should", "<span class=

1706

"RFC">recommended", "may", and "<span class=

1707

"RFC">optional" in this document must be interpreted as

1708

described in <a href="http://www.ietf.org/rfc/rfc2119.txt"

1709

target="_blank"

1710

title="RFC 2119.">RFC 2119</a>.

1711

1712

1713

1714

This section defines conformance for OPF Package Documents, and Reading Systems that

1715

process those Documents.

1716

1717

1718

1719

1720

<a class="SectionTitle"

1721

href="#TOC1.4.1"

1722

id="Section1.4.1"

1723

name="Section1.4.1">1.4.1: Package Conformance</a>

1724

</h3>

1725

1726

1727

This specification defines conformance for both individual OPF Package Documents and

1728

for a collection of files including exactly one OPF Package Document that

1729

collectively are referred to as an OPS Publication.

1730

1731

1732

1733

1734

<a class="SectionTitle"

1735

href="#TOC1.4.1.1"

1736

id="Section1.4.1.1"

1737

name="Section1.4.1.1">1.4.1.1: Package Conformance</a>

1738

</h4>

1739

1740

1741

Each conformant OPF Package Document must meet these

1742

necessary conditions:

1743

1744

1745

1746

<li>it is a well-formed XML document (as defined in XML 1.1); and

1747

</li>

1748

1749

<li>it is encoded in UTF-8 or UTF-16; and

1750

</li>

1751

1752

<li>it is a valid XML document according to the OPF Package Schema defined in

1753

<a href="#AppendixA"

1754

title="The OPF Package Schema.">Appendix A</a>; and

1755

</li>

1756

1757

<li>it may consist of one or more XML files, but only one

1758

may use the file extension .opf.

1759

</li>

1760

</ol>

1761

</div>

1762

1763

1764

1765

<a class="SectionTitle"

1766

href="#TOC1.4.1.2"

1767

id="Section1.4.1.2"

1768

name="Section1.4.1.2">1.4.1.2: Publication Conformance</a>

1769

</h4>

1770

1771

1772

A collection of files is a conforming OPS Publication if <del>and only if</del>:

1773

1774

1775

1776

<li>it includes a single OPF Package Document that obeys the Package Conformance

1777

Requirements listed above; and

1778

</li>

1779

1780

<li>

1781

<ins>only one file in the Publication may use the file

1782

extension .opf. If such a file is present, it

1783

must be the "root file" of the OPF Package Document;

1784

and</ins>

1785

</li>

1786

1787

<li>the OPF Package Document includes one and only one manifest entry corresponding

1788

to each other file in the OPS Publication excluding the file or files that make up

1789

the OPF Package Document itself; and

1790

</li>

1791

1792

<li>the manifest entry for each file in the publication specifies a MIME media type

1793

for the file (see <a href="http://www.ietf.org/rfc/rfc2046.txt"

1794

target="_blank"

1795

title="MIME Part 2: Media Types.">http://www.ietf.org/rfc/rfc2046.txt</a>);

1796

and

1797

</li>

1798

1799

<li>each file whose manifest entry identifies it as being in one of the OPS Core

1800

Media Types conforms as defined for those MIME media types; and

1801

</li>

1802

1803

<li>each file listed in the spine of the OPF Package Document <span class=

1804

"RFC">must conform to the OPS Content Document requirements defined in the

1805

OPS specification; and

1806

</li>

1807

1808

<li>

1809

<del>if the publication contains one or more documents which are either DTBook or

1810

an Out-Of-Line XML Island,</del> an NCX must be

1811

included; and

1812

</li>

1813

1814

<li>the metadata element or deprecated <span class=

1815

"Element">dc-metadata element contains at least one <span class=

1816

"Element">identifier element, at least one <span class=

1817

"Element">title element, and at least one <span class=

1818

"Element">language element drawn from the Dublin Core tag set; and

1819

</li>

1820

1821

<li>the unique-identifier attribute of the

1822

package element is a correct XML <span class=

1823

"Element">IDREF to a Dublin Core identifier

1824

element; and

1825

</li>

1826

1827

<li>any extended values specified for the Dublin Core <span class=

1828

"Element">creator and contributor elements' OPF

1829

role attribute must be

1830

taken from the registered MARC Relator Code list or must

1831

begin with oth.; and

1832

</li>

1833

1834

<li>any extended values specified for the guide

1835

element's type attribute begin with <span class=

1836

"AttributeValue">other.; and

1837

</li>

1838

1839

<li>the version attribute of the <span class=

1840

"Element">package element is specified with a value of <span class=

1841

"AttributeValue">2.0; and

1842

</li>

1843

1844

<li>the package element's namespace must be

1845

http://www.idpf.org/2007/opf.

1846

</li>

1847

</ol>

1848

1849

1850

<ins>This specification and the OPS specification impose additional conformance

1851

constraints on the Package Document and on OPS Content Documents.</ins>

1852

1853

</div>

1854

</div>

1855

1856

1857

1858

<a class="SectionTitle"

1859

href="#TOC1.4.2"

1860

id="Section1.4.2"

1861

name="Section1.4.2">1.4.2: Reading System Conformance</a>

1862

</h3>

1863

1864

1865

This specification defines conformance for a Reading System when presented with an

1866

OPS Publication. OPS Content documents have further conformance requirements that can

1867

be found in the OPS specification. A Reading System is conformant if and only if it

1868

processes documents as follows:

1869

1870

1871

1872

<li>When presented with an OPF Package Document the Reading System

1873

must

1874

1875

<li>process all elements and attributes as described in <a href="#Section2"

1876

title="The OPF Package Document.">Section 2</a> of this specification; and

1877

</li>

1878

1879

<li>ignore all elements and attributes not described in <a href="#Section2"

1880

title="The OPF Package Document.">Section 2</a> of this specification; and

1881

</li>

1882

1883

<li>verify the existence of the appropriate namespace specifications, as defined

1884

in the <a href="#Section1.3.2"

1885

title="Relationship to XML Namespaces">Relationship to XML Namespaces</a>

1886

section above.

1887

</li>

1888

</ol>

1889

</li>

1890

1891

<li>When providing navigation via the OPF spine, the Reading System <span class=

1892

"RFC">must not render content that is not an OPS Content Document.

1893

</li>

1894

1895

<li>When presented with an OEBPS 1.2 Package, the Reading System <span class=

1896

"RFC">must process it as a conformant OEBPS 1.2 Reading System would. Note

1897

that only the OEBPS 1.2 Package must be processed as an

1898

OEBPS 1.2 Reading System would, not the content documents referred to in the Package.

1899

</li>

1900

1901

<li>When presented with an OEBPS 1.2 Publication, a Reading System

1902

should process it as a conformant OEBPS 1.2 Reading System would. Such a

1903

Reading System can claim an optional level of Reading System conformance, "Backward

1904

Compatibility Conformance."

1905

</li>

1906

</ol>

1907

</div>

1908

1909

1910

1911

<a class="SectionTitle"

1912

href="#TOC1.4.3"

1913

id="Section1.4.3"

1914

name="Section1.4.3">1.4.3: Compatibility of OPF Version 2.0</a>

1915

</h3>

1916

1917

1918

Version 2.0 of OPF is not meant to be a substantially "new" specification. However,

1919

version 2.0 does add one significant functional enhancement in addition to a number

1920

of other changes from OEBPS version 1.2. Specifically, the following are the most

1921

substantive additions:

1922

1923

1924

<ul>

1925

<li>XML 1.1 is incorporated.

1926

</li>

1927

1928

<li>XML namespace processing <del>in</del><ins>is</ins> now <span class=

1929

"RFC">required.

1930

</li>

1931

1932

<li>Support for <del>Daisy</del><ins>DAISY</ins>’s Navigation Center eXtended (NCX)

1933

has been added to enhance ease of navigation and accessibility of publications.

1934

</li>

1935

1936

<li>

1937

<del>The leading character of</del> Dublin Core element names <span class=

1938

"RFC">must now be lower case to conform to Dublin Core’s XML implementation

1939

recommendations.

1940

</li>

1941

1942

<li>The tours element has been deprecated.

1943

</li>

1944

</ul>

1945

1946

1947

While most changes from version OEBPS 1.2 to OPF 2.0 have been done via deprecation

1948

rather than removal of previous functionality, the OEBPS 1.2 Package is not a fully

1949

compatible subset of OPF 2.0 (e.g. new namespace processing requirements).

1950

1951

</div>

1952

</div>

1953

1954

1955

1956

<del><a class="SectionTitle"

1957

href="#TOC1.5"

1958

id="Section1.5"

1959

name="Section1.5">1.5: Accessibility</a></del>

1960

</h2>

1961

1962

1963

<del>This specification incorporates features that ensure content can be made

1964

accessible to, and usable by, persons with reading disabilities. Existing accessibility

1965

features developed by the World Wide Web Consortium (W3C) are incorporated into this

1966

specification.</del>

1967

1968

1969

1970

<del>Publications should be authored in accordance with the

1971

W3C Web Content Accessibility Guidelines 1.0 (<a href=

1972

"http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/"

1973

target="_blank"

1974

title=

1975

"WAI Web Content Accessibility Guidelines.">http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/</a>)

1976

or, if it is released while the Working Group is active, the Web Content

1977

Accessibility Guidelines 2.0 (the current draft is available at <a href=

1978

"http://www.w3.org/TR/WCAG20/"

1979

target="_blank"

1980

title="Web Content Accessibility Guidelines 2.0.">http://www.w3.org/TR/WCAG20/</a>)

1981

to ensure that the broadest possible set of users will have access to books

1982

delivered in this format.</del>

1983

1984

1985

1986

<del>In addition, recommendations from the W3C HTML 4.0 Guidelines for Mobile Access

1987

(<a href="http://www.w3.org/TR/NOTE-html40-mobile/"

1988

target="_blank"

1989

title="Guidelines for Mobile Access.">http://www.w3.org/TR/NOTE-html40-mobile/</a>)

1990

and the W3C Web Accessibility Initiative's proposed User Agent Guidelines (<a href=

1991

"http://www.w3.org/TR/WD-WAI-USERAGENT/"

1992

target="_blank"

1993

title="WAI User Agent Guidelines.">http://www.w3.org/TR/WD-WAI-USERAGENT/</a>) ought

1994

to be reviewed and applied by OPF implementers to ensure that Reading Systems will

1995

be in conformance with accessibility requirements.</del>

1996

1997

</div>

1998

</div>

1999

2000

2001

2002

<a class="SectionTitle"

2003

href="#TOC2.0"

2004

id="Section2.0"

2005

name="Section2.0">2.0: The OPF Package Document</a>

2006

</h1>

2007

2008

2009

A publication conforming to this specification must include

2010

exactly one XML OPF Package Document, which specifies the OPS Content Documents, images,

2011

and other objects that make up the OPS Publication and how they relate to each other.

2012

2013

2014

2015

The OPF Package Document should be named

2016

<del>using</del><ins>ending in</ins> the extension <ins>"</ins><span class=

2017

"File">.opf<ins>"</ins>, in order to make it readily identifiable within the group

2018

of files making up the publication. The OPS Package Document is of MIME media type

2019

application/oebps-package+xml. This specification does not

2020

define means for physically bundling files together to make one data transfer object

2021

(such as using zip or tar); the OEBPS Container Format (OCF) specifies this

2022

functionality.

2023

2024

2025

2026

This specification neither precludes nor requires the inclusion of the OPF Package Schema

2027

in a Publication.

2028

2029

2030

2031

The major parts of the OPF Package Document are:

2032

2033

2034

2035

2036

Package Name

2037

2038

2039

2040

A unique identifier for the OPS Publication as a whole.

2041

2042

2043

2044

Metadata

2045

2046

2047

2048

Publication metadata (title, author, publisher, etc.).

2049

2050

2051

2052

Manifest

2053

2054

2055

2056

A list of files (documents, images, style sheets, etc.) that make up the publication.

2057

The manifest also includes fallback declarations for files of types not supported by

2058

this specification.

2059

2060

2061

2062

Spine

2063

2064

2065

2066

An arrangement of documents providing a linear reading order.

2067

2068

2069

2070

Tours (Deprecated)

2071

2072

2073

2074

A set of alternate reading sequences through the publication, such as selective views

2075

for various reading purposes, reader expertise levels, etc.

2076

2077

2078

2079

Guide

2080

2081

2082

2083

A set of references to fundamental structural features of the publication, such as

2084

table of contents, foreword, bibliography, etc.

2085

2086

</div>

2087

2088

2089

An OPF Package Document must be a valid XML document conforming

2090

to the OPF Package schema (<a href="#AppendixA"

2091

title="The OPF Package Schema.">Appendix A</a>). An informal outline of the package is

2092

as follows:

2093

2094

2095

2096

<?xml version="1.0"?>

2097

<package version="2.0" xmlns="http://www.idpf.org/2007/opf" <ins>unique-identifier="BookId"</ins>>

2098

metadata

2099

manifest

2100

spine

2101

guide

2102

</package>

2103

</pre>

2104

2105

The following sections describe the parts of the OPF Package Document.

2106

2107

2108

2109

2110

<a class="SectionTitle"

2111

href="#TOC2.1"

2112

id="Section2.1"

2113

name="Section2.1">2.1: Package Identity</a>

2114

</h2>

2115

2116

2117

The package element is the root element in an OPF Package

2118

Document; all other elements are nested within it.

2119

2120

2121

2122

The package <ins>element</ins> <span class=

2123

"RFC">must specify a value for its <span class=

2124

"Attribute">unique-identifier attribute. The <span class=

2125

"Attribute">unique-identifier attribute's value specifies which Dublin Core

2126

identifier element, described in <a href="#Section2.2.10"

2127

target="_blank"

2128

title="<identifier></identifier>">Section 2.2.10</a>, provides the

2129

package's preferred, or primary, identifier. The OPF Package Document's author is

2130

responsible for choosing a primary identifier that is unique to one and only one

2131

particular package (i.e., the set of files referenced from the package document's

2132

manifest).

2133

2134

2135

2136

Notwithstanding the requirement for uniqueness, Reading Systems must

2137

not fail catastrophically if they encounter two distinct packages with the same

2138

purportedly unique primary identifier.

2139

2140

</div>

2141

2142

2143

2144

<a class="SectionTitle"

2145

href="#TOC2.2"

2146

id="Section2.2"

2147

name="Section2.2">2.2: Publication Metadata</a>

2148

</h2>

2149

2150

2151

The required metadata element is

2152

used to provide information about the publication as a whole. It <span class=

2153

"RFC">may contain Dublin Core metadata elements

2154

directly or within a (now deprecated) dc-metadata

2155

sub-element. Supplemental metadata can also be specified directly or within a (now

2156

deprecated) x-metadata sub-element.

2157

2158

2159

2160

Reading Systems must allow the specification of the deprecated

2161

dc-metadata and x-metadata

2162

elements. Newly created OPS 2.0 packages should not create

2163

dc-metadata or x-metadata

2164

elements. If the dc-metadata element is used, all

2165

dc elements must go in

2166

dc-metadata and all other <span class=

2167

"Element">metadata elements, if any, must go into

2168

x-metadata. If the <span class=

2169

"Element">dc-metadata element is not used, all metadata elements <span class=

2170

"RFC">must go directly in the metadata element.

2171

2172

2173

2174

The required metadata or

2175

dc-metadata (deprecated) elements contain specific

2176

publication-level metadata as defined by the Dublin Core Metadata Initiative (<a href=

2177

"http://www.dublincore.org/"

2178

target="_blank"

2179

title="Dublin Core website,">http://www.dublincore.org/</a>). The descriptions below

2180

are included for convenience, and the Dublin Core's own definitions take precedence

2181

(see <a href="http://dublincore.org/documents/2004/12/20/dces/"

2182

target="_blank"

2183

title=

2184

"Dublin Core metadata definitions.">http://dublincore.org/documents/2004/12/20/dces/</a>).

2185

2186

2187

2188

One or more optional instances of a <span class=

2189

"Element">meta element, analogous to the XHTML 1.1 <span class=

2190

"Element">meta element but applicable to the publication as a whole,

2191

may be placed within the metadata

2192

element or within the deprecated x-metadata element. This

2193

allows content providers to express arbitrary metadata beyond the data described by the

2194

Dublin Core specification. Individual OPS Content Documents <span class=

2195

"RFC">may include the meta element directly (as in

2196

XHTML 1.1) for document-specific metadata. This specification uses the OPF Package

2197

Document alone as the basis for expressing publication-level Dublin Core metadata.

2198

2199

2200

2201

For example:

2202

2203

2204

2205

<metadata xmlns:dc="http://purl.org/dc/elements/1.1/"

2206

xmlns:opf="http://www.idpf.org/2007/opf">

2207

<dc:title>Tale of Two Cities</dc:title>

2208

<dc:creator opf:role="aut">Charles Dickens</dc:creator>

2209

...

2210

2211

</metadata>

2212

</pre>

2213

2214

The XML namespace mechanism (see <a href="http://www.w3.org/TR/REC-xml-names11/"

2215

target="_blank"

2216

title="XML Namespaces specification.">http://www.w3.org/TR/REC-xml-names11/</a>) is

2217

used to identify the elements used for Dublin Core metadata without conflict. The

2218

metadata or dc-metadata

2219

(deprecated) elements may contain any number of instances of any Dublin Core

2220

elements. Dublin Core metadata elements may occur in any order; in fact, multiple

2221

instances of the same element type (e.g. multiple Dublin Core <span class=

2222

"Element">creator elements) can be interspersed with other metadata elements

2223

without change of meaning.

2224

2225

2226

2227

Each Dublin Core field is represented by an element whose content is the field's value.

2228

At least one of each of Dublin Core title, <span class=

2229

"Element">identifier and language <span class=

2230

"RFC">must be included in the metadata element.

2231

Dublin Core elements, like any other elements in the OPF Package Document, <span class=

2232

"RFC">may have an id attribute specified. At

2233

least one Dublin Core identifier, which is referenced from

2234

the package unique-identifier attribute, <span class=

2235

"RFC">must have an id specified.

2236

2237

2238

2239

Because the Dublin Core metadata fields for creator and

2240

contributor do not distinguish roles of specific

2241

contributors (such as author, editor, and illustrator), this specification adds an

2242

optional role attribute for this purpose. See <a href=

2243

"#Section2.2.6"

2244

title="Role">Section 2.2.6</a> for a discussion of <span class=

2245

"Attribute">role.

2246

2247

2248

2249

To facilitate machine processing of Dublin Core creator

2250

and contributor fields, this specification adds the

2251

optional file-as attribute for

2252

those elements. This attribute is used to specify a normalized form of the contents.

2253

See <a href="#Section2.2.2"

2254

title="File-As">Section 2.2.2</a> for a discussion of <span class=

2255

"Attribute">file-as.

2256

2257

2258

2259

This specification also adds a scheme attribute to the

2260

Dublin Core identifier element to provide a structural

2261

mechanism to separate an identifier value from the system or authority that generated

2262

or defined that identifier value. See <a href=

2263

"#Section2.2.10"

2264

title="Scheme.">Section 2.2.10</a> for a discussion of <span class=

2265

"Attribute">scheme.

2266

2267

2268

2269

This specification also adds an event attribute to the

2270

Dublin Core date element to enable content providers to

2271

distinguish various publication specific dates (for example, creation, publication,

2272

modification). See <a href="#Section2.2.7"

2273

title="Event.">Section 2.2.7</a> for a discussion of <span class=

2274

"Attribute">event. For example:

2275

2276

2277

2278

<package version="2.0" xmlns="http://www.idpf.o<ins>r</ins>g/2007/opf"

2279

unique-identifier="BookId">

2280

<metadata xmlns:dc="http://purl.org/dc/elements/1.1/"

2281

xmlns:opf="http://www.idpf.org/2007/opf">

2282

<dc:title>Alice in Wonderland</dc:title>

2283

<dc:language>en</dc:language>

2284

<dc:identifier id="BookId" opf:scheme="ISBN">

2285

123456789X

2286

</dc:identifier>

2287

<dc:creator opf:role="aut">Lewis Carroll</dc:creator>

2288

</metadata>

2289

...

2290

</package>

2291

</pre>

2292

2293

There are no attributes for the elements within metadata defined by Dublin Core — only

2294

the elements' contents are so defined. In the above example, the specification of the

2295

OPF namespace on the metadata element is present to

2296

resolve the scheme and <span class=

2297

"Attribute">role attributes used in the identifier

2298

and creator elements, respectively.

2299

2300

2301

2302

<ins>For compatibility with Guidelines for implementing Dublin Core in XML (<a href=

2303

"http://dublincore.org/documents/dc-xml-guidelines/"

2304

target="_blank"

2305

title=

2306

"Guidelines for implementing Dublin Core in XML">http://dublincore.org/documents/dc-xml-guidelines/</a>)

2307

this specification allows xsi:type attribute for metadata items that can be given

2308

using some sort of encoding scheme and xml:lang attribute when an item can be given

2309

using human-readable text. Elements that allow xsi:type attribute are identifier,

2310

language, date, format and type. Elements that allow xml:lang attribute are: title,

2311

contributor, coverage, creator, description, publisher, relation, rights, source,

2312

and subject. This specification does not impose any specific rules for these

2313

attributes (with possible exception of heuristics that use xml:lang described

2314

below).</ins>

2315

2316

2317

2318

The following subsections describe the individual Dublin Core metadata elements.

2319

2320

2321

2322

2323

<a class="SectionTitle"

2324

href="#TOC2.2.1"

2325

id="Section2.2.1"

2326

name="Section2.2.1">2.2.1: <title>

2327

</title></a>

2328

</h3>

2329

2330

2331

The title of the publication. An OPF Package Document must

2332

include at least one instance of this element type, however multiple instances are

2333

permitted. Any Reading System that displays title metadata <span class=

2334

"RFC">should display the content of the most appropriate <span class=

2335

"Element">title element(s). Determination of the most appropriate titles is

2336

not defined by this specification, but may include the

2337

available fonts, an examination of xml:lang

2338

attributes, or other heuristics. In the absence of such an algorithm, conforming

2339

Reading Systems should consider either the first

2340

title element or all the <span class=

2341

"Element">title elements as the most appropriate.

2342

2343

</div>

2344

2345

2346

2347

<a class="SectionTitle"

2348

href="#TOC2.2.2"

2349

id="Section2.2.2"

2350

name="Section2.2.2">2.2.2: <creator>

2351

</creator></a>

2352

</h3>

2353

2354

2355

A primary creator or author of the publication. Additional contributors whose

2356

contributions are secondary to those listed in creator

2357

elements should be named in <span class=

2358

"Element">contributor elements.

2359

2360

2361

2362

Publications with multiple co-authors should provide

2363

multiple creator elements, each containing one author.

2364

The order of creator elements is presumed to define the

2365

order in which the creators' names should be presented by

2366

the Reading System.

2367

2368

2369

2370

This specification recommends that the content of the <span class=

2371

"Element">creator elements hold the text for a single name as it would be

2372

presented to the Reader.

2373

2374

2375

2376

This specification adds to the creator element two

2377

optional attributes: role and

2378

file-as. The set of values for <span class=

2379

"Attribute">role are identical to those defined in <a href="#Section2.2.6"

2380

title="Contributor">Section 2.2.6</a> for the <span class=

2381

"Element">contributor element. The file-as

2382

attribute should be used to specify a normalized form of

2383

the contents, suitable for machine processing. For example, one might find

2384

2385

2386

2387

<dc:creator opf:file-as="King, Martin Luther Jr." opf:role="aut">

2388

Rev. Dr. Martin Luther King Jr.

2389

</dc:creator>

2390

</pre>

2391

2392

Any Reading System that displays creator metadata should

2393

display the content of the most appropriate creator

2394

element(s). Determination of the most appropriate creators is not defined by this

2395

specification, but may include the available fonts, an

2396

examination of xml:lang attributes, or other

2397

heuristics. In the absence of such an algorithm, conforming Reading Systems

2398

should display the contents of all <span class=

2399

"Element">creator elements, in the order provided, with appropriate separating

2400

spacing and/or punctuation.

2401

2402

</div>

2403

2404

2405

2406

<a class="SectionTitle"

2407

href="#TOC2.2.3"

2408

id="Section2.2.3"

2409

name="Section2.2.3">2.2.3: <subject>

2410

</subject></a>

2411

</h3>

2412

2413

2414

Multiple instances of the subject element are supported,

2415

each including an arbitrary phrase or keyword. This specification makes no attempt to

2416

standardize subject naming schemes, such as the Library of Congress Subject Heading

2417

System.

2418

2419

</div>

2420

2421

2422

2423

<a class="SectionTitle"

2424

href="#TOC2.2.4"

2425

id="Section2.2.4"

2426

name="Section2.2.4">2.2.4: <description>

2427

</description></a>

2428

</h3>

2429

2430

2431

Description of the publication's content.

2432

2433

</div>

2434

2435

2436

2437

<a class="SectionTitle"

2438

href="#TOC2.2.5"

2439

id="Section2.2.5"

2440

name="Section2.2.5">2.2.5: <publisher>

2441

</publisher></a>

2442

</h3>

2443

2444

2445

The publisher as defined by the Dublin Core Metadata Element Set (<a href=

2446

"http://dublincore.org/documents/2004/12/20/dces/"

2447

target="_blank"

2448

title=

2449

"Dublin Core Metadata Element Set.">http://dublincore.org/documents/2004/12/20/dces/</a>).

2450

2451

</div>

2452

2453

2454

2455

<a class="SectionTitle"

2456

href="#TOC2.2.6"

2457

id="Section2.2.6"

2458

name="Section2.2.6">2.2.6: <contributor>

2459

</contributor></a>

2460

</h3>

2461

2462

2463

A party whose contribution to the publication is secondary to those named in

2464

creator elements.

2465

2466

2467

2468

Other than significance of contribution, the semantics of this element are identical

2469

to those of creator. Reading Systems are free to choose

2470

to display creator information without accompanying contributor information.

2471

2472

2473

2474

This specification adds to the contributor element two

2475

optional attributes: role and

2476

file-as. The file-as

2477

attribute is defined as for creator, and is documented

2478

in <a href="#Section2.2.2"

2479

title="Creator">Section 2.2.2</a>.

2480

2481

2482

2483

The normative list of values used for the role

2484

attribute is defined by the MARC relator code list (<a href=

2485

"http://www.loc.gov/marc/relators/"

2486

target="_blank"

2487

title="MARC relator code list.">http://www.loc.gov/marc/relators/</a>). When roles

2488

are specified, the 3-character registered MARC values <span class=

2489

"RFC">must be used when applicable. Although that list is extensive, other

2490

values may be added if a desired role is not covered by those predefined values.

2491

Such values must begin with oth., and shall be

2492

considered subdivisions of the other relator

2493

code. Like other constructs in this specification, these values are case-sensitive

2494

and must be coded entirely in lower-case.

2495

2496

2497

2498

For convenience, some relator code values are listed here as examples. Consult the

2499

MARC code list cited above for the complete list.

2500

2501

2502

2503

<tr>

2504

2505

Adapter [adp]

2506

</td>

2507

2508

Use for a person who 1) reworks a musical composition, usually for a different

2509

medium, or 2) rewrites novels or stories for motion pictures or other audiovisual

2510

medium.

2511

</td>

2512

</tr>

2513

2514

<tr>

2515

2516

Annotator [ann]

2517

</td>

2518

2519

Use for a person who writes manuscript annotations on a printed item.

2520

</td>

2521

</tr>

2522

2523

<tr>

2524

2525

Arranger [arr]

2526

</td>

2527

2528

Use for a person who transcribes a musical composition, usually for a different

2529

medium from that of the original; in an arrangement the musical substance remains

2530

essentially unchanged.

2531

</td>

2532

</tr>

2533

2534

<tr>

2535

2536

Artist [art]

2537

</td>

2538

2539

Use for a person (e.g., a painter) who conceives, and perhaps also implements, an

2540

original graphic design or work of art, if specific codes (e.g., [egr], [etr])

2541

are not desired. For book illustrators, prefer Illustrator [ill].

2542

</td>

2543

</tr>

2544

2545

<tr>

2546

2547

Associated name [asn]

2548

</td>

2549

2550

Use as a general relator for a name associated with or found in an item or

2551

collection, or which cannot be determined to be that of a Former owner [fmo] or

2552

other designated relator indicative of provenance.

2553

</td>

2554

</tr>

2555

2556

<tr>

2557

2558

Author [aut]

2559

</td>

2560

2561

Use for a person or corporate body chiefly responsible for the intellectual or

2562

artistic content of a work. This term may also be used when more than one person

2563

or body bears such responsibility.

2564

</td>

2565

</tr>

2566

2567

<tr>

2568

2569

Author in quotations or text extracts [aqt]

2570

</td>

2571

2572

Use for a person whose work is largely quoted or extracted in a works to which he

2573

or she did not contribute directly. Such quotations are found particularly in

2574

exhibition catalogs, collections of photographs, etc.

2575

</td>

2576

</tr>

2577

2578

<tr>

2579

2580

Author of afterword, colophon, etc. [aft]

2581

</td>

2582

2583

Use for a person or corporate body responsible for an afterword, postface,

2584

colophon, etc. but who is not the chief author of a work.

2585

</td>

2586

</tr>

2587

2588

<tr>

2589

2590

Author of introduction, etc. [aui]

2591

</td>

2592

2593

Use for a person or corporate body responsible for an introduction, preface,

2594

foreword, or other critical matter, but who is not the chief author.

2595

</td>

2596

</tr>

2597

2598

<tr>

2599

2600

Bibliographic antecedent [ant]

2601

</td>

2602

2603

Use for the author responsible for a work upon which the work represented by the

2604

catalog record is based. This can be appropriate for adaptations, sequels,

2605

continuations, indexes, etc.

2606

</td>

2607

</tr>

2608

2609

<tr>

2610

2611

Book producer [bkp]

2612

</td>

2613

2614

Use for the person or firm responsible for the production of books and other

2615

print media, if specific codes (e.g., [bkd], [egr], [tyd], [prt]) are not

2616

desired.

2617

</td>

2618

</tr>

2619

2620

<tr>

2621

2622

Collaborator [clb]

2623

</td>

2624

2625

Use for a person or corporate body that takes a limited part in the elaboration

2626

of a work of another author or that brings complements (e.g., appendices, notes)

2627

to the work of another author.

2628

</td>

2629

</tr>

2630

2631

<tr>

2632

2633

Commentator [cmm]

2634

</td>

2635

2636

Use for a person who provides interpretation, analysis, or a discussion of the

2637

subject matter on a recording, motion picture, or other audiovisual medium.

2638

Compiler [com] Use for a person who produces a work or publication by selecting

2639

and putting together material from the works of various persons or bodies.

2640

</td>

2641

</tr>

2642

2643

<tr>

2644

2645

Designer [dsr]

2646

</td>

2647

2648

Use for a person or organization responsible for design if specific codes (e.g.,

2649

[bkd], [tyd]) are not desired.

2650

</td>

2651

</tr>

2652

2653

<tr>

2654

2655

Editor [edt]

2656

</td>

2657

2658

Use for a person who prepares for publication a work not primarily his/her own,

2659

such as by elucidating text, adding introductory or other critical matter, or

2660

technically directing an editorial staff.

2661

</td>

2662

</tr>

2663

2664

<tr>

2665

2666

Illustrator [ill]

2667

</td>

2668

2669

Use for the person who conceives, and perhaps also implements, a design or

2670

illustration, usually to accompany a written text.

2671

</td>

2672

</tr>

2673

2674

<tr>

2675

2676

Lyricist [lyr]

2677

</td>

2678

2679

Use for the writer of the text of a song.

2680

</td>

2681

</tr>

2682

2683

<tr>

2684

2685

Metadata contact [mdc]

2686

</td>

2687

2688

Use for the person or organization primarily responsible for compiling and

2689

maintaining the original description of a metadata set (e.g., geospatial metadata

2690

set).

2691

</td>

2692

</tr>

2693

2694

<tr>

2695

2696

Musician [mus]

2697

</td>

2698

2699

Use for the person who performs music or contributes to the musical content of a

2700

work when it is not possible or desirable to identify the function more

2701

precisely.

2702

</td>

2703

</tr>

2704

2705

<tr>

2706

2707

Narrator [nrt]

2708

</td>

2709

2710

Use for the speaker who relates the particulars of an act, occurrence, or course

2711

of events.

2712

</td>

2713

</tr>

2714

2715

<tr>

2716

2717

Other [oth]

2718

</td>

2719

2720

Use for relator codes from other lists which have no equivalent in the MARC list

2721

or for terms which have not been assigned a code.

2722

</td>

2723

</tr>

2724

2725

<tr>

2726

2727

Photographer [pht]

2728

</td>

2729

2730

Use for the person or organization responsible for taking photographs, whether

2731

they are used in their original form or as reproductions.

2732

</td>

2733

</tr>

2734

2735

<tr>

2736

2737

Printer [prt]

2738

</td>

2739

2740

Use for the person or organization who prints texts, whether from type or plates.

2741

</td>

2742

</tr>

2743

2744

<tr>

2745

2746

Redactor [red]

2747

</td>

2748

2749

Use for a person who writes or develops the framework for an item without being

2750

intellectually responsible for its content.

2751

</td>

2752

</tr>

2753

2754

<tr>

2755

2756

Reviewer [rev]

2757

</td>

2758

2759

Use for a person or corporate body responsible for the review of book, motion

2760

picture, performance, etc.

2761

</td>

2762

</tr>

2763

2764

<tr>

2765

2766

Sponsor [spn]

2767

</td>

2768

2769

Use for the person or agency that issued a contract, or under whose auspices a

2770

work has been written, printed, published, etc.

2771

</td>

2772

</tr>

2773

2774

<tr>

2775

2776

Thesis advisor [ths]

2777

</td>

2778

2779

Use for the person under whose supervision a degree candidate develops and

2780

presents a thesis, memoir, or text of a dissertation.

2781

</td>

2782

</tr>

2783

2784

<tr>

2785

2786

Transcriber [trc]

2787

</td>

2788

2789

Use for a person who prepares a handwritten or typewritten copy from original

2790

material, including from dictated or orally recorded material.

2791

</td>

2792

</tr>

2793

2794

<tr>

2795

2796

Translator [trl]

2797

</td>

2798

2799

Use for a person who renders a text from one language into another, or from an

2800

older form of a language into the modern form.

2801

</td>

2802

</tr>

2803

</table>

2804

</div>

2805

2806

2807

2808

<a class="SectionTitle"

2809

href="#TOC2.2.7"

2810

id="Section2.2.7"

2811

name="Section2.2.7">2.2.7: <date>

2812

</date></a>

2813

</h3>

2814

2815

2816

Date of publication, in the format defined by "Date and Time Formats" at <a href=

2817

"http://www.w3.org/TR/NOTE-datetime"

2818

target="_blank"

2819

title="W3C Note on dates and times.">http://www.w3.org/TR/NOTE-datetime</a> and by

2820

ISO 8601 on which it is based. In particular, dates without times are represented

2821

in the form YYYY[-MM[-DD]]: a required 4-digit year, an

2822

optional 2-digit month, and if the month is given, an

2823

optional 2-digit day of month.

2824

2825

2826

2827

The date element has one <span class=

2828

"RFC">optional OPF event attribute. The set of

2829

values for event are not defined by this specification; possible values <span class=

2830

"RFC">may include: creation, <span class=

2831

"AttributeValue">publication, and <span class=

2832

"AttributeValue">modification.

2833

2834

</div>

2835

2836

2837

2838

<a class="SectionTitle"

2839

href="#TOC2.2.8"

2840

id="Section2.2.8"

2841

name="Section2.2.8">2.2.8: <type>

2842

</type></a>

2843

</h3>

2844

2845

2846

type includes terms describing general categories,

2847

functions, genres, or aggregation levels for content. The advised best practice is to

2848

select a value from a controlled vocabulary.

2849

2850

</div>

2851

2852

2853

2854

<a class="SectionTitle"

2855

href="#TOC2.2.9"

2856

id="Section2.2.9"

2857

name="Section2.2.9">2.2.9: <format>

2858

</format></a>

2859

</h3>

2860

2861

2862

The media type or dimensions of the resource. Best practice is to use a value from a

2863

controlled vocabulary (e.g. MIME media types).

2864

2865

</div>

2866

2867

2868

2869

<a class="SectionTitle"

2870

href="#TOC2.2.10"

2871

id="Section2.2.10"

2872

name="Section2.2.10">2.2.10: <identifier>

2873

</identifier></a>

2874

</h3>

2875

2876

2877

A string or number used to uniquely identify the resource. An OPF Package Document

2878

must include at least one instance of this element type,

2879

however multiple instances are permitted.

2880

2881

2882

2883

At least one identifier must

2884

have an id specified <ins>(the value being of the XML

2885

"ID" data type)</ins>, so it can be referenced from the package <span class=

2886

"Attribute">unique-identifier attribute described in <a href="#Section2.1"

2887

title="Package Identity">Section 2.1</a>.

2888

2889

2890

2891

The identifier element has an <span class=

2892

"RFC">optional OPF scheme attribute defined by

2893

this specification. The scheme attribute names the

2894

system or authority that generated or assigned the text contained within the

2895

identifier element, for example "ISBN" or "DOI." The values of the <span class=

2896

"Attribute">scheme attribute are case sensitive <ins>only when the particular

2897

scheme requires it</ins>.

2898

2899

2900

2901

This specification does not standardize or endorse any particular publication

2902

identifier scheme. Specific uses of URLs or ISBNs are not yet addressed by this

2903

specification. Identifier schemes are not currently defined by Dublin Core.

2904

2905

</div>

2906

2907

2908

2909

<a class="SectionTitle"

2910

href="#TOC2.2.11"

2911

id="Section2.2.11"

2912

name="Section2.2.11">2.2.11: <source>

2913

</source></a>

2914

</h3>

2915

2916

2917

Information regarding a prior resource from which the publication was derived; see

2918

the Dublin Core Metadata Element Set (<a href=

2919

"http://dublincore.org/documents/2004/12/20/dces/"

2920

target="_blank"

2921

title=

2922

"Dublin Core Metadata Element Set">http://dublincore.org/documents/2004/12/20/dces/</a>).

2923

2924

</div>

2925

2926

2927

2928

<a class="SectionTitle"

2929

href="#TOC2.2.12"

2930

id="Section2.2.12"

2931

name="Section2.2.12">2.2.12: <language>

2932

</language></a>

2933

</h3>

2934

2935

2936

Identifies a language of the intellectual content of the Publication. An OPF Package

2937

Document must include at least one instance of this element

2938

type, however multiple instances are permitted. The content of this element

2939

must comply with RFC 3066 (see <a href=

2940

"http://www.ietf.org/rfc/rfc3066.txt"

2941

target="_blank"

2942

title="RFC 3066.">http://www.ietf.org/rfc/rfc3066.txt</a>), or its successor on

2943

the IETF Standards Track. The Dublin Core permits other descriptions as well; this

2944

specification does not.

2945

2946

</div>

2947

2948

2949

2950

<a class="SectionTitle"

2951

href="#TOC2.2.13"

2952

id="Section2.2.13"

2953

name="Section2.2.13">2.2.13: <relation>

2954

</relation></a>

2955

</h3>

2956

2957

2958

An identifier of an auxiliary resource and its relationship to the publication.

2959

2960

</div>

2961

2962

2963

2964

<a class="SectionTitle"

2965

href="#TOC2.2.14"

2966

id="Section2.2.14"

2967

name="Section2.2.14">2.2.14: <coverage>

2968

</coverage></a>

2969

</h3>

2970

2971

2972

The extent or scope of the publication’s content. The advised best practice is to

2973

select a value from a controlled vocabulary; see the Dublin Core Metadata Element Set

2974

(<a href="http://dublincore.org/documents/2004/12/20/dces/"

2975

target="_blank"

2976

title=

2977

"Dublin Core Metadata Element Set">http://dublincore.org/documents/2004/12/20/dces/</a>).

2978

2979

</div>

2980

2981

2982

2983

<a class="SectionTitle"

2984

href="#TOC2.2.15"

2985

id="Section2.2.15"

2986

name="Section2.2.15">2.2.15: <rights>

2987

</rights></a>

2988

</h3>

2989

2990

2991

A statement about rights, or a reference to one. In this specification, the copyright

2992

notice and any further rights description should appear

2993

directly.

2994

2995

2996

2997

This specification does not address the manner in which a Content Provider specifies

2998

to a secure distributor any licensing terms under which readership rights or copies

2999

of the content could be sold.

3000

3001

</div>

3002

</div>

3003

3004

3005

3006

<a class="SectionTitle"

3007

href="#TOC2.3"

3008

id="Section2.3"

3009

name="Section2.3">2.3: Manifest</a>

3010

</h2>

3011

3012

3013

The required manifest

3014

must provide<del>s</del> a list of all the files that are

3015

part<del>s</del> of the publication <ins>(e.g. Content Documents, style sheets, image

3016

files, any embedded font files, any included schemas)</ins>. The <span class=

3017

"Element">manifest element must contain one or more

3018

item elements. Each item

3019

describes a document, an image file, a style sheet, or other component that is

3020

considered part of the publication. The manifest

3021

must not include item elements

3022

referring to the file or files that make up the OPF Package Document.

3023

3024

3025

3026

Each item element contained within a <span class=

3027

"Element">manifest element must have the attributes <span class=

3028

"Attribute">id, href (a URI; if relative, the URI

3029

is interpreted as relative to the OPF Package Document file containing the reference),

3030

and media-type (specifying the item’s MIME media type).

3031

3032

3033

3034

The order of item elements in the manifest is not

3035

significant.

3036

3037

3038

3039

For example:

3040

3041

3042

3043

3044

<item id="intro" href="introduction.html"

3045

media-type="application/xhtml+xml" />

3046

<item id="c1" href="chapter-1.html"

3047

media-type="application/xhtml+xml" />

3048

<item id="c2" href="chapter-2.html"

3049

media-type=application/xhtml+xml" />

3050

<item id="toc" href="contents.xml"

3051

media-type="application/xhtml+xml" />

3052

<item id="oview" href="arch.png"

3053

media-type="image/png" />

3054

</manifest>

3055

</pre>

3056

3057

The URIs in href attributes of <span class=

3058

"Element">item elements in the manifest

3059

must not use fragment identifiers.

3060

3061

3062

3063

<ins>A single resource (href) must

3064

not be listed in the manifest more than once.</ins>

3065

3066

3067

3068

A Content Document’s root element must be consistent with the

3069

media-type of the associated <span class=

3070

"Element">item element within the manifest.

3071

3072

3073

3074

3075

<a class="SectionTitle"

3076

href="#TOC2.3.1"

3077

id="Section2.3.1"

3078

name="Section2.3.1">2.3.1: Fallback Items</a>

3079

</h3>

3080

3081

3082

The OPS specification defines a set of OPS Core Media Types that all conforming

3083

Reading Systems must support (e.g. XHTML, PNG, SVG). For a

3084

publication that uses only those media types, the <span class=

3085

"Element">manifest merely lists the publication's component files directly.

3086

However, content providers may construct publications that

3087

reference items of additional media types. In order for such publications to be read

3088

by all conforming Reading Systems, content providers must

3089

provide alternative "fallback" items for each such item. For every item that is not

3090

an OPS Core Media Type, at least one of its associated fallback items <span class=

3091

"RFC">must either be of a type drawn from the set of OPS Core Media Types or,

3092

in some cases, CSS styling may be provided for documents

3093

containing non-preferred XML vocabularies.

3094

3095

3096

3097

This specification and the OPS specification jointly define four different mechanisms

3098

for specifying OPS Core Media Type fallbacks. These are as follows:

3099

3100

3101

<ol>

3102

<li>For inline "replaced" resources referenced via the <span class=

3103

"Element">object element, this specification relies on that element’s inherent

3104

replacement capabilities, described in <a href=

3105

"http://www.idpf.org/ops/ops2.0/download/OPS2.0.html#Section2.3.6"

3106

target="_blank"

3107

title="object and param Elements">Section 2.3.6</a> of the OPS specification.

3108

</li>

3109

3110

<li>For inline "replaced" resources referenced via the <span class=

3111

"Element">img element, the text value of the <span class=

3112

"Attribute">alt <ins>or title</ins>

3113

attribute<ins>s</ins> provide<del>s</del> a valid fallback, described in <a href=

3114

"http://www.idpf.org/ops/ops2.0/download/OPS2.0.html#Section2.3.4"

3115

target="_blank"

3116

title="img Element">Section 2.3.4</a> of the OPS specification.

3117

</li>

3118

3119

<li>For Inline XML Islands a switch-based fallback mechanism is provided, described

3120

in <a href="http://www.idpf.org/ops/ops2.0/download/OPS2.0.html#Section2.6.3.1"

3121

target="_blank"

3122

title="The switch Element and Contained Elements">Section 2.6.3.1</a> of the

3123

OPS specification.

3124

</li>

3125

3126

<li>For non-inline destinations, whether referenced from a document or a package, and

3127

for inline "replaced" resources referenced via the img

3128

element, the various attributes of the package item

3129

element are used to provide fallback information. This is defined in this section of

3130

this specification.

3131

</li>

3132

</ol>

3133

3134

3135

For the purpose of fallback specification, the file with the media type <span class=

3136

"MIMEType">application/x-dtbncx+xml that specifies the publication’s NCX (see

3137

below) should be considered a Core Media Type, thus fallback

3138

information must not be provided for this file.

3139

3140

3141

3142

3143

<a class="SectionTitle"

3144

href="#TOC2.3.1.1"

3145

id="Section2.3.1.1"

3146

name="Section2.3.1.1">2.3.1.1: Items That Are Not OPS Core Media Types</a>

3147

</h4>

3148

3149

3150

An item that specifies a resource that is not an OPS

3151

Core Media Type <del>and is not an <a href=

3152

"http://www.idpf.org/ops/ops2.0/download/OPS2.0.html#Section2.6.2"

3153

target="_blank"

3154

title="Out-Of-Line XML Islands">Out-Of-Line XML Island</a></del> (e.g. a

3155

non-core image type, a text file, a PDF file) must have

3156

a fallback specified. In this case, its fallback must be identified with a

3157

fallback attribute pointing to another <span class=

3158

"Element">item. <ins>See <a href="#Section2.3.1.2"

3159

title="Out-of-Line XML Islands Fallbacks">Section 2.3.1.2</a> for fallback

3160

requirements for Out-of-Line XML Islands.</ins>

3161

3162

3163

3164

An item identifies a fallback <span class=

3165

"Element">item using its fallback attribute,

3166

which must specify the ID

3167

of the item element that identifies the fallback.

3168

Items referenced from fallback attributes

3169

may each specify a fallback

3170

attribute in turn, forming a multi-level fallback chain. For example:

3171

3172

3173

3174

3175

<item id="item1"

3176

href="FunDoc.txt"

3177

media-type="text/plain"

3178

fallback="fall1" />

3179

<item id="fall1" fallback="fall2"

3180

href="FunDoc.pdf"

3181

media-type="application/pdf" />

3182

<item id="fall2"

3183

href="FunDoc.html"

3184

media-type="application/<ins>x</ins>html+xml" />

3185

3186

</manifest>

3187

</pre>

3188

3189

If a fallback attribute points to an <span class=

3190

"Element">item that also has a fallback

3191

attribute, a Reading System must continue down the

3192

fallback chain until it reaches a reference to an item

3193

with a media type it can display (or as specified below, it reaches an <span class=

3194

"Element">item with a fallback-style

3195

attribute). A Reading System may continue further, and

3196

may display any item from the

3197

chain. In the absence of element-specific (i.e. img

3198

and object) fallback information, every <span class=

3199

"Element">item in a publication that does not have one of the OPS Core Media

3200

Types must, directly or indirectly, specify a fallback to

3201

an item that does have one of the OPS Core Media Types

3202

(or as specified below, an item with a <span class=

3203

"Attribute">fallback-style attribute).

3204

3205

3206

3207

Fallback chains must terminate; circular references are

3208

not permitted. Nevertheless, Reading Systems should not

3209

fail catastrophically if they encounter such a loop.

3210

3211

</div>

3212

3213

3214

3215

<a class="SectionTitle"

3216

href="#TOC2.3.1.2"

3217

id="Section2.3.1.2"

3218

name="Section2.3.1.2">2.3.1.2: Items That Are Out-Of-Line XML Islands</a>

3219

</h4>

3220

3221

3222

An item that specifies a resource that is an

3223

Out-Of-Line XML Island (an XML document that is not authored in a Preferred

3224

Vocabulary). An item is an Out-Of-Line XML Island if:

3225

3226

3227

3228

<li>It specifies a resource that is an XML document not authored in a Preferred

3229

Vocabulary (i.e. an XML document with a media-type

3230

that is neither application/xhtml+xml, <span class=

3231

"MIMEType">application/x-dtbook+xml nor the deprecated <span class=

3232

"MIMEType">text/x-eob1-document); or

3233

</li>

3234

3235

<li>It specifies a resource that is an XML document authored in a Preferred

3236

Vocabulary and incorporates the use of Extended Modules.

3237

</li>

3238

</ol>

3239

3240

3241

More information is needed, and more freedom is provided, for fallback

3242

determination and processing of Out-Of-Line XML Islands. The namespace of an

3243

Out-Of-Line XML Island item <span class=

3244

"RFC">must be specified with the <span class=

3245

"Attribute">required-namespace attribute and its fallback <span class=

3246

"RFC">must be identified with either a <span class=

3247

"Attribute">fallback attribute pointing to another <span class=

3248

"Element">item or by providing CSS styling that can be used to render the

3249

island via the fallback-style attribute.

3250

3251

3252

3253

If the fallback attribute is specified, Reading

3254

System processing is identical to the Non-OPS Core Media Types handling described

3255

above.

3256

3257

3258

3259

If the fallback-style attribute is specified, a

3260

Reading System may choose to process the Out-Of-Line XML

3261

Island (even though it can not natively process the vocabulary or Extended Modules

3262

used in the island) using the stylesheet specified by the <span class=

3263

"Attribute">fallback-style attribute's value which <span class=

3264

"RFC">must contain a reference to the id of

3265

the item containing an <span class=

3266

"Attribute">href to the stylesheet desired for the island.

3267

3268

3269

3270

Both fallback and <span class=

3271

"Attribute">fallback-style attributes may be

3272

specified, in which case the Reading System may choose to

3273

either follow the fallback chain or to process the Out-Of-Line XML Island with the

3274

supplied CSS stylesheet.

3275

3276

3277

3278

An Out-Of-Line XML Island authored in a Preferred Vocabulary by definition

3279

incorporates the use of Extended Modules. In this case, and with non-Preferred

3280

Vocabulary islands utilizing Extended Modules, the <span class=

3281

"Attribute">required-modules attribute must be

3282

present along with the required-namespace attribute.

3283

3284

3285

3286

The attribute value for required-modules

3287

must be a comma-separated list containing the name(s) of

3288

the Extended Modules used in the Out-of-Line XML Island. The names of the modules

3289

are not case-sensitive, unless specifically defined otherwise in the XML vocabulary

3290

specification. Spaces in module names must be replaced

3291

with "-" for listing in the required-modules

3292

attribute value. For XHTML, in the context of OPS, the Extended Modules include

3293

ruby, <span class=

3294

"AttributeValue">forms, <span class=

3295

"AttributeValue">server-side-image-map, and <span class=

3296

"AttributeValue">intrinsic-events.

3297

3298

3299

3300

Note that listing the names of non-Extended Modules in a <span class=

3301

"Attribute">required-modules attribute value is also allowed; such modules

3302

are always considered to be supported if the XML vocabulary is supported. This can

3303

be useful both for clarity and in the case where there is a possibility that some

3304

modules could become optional in the later revisions of

3305

the specification (e.g. the currently deprecated Style Attribute XHTML module in

3306

OPS).

3307

3308

3309

3310

It is allowed, and sometimes useful, to provide a <span class=

3311

"Attribute">required-modules attribute on an item specifying a non-Preferred

3312

Vocabulary Out-Of-Line XML Island — either for clarity or to specify Extended

3313

Modules needed from the non-Preferred Vocabulary.

3314

3315

3316

3317

Most importantly, a Reading System that can natively process the non-Preferred

3318

Vocabulary (or Extended Modules) used for an Out-Of-Line XML Island <span class=

3319

"RFC">may choose to use its integral understanding to natively process the

3320

document. However, fallback information must be provided

3321

for Reading Systems that do not have such native processing ability.

3322

3323

3324

3325

For example:

3326

3327

3328

3329

3330

<item id="item1"

3331

href="Doc1.hpy"

3332

media-type="text/happy+xml"

3333

required-namespace="http://happy.com/ns/happy1/"

3334

fallback="item2" />

3335

<item id="item2"

3336

href="Doc1.less-hpy"

3337

media-type="text/less-happy+xml"

3338

required-namespace="http://happy.com/ns/happy2/"

3339

fallback="item2.5"

3340

fallback-style="css1" />

3341

<item id="item2.5"

3342

href="Doc1.htm"

3343

media-type="application/xhtml+xml"

3344

required-namespace="http://www.w3.org/1999/xhtml"

3345

required-modules="ruby, server-side-image-map"

3346

fallback="item3" />

3347

<item id="item3"

3348

href="Doc1.dtb"

3349

media-type="application/x-dtbook+xml" />

3350

<item id="item4"

3351

href="Doc2.hpy"

3352

media-type="text/happy+xml"

3353

required-namespace="http://happy.com/ns/happy1/"

3354

fallback-style="css1" />

3355

<item id="css1"

3356

href="happy.css"

3357

media-type="text/css" />

3358

</manifest>

3359

</pre>

3360

3361

In the above example when processing item1, a

3362

Reading System could choose to render item1

3363

natively, item2 natively, <span class=

3364

"AttributeValue">item2 with only styling from <span class=

3365

"AttributeValue">css1, item2.5 natively

3366

(assuming the Ruby and Server Side Image Map XHTML Extended Modules are supported

3367

by the Reading System), or item3 natively. When

3368

processing item4, a Reading System could choose

3369

to render item4 natively or <span class=

3370

"AttributeValue">item4 with only styling from <span class=

3371

"AttributeValue">css1.

3372

3373

3374

3375

Inclusion of the required-namespace attribute is

3376

not required in item elements

3377

referring to XML documents authored in Preferred Vocabularies unless Extended

3378

Modules are used, in which case both <span class=

3379

"Attribute">required-namespace and <span class=

3380

"Attribute">required-modules attributes must be

3381

provided.

3382

3383

</div>

3384

</div>

3385

</div>

3386

3387

3388

3389

<a class="SectionTitle"

3390

href="#TOC2.4"

3391

id="Section2.4"

3392

name="Section2.4">2.4: Spine</a>

3393

</h2>

3394

3395

3396

<del>Following the manifest, there <span class=

3397

"RFC">must be one spine element, which defines the

3398

primary linear reading order of the publication. It specifies an ordered list of one or

3399

more OPS Content Documents drawn from the manifest, using

3400

itemref elements contained within the <span class=

3401

"Element">spine element.</del>

3402

3403

3404

3405

<del>A publication must specify exactly one <span class=

3406

"Element">spine. Reading Systems must treat the file

3407

named in the first itemref element within the <span class=

3408

"Element">spine as the first file to be rendered in the reading of the

3409

publication. The successive files named in successive <span class=

3410

"Element">itemref elements are those that are to be rendered using "next-page"

3411

style functionality that could be available in the Reading System.</del>

3412

3413

3414

3415

<del>The spine must refer only to

3416

item elements with media types of <span class=

3417

"MIMEType">application/xhtml+xml, <span class=

3418

"MIMEType">application/x-dtbook+xml, the deprecated <span class=

3419

"MIMEType">text/x-eob1-document, or an Out-Of-Line XML Island (with <span class=

3420

"RFC">required fallback). Content with other

3421

media types may be referenced via OPS Content Documents, which

3422

should provide text alternates and other information to

3423

enhance accessibility as appropriate.</del>

3424

3425

3426

3427

<del>The spine need not include references to every one of

3428

the manifest’s item elements

3429

that reference OPS Content Documents, because there are means other than the

3430

spine for accessing documents in the publication. For

3431

example, hypertext links may provide access to documents not

3432

in the spine, as may tours and

3433

guides (see below).</del>

3434

3435

3436

3437

<del>For example:</del>

3438

3439

3440

3441

<del>

3442

3443

<item id="toc"

3444

href="contents.html"

3445

media-type="application/html+xml" />

3446

<item id="c1"

3447

href="chap1.html"

3448

media-type="application/html+xml" />

3449

<item id="c2"

3450

href="chap2.dtb"

3451

media-type="application/x-dtbook+xml" />

3452

<item id="c3"

3453

href="chap3.html"

3454

media-type="application/html+xml" />

3455

3456

3457

3458

3459

</manifest>

3460

3461

3462

3463

3464

3465

</spine>

3466

</del>

3467

</pre>

3468

3469

<del>In the above example, suppose the document referenced by <span class=

3470

"Attribute">id c1 is being viewed by a

3471

reader. When the end of the document is reached, the next document in linear order

3472

would be the document referenced by id <span class=

3473

"AttributeValue">c2.</del>

3474

3475

3476

3477

<del>The NCX section below specifies the requirements for the navigation control file

3478

and the spine toc

3479

attribute.</del>

3480

3481

3482

3483

<del>Content is considered reachable if it is referenced directly or indirectly through

3484

hyperlinks or navigation structure (NCX). Referencing content through <span class=

3485

"Element">img or object elements does not make an

3486

item reachable. All content reachable in the publication must

3487

be referenced with itemref elements.</del>

3488

3489

3490

3491

<del>Each item must only be

3492

referenced by a single element (itemref). Content

3493

referenced by an itemref element that omits the

3494

optional linear attribute (or

3495

provides the linear attribute with a value of

3496

yes) is called primary content. Content referenced

3497

by an itemref element that includes the optional

3498

linear attribute with a value of <span class=

3499

"AttributeValue">no is referred to as auxiliary content.</del>

3500

3501

3502

3503

<del>Reading Systems must display all primary (and optionally

3504

auxiliary) content items in a way that allows linear (forward and backward) navigation

3505

through all the items in the order in which they are listed in the <span class=

3506

"Element">spine. The decision on whether to include auxiliary content in the

3507

linear navigation order should be based on the Reading System

3508

design and device capabilities. This specification neither encourages nor discourages

3509

such inclusion. Reading Systems must display in some fashion

3510

all auxiliary content items if such items can be reached through hyperlinks, even if

3511

the auxiliary content items are not included in the linear navigation order.</del>

3512

3513

3514

3515

<del>For example:</del>

3516

3517

3518

3519

<del>

3520

3521

3522

3523

3524

3525

3526

3527

3528

</spine>

3529

</del>

3530

</pre>

3531

3532

<del>Note that this design (the addition of the linear

3533

attribute) is backward compatible with OEBPS 1.2, assuming that the OEBPS 1.2 Reading

3534

System ignores unknown attributes.</del>

3535

3536

3537

3538

<ins>Following manifest, there <span class=

3539

"RFC">must be one and only one spine element, which

3540

contains one or more itemref elements. Each <span class=

3541

"Element">itemref references an OPS Content Document designated in the

3542

manifest. The order of the <span class=

3543

"Element">itemref elements organizes the associated OPS Content Documents into

3544

the linear reading order of the publication.</ins>

3545

3546

3547

3548

<ins>Each itemref in spine

3549

must not reference media types other than OPS Content

3550

Documents (or documents whose fallback chain includes an OPS Content Document). An OPS

3551

Content Document must be of one of the following media types:

3552

application/xhtml+xml, <span class=

3553

"MIMEType">application/x-dtbook+xml, the deprecated <span class=

3554

"MIMEType">text/x-oeb1-document, and Out-Of-Line XML Island (with <span class=

3555

"RFC">required fallback.) When a document with a

3556

media type not from this list (or a document whose fallback chain doesn't include a

3557

document with a media type from this list) is referenced in <span class=

3558

"Element">spine, Reading Systems must not include it as

3559

part of the spine.</ins>

3560

3561

3562

3563

<ins>As items appearing in the spine must either be OPS

3564

Content Documents or items with a fallback chain that includes an OPS Content, it is

3565

possible to have a fallback chain for a spine item that

3566

"falls over" another OPS Core Media type. For example, a <span class=

3567

"Element">spine itemref could reference a PDF

3568

document, that falls back to a PNG image, that in turn falls back to a OPS XHTML

3569

Content Document. It is valid for this item to appear in the <span class=

3570

"Element">spine because the fallback chain includes (in this case terminates

3571

with) an OPS Content Document.</ins>

3572

3573

3574

3575

<ins>In addition, a specific spine item (from the

3576

perspective of its id attribute value in <span class=

3577

"Element">manifest) must not appear more than once in <span class=

3578

"Element">spine.</ins>

3579

3580

3581

3582

<ins>All OPS Content Documents that are part of the publication (i.e. are listed in the

3583

manifest) which are potentially reachable by any reference mechanism allowed in this

3584

specification must be included in the <span class=

3585

"Element">spine. Such reference mechanisms include, as a partial list, hypertext

3586

links within OPS Content Documents, and references by the NCX, Tours and Guide.</ins>

3587

3588

3589

3590

<ins>Should a Reading System encounter, by such reference, an OPS Content Document not

3591

listed in spine as required in this specification, the

3592

Reading System should add it to <span class=

3593

"Element">spine (the placement at the discretion of the Reading System) and

3594

assign the value of the linear attribute to <span class=

3595

"AttributeValue">no (see next.)</ins>

3596

3597

3598

3599

<ins>For each itemref, the publication author <span class=

3600

"RFC">may specify the optional linear attribute

3601

to designate whether the associated OPS Content Document is primary (<span class=

3602

"Attribute">linear="yes", which is the default when <span class=

3603

"Attribute">linear is not present) or auxiliary (<span class=

3604

"Attribute">linear="no".) It is important that the publication author include

3605

some kind of internal reference, such as a hypertext link, to any OPS Content Document

3606

that is declared to be auxiliary; it is recommended that

3607

references be added to NCX for all auxiliary content. At least one <span class=

3608

"Element">itemref in spine <span class=

3609

"RFC">must be declared primary.</ins>

3610

3611

3612

3613

<ins>Specifying whether an OPS Content Document is primary or auxiliary is useful for

3614

Reading Systems which opt to present auxiliary content differently than primary

3615

content. For example, a Reading System might opt to render auxiliary content in a popup

3616

window apart from the main window which presents the primary content. (For an example

3617

of the types of content that may be considered auxiliary, refer to the example below

3618

and the subsequent discussion.)</ins>

3619

3620

3621

3622

<ins>Reading Systems are not required to differentiate between

3623

primary and auxiliary content, and for the requirements and recommendations given in

3624

this section may consider all OPS Content Documents in

3625

spine to be primary, regardless of the value of the

3626

linear attribute.</ins>

3627

3628

3629

3630

<ins>The linear attribute also maintains compatibility

3631

with OEBPS 1.x, where not all reachable OEBPS content documents were required to be

3632

listed in the spine. For upgrading an OEBPS Publication to

3633

OPS, every unlisted, reachable content document in the OEBPS 1.x Publication

3634

should be assigned <span class=

3635

"Attribute">linear="no".</ins>

3636

3637

3638

3639

<ins>Reading Systems are to use the ordered itemref

3640

information in spine to present the publication during

3641

reading. Reading Systems must recognize the first primary OPS

3642

Content Document in spine to be the beginning of the main

3643

reading order of the publication. Successive primary OPS Content Documents form the

3644

remainder of the main reading order in the same order given in <span class=

3645

"Element">spine. Reading Systems may use "next-page"

3646

style functionality when moving from one primary OPS Content Document to the next

3647

primary one in spine.</ins>

3648

3649

3650

3651

<ins>The spine element must

3652

include the toc attribute, whose value is the the

3653

id attribute value of the <span class=

3654

"RFC">required NCX document declared in manifest

3655

(see Section 2.4.1.)</ins>

3656

3657

3658

3659

<ins>Example illustrating spine and the optional

3660

linear attribute:</ins>

3661

3662

3663

3664

3665

<item id="intro"

3666

href="intro.html"

3667

media-type="application/xhtml+xml" />

3668

<item id="c1"

3669

href="chap1.html"

3670

media-type="application/xhtml+xml" />

3671

<item id="c1-answerkey"

3672

href="chap1-answerkey.html"

3673

media-type="application/xhtml+xml" />

3674

<item id="c2"

3675

href="chap2.dtb"

3676

media-type="application/x-dtbook+xml" />

3677

<item id="c2-answerkey"

3678

href="chap2-answerkey.html"

3679

media-type="application/xhtml+xml" />

3680

<item id="c3"

3681

href="chap3.html"

3682

media-type="application/xhtml+xml" />

3683

<item id="c3-answerkey"

3684

href="chap3-answerkey.html"

3685

media-type="application/xhtml+xml" />

3686

<item id="note"

3687

href="note.html"

3688

media-type="application/xhtml+xml" />

3689

<item id="f1"

3690

href="fig1.jpg"

3691

media-type="image/jpeg" />

3692

<item id="f2"

3693

href="fig2.jpg"

3694

media-type="image/jpeg" />

3695

<item id="f3"

3696

href="fig3.jpg"

3697

media-type="image/jpeg" />

3698

<item id="ncx"

3699

href="toc.ncx"

3700

media-type="application/x-dtbncx+xml" />

3701

</manifest>

3702

3703

3704

3705

3706

3707

3708

3709

3710

3711

</spine></ins>

3712

</pre>

3713

3714

<ins>In the above example, the publication author set <span class=

3715

"Attribute">linear="no" on four of the eight OPS Content Documents listed in

3716

spine, designating these content documents to be

3717

auxiliary. Three of the four are "answer keys," and the fourth is a note of some sort;

3718

all four are auxiliary to the main flow of the book and may be viewed separately from

3719

the main flow.</ins>

3720

3721

3722

3723

<ins>Reading Systems which recognize and render auxiliary content separate from primary

3724

content will set the main reading order to be the four primary OPS Content Documents:

3725

intro, c1,

3726

c2 and c3. The

3727

auxiliary content documents will be rendered by such Reading Systems, upon activation

3728

(such as through a hypertext link or entry in NCX), in some manner distinct from the

3729

main reading order. It is important that the publication author provide the necessary

3730

references to the auxiliary content documents, otherwise this content might not be

3731

reachable in some auxiliary-aware Reading Systems.</ins>

3732

3733

3734

3735

<ins>Reading Systems which opt to ignore linear="no" and

3736

set all itemref to be primary, as allowed in this

3737

specification, will assign all eight OPS Content Documents to the main reading order in

3738

the order given. This is especially useful for Reading Systems which provide print

3739

output, where it is important that all the information in the OPS Content Documents be

3740

printed in an author-determined linear order.</ins>

3741

3742

3743

3744

<ins>A Reading System may, at its discretion, provide both

3745

rendering options to the user.</ins>

3746

3747

3748

3749

3750

<a class="SectionTitle"

3751

href="#TOC2.4.1"

3752

id="Section2.4.1"

3753

name="Section2.4.1">2.4.1: Declarative Table of Contents — the NCX</a>

3754

</h3>

3755

3756

3757

In order to enable ease of navigation and provide greater accessibility, the OPF

3758

Package Document supports a "Navigation Center eXtended," the NCX. This is a concept

3759

and implementation that has been standardized by the DAISY Consortium.

3760

3761

3762

3763

This specification uses the NCX defined in the DAISY/NISO Standard, formally the

3764

ANSI/NISO Z39.86-2005, Specifications for the Digital

3765

Talking Book. The NCX is a portion (Section 8) of this comprehensive

3766

multimedia standard. The DAISY Consortium maintains the NCX DTD. No modifications to

3767

the DTD are necessary for use with OPF. In the future the DAISY/NISO Advisory

3768

Committee will consider modularizing the NCX and changing terminology to be more in

3769

line with ebooks, multimedia publications and other electronic document usage.

3770

3771

3772

3773

Some optional elements and metadata items are not needed to

3774

implement the NCX for this specification. The sections below have been changed to

3775

normatively reference the DAISY/NISO standard for the NCX rather than duplicating it

3776

here. All "exceptions" are described in <a href="#Section2.4.2"

3777

title="NCX Exceptions in Usage for eBooks">Section 2.4.2</a>, below.

3778

3779

3780

3781

3782

<a class="SectionTitle"

3783

href="#TOC2.4.1.1"

3784

id="Section2.4.1.1"

3785

name="Section2.4.1.1">2.4.1.1: Introduction</a>

3786

</h4>

3787

3788

3789

The Navigation Control file for XML applications (NCX) exposes the hierarchical

3790

structure of a Publication to allow the user to navigate through it. The NCX is

3791

similar to a table of contents in that it enables the reader to jump directly to

3792

any of the major structural elements of the document, i.e. part, chapter, or

3793

section, but it will often contain more elements of the document than the publisher

3794

chooses to include in the original print table of contents. It can be visualized as

3795

a collapsible tree familiar to PC users. Its development was motivated by the need

3796

to provide quick access to the main structural elements of a document without the

3797

need to parse the entire documents. Other elements such as pages, footnotes,

3798

figures, tables, etc. can be included in separate, nonhierarchical lists and can be

3799

accessed by the user as well.

3800

3801

3802

3803

It is important to emphasize that these navigation features are intended as a

3804

convenience for users who want them, and not a burden to those who do not. The

3805

alternative guide to the book may be provided for

3806

those users not requiring the navigation features of the NCX.

3807

3808

</div>

3809

3810

3811

3812

<a class="SectionTitle"

3813

href="#TOC2.4.1.2"

3814

id="Section2.4.1.2"

3815

name="Section2.4.1.2">2.4.1.2: Key NCX Requirements</a>

3816

</h4>

3817

3818

3819

Reading Systems must support NCX.

3820

3821

3822

3823

<del>Publications containing only XHTML OPS Content Documents <span class=

3824

"RFC">should include an NCX (this "should" could

3825

transition to a "must" in future versions of this

3826

specification).</del>

3827

3828

3829

3830

<ins>OPS</ins> Publications <del>containing DTBook or Out-of-Line XML Island OPS

3831

Content Documents</del> must include an NCX.

3832

3833

3834

3835

Like all other Publication components, the NCX must be

3836

included as an item in the <span class=

3837

"Element">manifest (with media-type of

3838

application/x-dtbncx+xml). The NCX-referencing

3839

item must not contain any

3840

fallback information (required-namespace,

3841

fallback or <span class=

3842

"Attribute">fallback-style attributes).

3843

3844

3845

3846

If a Publication includes an NCX, the item that

3847

describes the NCX must be referenced by the <span class=

3848

"Element">spine toc attribute.

3849

3850

3851

3852

The NCX file must be a valid XML document conforming to

3853

<a href="http://www.daisy.org/z3986/2005/ncx-2005-1.dtd"

3854

target="_blank"

3855

title="The NCX Document Type Definition."><span class=

3856

"File">ncx-2005-1.dtd</a> and comply with the additional normative

3857

requirements defined in <a href=

3858

"http://www.niso.org/standards/resources/Z39-86-2005.html"

3859

target="_blank"

3860

title=

3861

"The DTB specification.">http://www.niso.org/standards/resources/Z39-86-2005.html</a>.

3862

The version and <span class=

3863

"Element">xmlns attributes on the ncx

3864

element must be explicitly specified in the document

3865

instance, using values drawn from the above-named DTD.

3866

3867

</div>

3868

</div>

3869

3870

3871

3872

<a class="SectionTitle"

3873

href="#TOC2.4.2"

3874

id="Section2.4.2"

3875

name="Section2.4.2">2.4.2: NCX Exceptions in Usage for Publications</a>

3876

</h3>

3877

3878

3879

The NCX as defined in the ANSI/NISO Z39.86-2005 Standard Section 8 is ideal for OPS

3880

applications, however, some exceptions are noted herein. In the standard, the links

3881

from the NCX to the Publication point to SMIL <ins>(<a href=

3882

"http://www.w3.org/TR/2005/REC-SMIL2-20050107/"

3883

target="_blank"

3884

title=

3885

"The SMIL specification.">http://www.w3.org/TR/2005/REC-SMIL2-20050107/</a>)</ins>

3886

documents. For OPS Publications, the links will point to an XML elements in the

3887

source OPS Content Document. This difference causes the following exceptions to be

3888

noted from Section 8 in that standard:

3889

3890

3891

<ul>

3892

<li>

3893

smilCustomTest is not used in the OPF application of

3894

the NCX;

3895

</li>

3896

3897

<li>

3898

audio is not used in the OPS application of the NCX;

3899

</li>

3900

3901

<li>

3902

clipBegin (<span class=

3903

"Attribute">%SMILtimeVal, REQUIRED): is used

3904

for identifying the start of an audio segment, and hence not used in the OPF

3905

application of the NCX;

3906

</li>

3907

3908

<li>

3909

clipEnd (<span class=

3910

"Attribute">%SMILtimeVal, REQUIRED): is used

3911

for identifying the end of an audio segment, and hence not used in the OPF

3912

application of the NCX;

3913

</li>

3914

3915

<li>

3916

content Description: Pointer into SMIL file to

3917

beginning of the item referenced by the navPoint or

3918

navTarget. Note: In the OPF application of the NCX the

3919

pointer is to an XML element and not a SMIL location.

3920

</li>

3921

3922

<li>DTBs Spanning Multiple Media Units are not relevant in the Publication context

3923

because OPS Publications are significantly smaller than multimedia files.

3924

</li>

3925

3926

<li>Examples show links to SMIL files, but in the OPF application of NCX the links

3927

will be to XML elements. Also, the examples show audio

3928

references with clipBegin and

3929

clipEnd, which are not used in the OPF application of the NCX.

3930

</li>

3931

3932

<li>

3933

<ins>The required NCX metadata items "dtb:totalPageCount" and "dtb:maxPageNumber"

3934

may not be relevant when content is not related to a rendition with "paper pages".

3935

In this case, their values may be specified as zero and

3936

the Reading System may ignore them.</ins>

3937

</li>

3938

3939

<li>

3940

<ins>playOrder attributes remain required. Although

3941

playOrder attributes are not used to sequence SMIL

3942

content, they should contain valid values that reflect the

3943

linear document reading order. This could, for example, be used when one is

3944

navigating a pageList to find a corresponding location

3945

in the navMap.</ins>

3946

</li>

3947

</ul>

3948

</div>

3949

3950

3951

3952

<a class="SectionTitle"

3953

href="#TOC2.4.3"

3954

id="Section2.4.3"

3955

name="Section2.4.3">2.4.3: XML Islands in the Spine</a>

3956

</h3>

3957

3958

3959

<a href="http://www.idpf.org/ops/ops2.0/download/OPS2.0.html#Section2.6"

3960

target="_blank"

3961

title="XML Islands">XML Islands</a> may be referenced

3962

from the spine. In the event that a Reading System cannot display the XML Island

3963

correctly, then the standard fallback methodology defined in the <a href=

3964

"http://www.idpf.org/ops/ops2.0/download/"

3965

target="_blank"

3966

title="Open Publication Structre">Open Publication Structure</a> <span class=

3967

"RFC">must be used.

3968

3969

3970

3971

In short, the Reading System must display the chosen

3972

fallback for an XML Island in the event that the

3973

island itself cannot be displayed.

3974

3975

</div>

3976

</div>

3977

3978

3979

3980

<a class="SectionTitle"

3981

href="#TOC2.5"

3982

id="Section2.5"

3983

name="Section2.5">2.5: Tours [Deprecated]</a>

3984

</h2>

3985

3986

3987

Much as a tour-guide might assemble points of interest into a set of sightseers' tours,

3988

a content provider could assemble selected parts of a publication into a set of tours

3989

to enable convenient navigation.

3990

3991

3992

3993

An OPS Package Document may, but need not, contain one

3994

tours element, which in turn contains one or more

3995

tour elements. Each tour

3996

must have a title attribute,

3997

intended for presentation to the user. Reading Systems may use

3998

tours to provide various access sequences to parts of the

3999

publication, such as selective views for various reading purposes, reader expertise

4000

levels, etc. Because Reading Systems are not required to

4001

implement tour support, content providers should also provide

4002

other means of accessing content referenced from tours.

4003

4004

4005

4006

Each tour element contains one or more <span class=

4007

"Element">site elements, each of which must have an

4008

href attribute and a <span class=

4009

"Attribute">title attribute. The href attribute

4010

must refer to an OPS Content Document included in the

4011

manifest, and may include a

4012

fragment identifier as defined in section 4.1 of RFC 2396 (see <a href=

4013

"http://www.ietf.org/rfc/rfc2396.txt"

4014

target="_blank"

4015

title="The URI RFC.">http://www.ietf.org/rfc/rfc2396.txt</a>). Each <span class=

4016

"Element">site element specifies a starting point from which the reader can

4017

explore freely. Reading Systems may use the bounds of the

4018

referenced element to determine the scope of the site. If a fragment identifier is

4019

not used, the scope is considered to be the entire document. This specification does

4020

not require Reading Systems to mark or otherwise identify

4021

the entire scope of a referenced element. The order of <span class=

4022

"Element">site elements is presumed to be significant, and <span class=

4023

"RFC">should be used by Reading Systems to aid navigation.

4024

4025

4026

4027

For example:

4028

4029

4030

4031

<tours>

4032

4033

<site title="Chicken Fingers"

4034

href="appetizers.html#r3" />

4035

<site title="Chicken a la King"

4036

href="entrees.html#r5" />

4037

</tour>

4038

4039

4040

4041

</tour>

4042

</tours>

4043

</pre>

4044

</div>

4045

4046

4047

4048

<a class="SectionTitle"

4049

href="#TOC2.6"

4050

id="Section2.6"

4051

name="Section2.6">2.6: Guide</a>

4052

</h2>

4053

4054

4055

Within the package there may be one <span class=

4056

"Element">guide element, containing one or more <span class=

4057

"Element">reference elements. The guide element

4058

identifies fundamental structural components of the publication, to enable Reading

4059

Systems to provide convenient access to them.

4060

4061

4062

4063

For example:

4064

4065

4066

4067

<guide>

4068

<reference type="toc" title="Table of Contents"

4069

href="toc.html" />

4070

<reference type="loi" title="List Of Illustrations"

4071

href="toc.html#figures" />

4072

<reference type="other.intro" title="Introduction"

4073

href="intro.html" />

4074

</guide>

4075

</pre>

4076

4077

The structural components of the books are listed in <span class=

4078

"Element">reference elements contained within the <span class=

4079

"Element">guide element. These components could refer to the table of contents,

4080

list of illustrations, foreword, bibliography, and many other standard parts of the

4081

book. Reading Systems are not required to use the <span class=

4082

"Element">guide element in any way.

4083

4084

4085

4086

Each reference must have an <span class=

4087

"Attribute">href attribute referring to an OPS Content Document included in the

4088

manifest, and which may include a

4089

fragment identifier as defined in section 4.1 of RFC 2396 (see h<a href=

4090

"ttp://www.ietf.org/rfc/rfc2396.txt"

4091

target="_blank"

4092

title="The URI RFC.">ttp://www.ietf.org/rfc/rfc2396.txt</a>). Reading Systems

4093

may use the bounds of the referenced element to determine

4094

the scope of the reference. If a fragment identifier is not used, the scope is

4095

considered to be the entire document. This specification does not

4096

require Reading Systems to mark or otherwise identify the entire scope of a

4097

referenced element.

4098

4099

4100

4101

The required type attribute

4102

describes the publication component referenced by the <span class=

4103

"Attribute">href attribute. The values for the <span class=

4104

"Attribute">type attributes must be selected from the

4105

list defined below when applicable. Other types may be used

4106

when none of the predefined types are applicable; their

4107

names must begin with the string <span class=

4108

"AttributeValue">other.. The value for the type

4109

attribute is case-sensitive.

4110

4111

4112

4113

The following list of type values is derived from the

4114

13th edition of the Chicago Manual of Style:

4115

4116

4117

4118

<tr>

4119

4120

cover

4121

</td>

4122

4123

the book cover(s), jacket information, etc.

4124

</td>

4125

</tr>

4126

4127

<tr>

4128

4129

title-page

4130

</td>

4131

4132

page with possibly title, author, publisher, and other metadata

4133

</td>

4134

</tr>

4135

4136

<tr>

4137

4138

toc

4139

</td>

4140

4141

table of contents

4142

</td>

4143

</tr>

4144

4145

<tr>

4146

4147

index

4148

</td>

4149

4150

back-of-book style index

4151

</td>

4152

</tr>

4153

4154

<tr>

4155

4156

glossary

4157

</td>

4158

4159

</td>

4160

</tr>

4161

4162

<tr>

4163

4164

acknowledgements

4165

</td>

4166

4167

</td>

4168

</tr>

4169

4170

<tr>

4171

4172

bibliography

4173

</td>

4174

4175

</td>

4176

</tr>

4177

4178

<tr>

4179

4180

colophon

4181

</td>

4182

4183

</td>

4184

</tr>

4185

4186

<tr>

4187

4188

copyright-page

4189

</td>

4190

4191

</td>

4192

</tr>

4193

4194

<tr>

4195

4196

dedication

4197

</td>

4198

4199

</td>

4200

</tr>

4201

4202

<tr>

4203

4204

epigraph

4205

</td>

4206

4207

</td>

4208

</tr>

4209

4210

<tr>

4211

4212

foreword

4213

</td>

4214

4215

</td>

4216

</tr>

4217

4218

<tr>

4219

4220

loi

4221

</td>

4222

4223

list of illustrations

4224

</td>

4225

</tr>

4226

4227

<tr>

4228

4229

lot

4230

</td>

4231

4232

list of tables

4233

</td>

4234

</tr>

4235

4236

<tr>

4237

4238

notes

4239

</td>

4240

4241

</td>

4242

</tr>

4243

4244

<tr>

4245

4246

preface

4247

</td>

4248

4249

</td>

4250

</tr>

4251

4252

<tr>

4253

4254

text

4255

</td>

4256

4257

First "real" page of content (e.g. "Chapter 1")

4258

</td>

4259

</tr>

4260

</table>

4261

</div>

4262

</div>

4263

</div>

4264

4265

4266

4267

Appendices

4268

</h1>

4269

4270

4271

4272

<a class="SectionTitle"

4273

href="#AppendixTOCA"

4274

id="AppendixA"

4275

name="AppendixA">Appendix A: The OPF Package Schema</a>

4276

</h2>

4277

4278

4279

4280

4281

4282

4283

<?xml version="1.0"?>

4284

<grammar xmlns="http://relaxng.org/ns/structure/1.0" ns="http://www.idpf.org/2007/opf"

4285

datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes">

4286

4287

<!--

4288

Title:

4289

Relax NG Schema for the Open Packaging

4290

Format (OPF) version 2.0

4291

4292

Version:

4293

2.0

4294

4295

Revision:

4296

20070222

4297

4298

Authors:

4299

This Version 2.0 :

4300

Peter Sorotokin <psorotok@adobe.com>

4301

-->

4302

4303

<start>

4304

4305

</start>

4306

4307

4308

4309

4310

4311

</attribute>

4312

</optional>

4313

</define>

4314

4315

4316

4317

4318

<text/>

4319

</attribute>

4320

</optional>

4321

</define>

4322

4323

4324

4325

4326

<text/>

4327

</attribute>

4328

</optional>

4329

</define>

4330

4331

4332

4333

4334

<text/>

4335

</attribute>

4336

</optional>

4337

</define>

4338

4339

4340

4341

4342

<text/>

4343

</attribute>

4344

</optional>

4345

</define>

4346

4347

4348

4349

4350

<text/>

4351

</attribute>

4352

</optional>

4353

</define>

4354

4355

4356

4357

4358

<text/>

4359

</attribute>

4360

</optional>

4361

</define>

4362

4363

4364

4365

4366

4367

</attribute>

4368

4369

4370

</attribute>

4371

4372

4373

</element>

4374

</define>

4375

4376

4377

4378

4379

4380

4381

4382

</optional>

4383

4384

4385

</optional>

4386

</define>

4387

4388

4389

4390

4391

4392

</element>

4393

</define>

4394

4395

4396

4397

4398

4399

4400

4401

</optional>

4402

</interleave>

4403

4404

4405

4406

</oneOrMore>

4407

4408

4409

</oneOrMore>

4410

4411

4412

</oneOrMore>

4413

4414

4415

</zeroOrMore>

4416

4417

4418

</zeroOrMore>

4419

4420

4421

</zeroOrMore>

4422

</interleave>

4423

</choice>

4424

</define>

4425

4426

4427

4428

4429

4430

</element>

4431

</define>

4432

4433

4434

4435

4436

4437

</oneOrMore>

4438

4439

4440

</oneOrMore>

4441

4442

4443

</oneOrMore>

4444

4445

4446

</zeroOrMore>

4447

</interleave>

4448

</define>

4449

4450

4451

4452

4453

4454

4455

</attribute>

4456

4457

4458

4459

4460

</element>

4461

</define>

4462

4463

4464

4465

4466

4467

4468

</element>

4469

</define>

4470

4471

4472

4473

4474

4475

4476

</element>

4477

</define>

4478

4479

4480

4481

4482

4483

4484

4485

4486

4487

</element>

4488

4489

4490

4491

4492

</element>

4493

4494

4495

4496

4497

4498

4499

</element>

4500

4501

4502

4503

4504

4505

</element>

4506

4507

4508

4509

4510

</element>

4511

4512

4513

4514

4515

</element>

4516

4517

4518

4519

4520

</element>

4521

4522

4523

4524

4525

</element>

4526

4527

4528

4529

4530

</element>

4531

4532

4533

4534

4535

</element>

4536

4537

4538

4539

4540

</element>

4541

4542

4543

4544

4545

</element>

4546

</choice>

4547

</define>

4548

4549

4550

<text/>

4551

</define>

4552

4553

4554

4555

4556

4557

</element>

4558

</define>

4559

4560

4561

4562

4563

4564

</zeroOrMore>

4565

4566

4567

</zeroOrMore>

4568

</interleave>

4569

</define>

4570

4571

4572

4573

4574

4575

4576

<text/>

4577

</attribute>

4578

4579

<text/>

4580

</attribute>

4581

4582

<attribute name="<del>schema</del><ins>scheme</ins>">

4583

<text/>

4584

</attribute>

4585

</optional>

4586

4587

</element>

4588

</define>

4589

4590

4591

4592

</define>

4593

4594

4595

4596

4597

4598

</element>

4599

</define>

4600

4601

4602

4603

4604

</oneOrMore>

4605

</define>

4606

4607

4608

4609

4610

4611

</attribute>

4612

4613

<text/>

4614

</attribute>

4615

4616

<text/>

4617

</attribute>

4618

4619

4620

4621

</attribute>

4622

</optional>

4623

4624

4625

4626

</attribute>

4627

</optional>

4628

4629

4630

<text/>

4631

</attribute>

4632

4633

4634

<text/>

4635

</attribute>

4636

</optional>

4637

</optional>

4638

4639

</element>

4640

</define>

4641

4642

4643

4644

</define>

4645

4646

4647

4648

4649

4650

4651

4652

</attribute>

4653

4654

4655

</element>

4656

</define>

4657

4658

4659

4660

4661

</oneOrMore>

4662

</define>

4663

4664

4665

4666

4667

4668

4669

</attribute>

4670

4671

4672

4673

4674

4675

</choice>

4676

</attribute>

4677

</optional>

4678

4679

</element>

4680

</define>

4681

4682

4683

4684

</define>

4685

4686

4687

4688

4689

4690

</element>

4691

</define>

4692

4693

4694

4695

4696

</oneOrMore>

4697

</define>

4698

4699

4700

4701

4702

4703

<text/>

4704

</attribute>

4705

4706

</element>

4707

</define>

4708

4709

4710

4711

4712

</oneOrMore>

4713

</define>

4714

4715

4716

4717

4718

4719

<text/>

4720

</attribute>

4721

4722

<text/>

4723

</attribute>

4724

4725

</element>

4726

</define>

4727

4728

4729

4730

</define>

4731

4732

4733

4734

4735

4736

</element>

4737

</define>

4738

4739

4740

4741

4742

</zeroOrMore>

4743

</define>

4744

4745

4746

4747

4748

4749

<text/>

4750

</attribute>

4751

4752

4753

<text/>

4754

</attribute>

4755

4756

4757

<text/>

4758

</attribute>

4759

4760

</element>

4761

</define>

4762

4763

4764

4765

</define>

4766

4767

4768

4769

4770

4771

4772

4773

</except>

4774

</anyName>

4775

4776

4777

4778

4779

</attribute>

4780

<text/>

4781

4782

</choice>

4783

</zeroOrMore>

4784

</element>

4785

</define>

4786

4787

</grammar>

4788

</pre>

4789

</div>

4790

4791

4792

4793

<a class="SectionTitle"

4794

href="#AppendixTOCB"

4795

id="AppendixB"

4796

name="AppendixB">Appendix B: Contributors</a>

4797

</h2>

4798

4799

4800

This specification has been developed through a cooperative effort, bringing together

4801

publishers, Reading System vendors, software developers, and experts in the relevant

4802

standards.

4803

4804

4805

4806

Version 2.0 of this specification was prepared by the International Digital Publishing

4807

Forum (IDPF) Open Publication Publication Structure (OEBPS) Working Group. Members of the

4808

working group at the time of publication of revision 2.0 were:

4809

4810

4811

4812

<li>Angel Ancin, iRex Technologies

4813

</li>

4814

4815

<li>Rick Bowes, Thomson Learning

4816

</li>

4817

4818

<li>Peter Brantley, Digital Library Federation

4819

</li>

4820

4821

<li>Clint Brauer, SONY

4822

</li>

4823

4824

<li>Ken Brooks, Thomson Learning

4825

</li>

4826

4827

<li>Janice Carter, Benetech

4828

</li>

4829

4830

<li>Richard Cohn, Adobe Systems, Inc.

4831

</li>

4832

4833

<li>Garth Conboy, Publication Technologies, Inc. (Working Group co-Chair)

4834

</li>

4835

4836

<li>Neil De Young, Hachette Book Group

4837

</li>

4838

4839

<li>Linh Do, Random House

4840

</li>

4841

4842

<li>Brady Duga, Publication Technologies, Inc.

4843

</li>

4844

4845

<li>Geoff Freed, WGBH

4846

</li>

4847

4848

<li>Markus Gylling, <del>Daisy</del><ins>DAISY</ins> Consortium

4849

</li>

4850

4851

<li>Jonathan Hevenstone, Publishing Dimensions (Working Group Vice Chair)

4852

</li>

4853

4854

<li>Rick Johnson, VitalSource Technologies

4855

</li>

4856

4857

<li>George Kerscher, <del>Daisy</del><ins>DAISY</ins> Consortium

4858

</li>

4859

4860

<li>Steve Kotrch, Simon & Schuster

4861

</li>

4862

4863

<li>Bill McCoy, Adobe Systems, Inc.

4864

</li>

4865

4866

<li>Jon Noring, Digital Pulp Publishing

4867

</li>

4868

4869

<li>Siobhan Padgett, Hachette Book Group

4870

</li>

4871

4872

<li>Mina Park, Holtzbrinck Publishers

4873

</li>

4874

4875

<li>John Rivlin, Publication Technologies, Inc. (Working Group co-Chair)

4876

</li>

4877

4878

<li>Tyler Ruse, CodeMantra

4879

</li>

4880

4881

<li>Mike Smith, Harlequin

4882

</li>

4883

4884

<li>Peter Sorotokin, Adobe Systems, Inc.

4885

</li>

4886

4887

<li>Jennifer Sutton, Benetech

4888

</li>

4889

4890

<li>Ben Trafford, Invited Expert

4891

</li>

4892

4893

<li>Gary Varnell, Osoft

4894

</li>

4895

4896

<li>Eli Willner, Green Point Technology Services

4897

</li>

4898

4899

<li>Ric Wright, Adobe Systems, Inc.

4900

</li>

4901

</ul>

4902

4903

4904

The prior version of the OPS specification, on which this effort is based, was OEBPS 1.2.

4905

OEBPS 1.2 was developed by the Open Publication Forum Publication Structure Working

4906

Group. Active members that that working group during development of OEBPS 1.2 were:

4907

4908

4909

4910

<li>Jeff Alexander, Franklin Electronic Publishers

4911

</li>

4912

4913

<li>Garth Conboy, Gemstar Publication Group Limited (Version 1.2 Co-Editor)

4914

</li>

4915

4916

<li>Eva Conkright, Random House

4917

</li>

4918

4919

<li>Brady Duga, Gemstar Publication Group Limited (Version 1.2 Co-Editor)

4920

</li>

4921

4922

<li>Jerry Dunietz, Microsoft Corporation (Working Group Vice Chair)

4923

</li>

4924

4925

<li>David Goldstein, Versaware Inc.

4926

</li>

4927

4928

<li>Gene Golovchinsky, FX Palo Alto Laboratory, Inc. (Development Sub-Group Co-Chair)

4929

</li>

4930

4931

<li>Donald Goyette, McGraw-Hill

4932

</li>

4933

4934

<li>Rebecca Guenther, Library of Congress

4935

</li>

4936

4937

<li>Markku Hakkinen, isSound Corporation

4938

</li>

4939

4940

<li>Barbara Hammond, Nokia

4941

</li>

4942

4943

<li>Benjamin Jung, deepX

4944

</li>

4945

4946

<li>George Kerscher, <del>Daisy</del><ins>DAISY</ins> Consortium

4947

</li>

4948

4949

<li>Christopher R, Maden, crism consulting

4950

</li>

4951

4952

<li>Bob Mathews, Adobe

4953

</li>

4954

4955

<li>Michael Moodie, National Library Service for the Blind and Physically Handicapped,

4956

Library of Congress

4957

</li>

4958

4959

<li>Jon Noring, Windspun Inc. (Maintenance Sub-Group Chair)

4960

</li>

4961

4962

<li>David Pawson, Royal National Institute for the Blind

4963

</li>

4964

4965

<li>Chris Powell, University of Michigan Library

4966

</li>

4967

4968

<li>James Pritchett, Recording for the Blind and Dyslexic

4969

</li>

4970

4971

<li>Allen Renear, Brown University Scholarly Technology Group (Working Group Chair)

4972

</li>

4973

4974

<li>Dorothea Salo, OverDrive, Inc. (Working Group Scribe)

4975

</li>

4976

4977

<li>Ilan Sender, Microsoft Corporation

4978

</li>

4979

4980

<li>Sheela Sethuraman, CAST

4981

</li>

4982

4983

<li>Roger Sperberg, e-bks, LLC

4984

</li>

4985

4986

<li>Patrick Stickler, Nokia

4987

</li>

4988

4989

<li>Lisa Rupe, Questia Media Inc.

4990

</li>

4991

4992

<li>Mikhail Vaysbukh, Data Conversion Laboratory

4993

</li>

4994

4995

<li>Garret Wilson, GlobalMentor, Inc. (Development Sub-Group Co-Chair)

4996

</li>

4997

4998

<li>Harrison Yee, Apex

4999

</li>

5000

</ul>

5001

</div>

5002

5003

5004

5005

<a class="SectionTitle"

5006

href="#AppendixTOCC"

5007

id="AppendixC"

5008

name="AppendixC">Appendix C: Acknowledgements</a>

5009

</h2>

5010

5011

5012

The working group wishes to specifically acknowledge the contributions of the following

5013

individuals. Peter Sorotokin for authoring the OPS and OPF

5014

RelaxNG schemas, creation of the NVDL definition of OPS, and general technical acumen.

5015

Ben Trafford for the concept and drafting of XML Islands,

5016

as well as overall technical participation, and the XML templates used to produce the

5017

specifications. George Kerscher for drafting the OPF NCX

5018

section, providing consistent accessibility direction and broad technical input.

5019

Brady Duga and Jon Noring for

5020

directional contributions, specification editing and providing continuity with the

5021

historic OEBPS 1.2 effort. Garth Conboy for working group

5022

leadership and motivation, specification drafting and technical contributions.

5023

5024

</div>

5025

5026

5027

5028

<a class="SectionTitle"

5029

href="#AppendixTOCD"

5030

id="AppendixD"

5031

name="AppendixD"><ins>Appendix D: Supporting Information & Errata</ins></a>

5032

</h2>

5033

5034

5035

<ins>For additional information about all IDPF specifications including sample files,

5036

specification implementations and other information, please visit our public forums at

5037

<a href="http://www.idpf.org/forums"

5038

target="_blank"

5039

title="IDPF Forums">http://www.idpf.org/forums</a>. If errors in the specifications

5040

are identified following publication, please post these errors to the forums. The

5041

responsible Working Group will review the errors and post pending corrections to the

5042

specifications if required or necessary. Corrections will be incorporated into

5043

subsequent versions of the specifications.</ins>

5044

5045

</div>

5046

</div>

5047

</body>

5048

</html>