IIIF Presentation Preflight
Pricing
$100.00 / 1,000 completed reports
IIIF Presentation Preflight
Check a supplied IIIF Presentation 3 Manifest against a narrow inline-image profile. Inspect declaration shapes, language maps, IDs and targets without fetching resources. Receive one complete JSON report. USD 0.10 per completed report, platform usage included. Not full IIIF conformance.
Pricing
$100.00 / 1,000 completed reports
Rating
0.0
(0)
Developer
Picknotes
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Check one supplied Manifest against a narrow Presentation 3.0 inline-image profile: inline Canvas, AnnotationPage and painting Annotation objects with a single Image body. The report checks declaration shapes, language maps, IDs and target relationships. It does not fetch contexts, pages, images or services. It does not provide full IIIF conformance, viewer compatibility, rights, ownership, authentication, image availability or pixel assurance. Unsupported coverage produces an incomplete report and cannot become an eligible completed delivery. A complete report may contain error findings.
Use the synthetic demo with own-data fields absent. Own mode requires useDemo=false, manifestJson and authorizedNonpersonalNonconfidentialData=true. Supply only authorized, nonpersonal and nonconfidential data. The exact original Manifest text is passed to the reviewed native parser; no input trimming, URI normalization or report rewriting occurs. The platform stores input before execution. No confidentiality, retention, deletion, location or secret-detection guarantee is made.
One eligible completed report uses one full thirteen-field dataset item. Export raw JSON without field selection, cleaning, flattening or unwinding. No report files are written to key-value storage. Each completed report costs USD 0.10, including platform usage and reports with findings; check the current platform price before running. The receipt binds the expected identity of the completion event. It does not prove sender authenticity, configured billing, a charge or settlement. An uncertain append may already be billed: never automatically repost or rerun it.
The optional four-file buyer helper verifies the complete source-free public consistency policy and extracts the exact report bytes. If you have the helper, run python3 -B extract.py item.json new-report.json using a raw item or singleton export. It checks shapes, canonical encoding, hashes, occurrence capacities, finding roles and locations, language and identity relationships, expected receipt and delivery identity. It does not have original input and cannot prove semantic completeness or sender authenticity. Optional unobserved maps and possible per-Page allocations remain genuine ambiguities. The private original-input semantic verifier is separate and is not bundled. Existing output files and symlink paths are refused; use trusted local parent directories and review reports before sharing them.
Limits remain 2 MiB for raw Manifest input, depth 32, 500 Canvas slots, 1,000 AnnotationPage slots and 1,000 Annotation slots. Native reports remain bounded at 4 MiB, while the exact eight-byte worker frame and actual escaped singleton dataset item each fit 4,500,000 bytes. Dynamic report capacity is min(4194304,4499992-inputBytes); receipt capacity is 2,048 bytes. Oversized results fail before append without truncation. Private workers retain 10 seconds, the outer entry 50 seconds, CPU soft/hard 30 seconds and Linux AS 448 MiB lower-only ceilings. Execution rejects unsupported inherited signal/timer or consumed-CPU state.
Read or save your report
The full report is already in the dataset item's reportJson field. You do not need a helper download to read or save it. Open the raw dataset items output, export JSON with every field intact, and save it locally as item.json. Do not enable cleaning, flattening, unwinding or field selection. Use either a single item object or a one-item JSON array.
To save the report with only Python's standard library, save the following as save_report.py, then run python3 save_report.py item.json new-report.json. Use a new output filename and a trusted local directory. This checks the recorded byte count and hash and writes the UTF-8 report text without changing its final newline. It is basic extraction, not full report consistency validation, original-input verification or sender authentication.
import hashlibimport jsonimport sysfrom pathlib import Pathvalue = json.loads(Path(sys.argv[1]).read_text(encoding="utf-8"))if isinstance(value, list):if len(value) != 1:raise ValueError("Expected exactly one dataset item")value = value[0]raw = value["reportJson"].encode("utf-8")if len(raw) != value["reportBytes"]:raise ValueError("Report byte count mismatch")if hashlib.sha256(raw).hexdigest() != value["reportSha256"]:raise ValueError("Report hash mismatch")with open(sys.argv[2], "xb") as output:output.write(raw)
For additional consistency checks, use the optional reviewed buyer helper with its extract.py, README.md, TERMS.md and MANIFEST.json kept together. The helper also checks the expected receipt and delivery identity and refuses existing output files and symlink output paths. It does not establish the truth of the original input or settled billing. Review reports before sharing them. No separate public hosting service or helper download is required for the basic extraction above.