pdf.md

PDF Profile

Editors:

• Michael Benowitz (NYPL)
• Laurent Le Meur (EDRLab)

Participate:

• GitHub readium/webpub-manifest
• File an issue

Example

{
  "@context": "http://readium.org/webpub-manifest/context.jsonld",
  
  "metadata": {
    "@type": "http://schema.org/Book",
    "conformsTo": "https://readium.org/webpub-manifest/profiles/pdf",
    "title": "Moby-Dick",
    "author": "Herman Melville",
    "language": "en"
  },

  "links": [
    {"rel": "self", "href": "http://example.org/manifest.json", "type": "application/webpub+json"},
  ],

  "readingOrder": [
    {
      "href": "http://example.org/mobydick-part1.pdf", 
      "type": "application/pdf", 
    },
    {
      "href": "http://example.org/mobydick-part2.pdf", 
      "type": "application/pdf", 
    }
  ],
  
  "resources": [
    {"rel": "cover", "href": "http://example.org/cover.jpeg", "type": "image/jpeg", "height": 600, "width": 300}
  ]
}

Introduction

The goal of this specification is to provide a profile of the Readium Web Publication Manifest dedicated to PDF documents.

It is mostly used as a basis for the specification of a method for protecting PDF files using LCP, i.e. LCP for PDF.

This profile relies on:

• a declaration of conformance with this Profile,
• a restriction on the resources of the reading order,

1. Declaring conformance with the PDF Profile

To declare that it conforms to the PDF Profile, a Readium Web Publication Manifest must include a conformsTo key in its metadata section, with https://readium.org/webpub-manifest/profiles/pdf as one of its value.

2. Restriction on resources in the reading order

In addition to the normal requirements of a readingOrder, all Link Objects must point strictly to PDF resources, with no fragment identifier.