@openpresentation/opf 0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Data-Advantage
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,103 @@
+# @openpresentation/opf
+
+Canonical Open Presentation Format package for JavaScript and TypeScript.
+
+Publishes the OPF schemas, catalog presets, generated TypeScript types, and local validation helpers. The schema is pre-stable (0.x — expect breaking changes between minor versions until 1.0). This package does not render PowerPoint files, parse `.pptx`, fetch remote catalogs, or use AI.
+
+Repository: https://github.com/OpenPresentation/opf
+
+## File naming
+
+Use `*.opf.json` for complete Open Presentation Format documents, such as `deck.opf.json`.
+
+OPF documents are plain JSON, and the `.opf.json` suffix keeps that visible to editors, validators, agents, and repository tooling. Avoid bare `*.opf` for OPF JSON because that extension is already used by other document and project formats.
+
+## Install
+
+```sh
+pnpm add @openpresentation/opf
+# or: npm install @openpresentation/opf
+# or: yarn add @openpresentation/opf
+```
+
+Requires Node 20 or later.
+
+## Usage
+
+Use the common root API for most application code:
+
+```ts
+import {
+  presentation,
+  audiences,
+  tones,
+  catalogs,
+  validate,
+  validatePresentation,
+} from "@openpresentation/opf";
+
+import type { Presentation } from "@openpresentation/opf";
+
+const deck: Presentation = {
+  name: "Quarterly Review",
+  slides: [{ title: "Quarterly Review", items: ["Revenue", "Product", "Hiring"] }],
+};
+
+console.log(presentation.$id);
+console.log(validatePresentation(deck).valid);
+console.log(validate(tones[0], "tones").valid);
+console.log(audiences.map((audience) => audience.id));
+console.log(Object.keys(catalogs));
+```
+
+Use focused imports when you only need one surface:
+
+```ts
+import { presentation, audience } from "@openpresentation/opf/schemas";
+import { audiences, tones } from "@openpresentation/opf/catalogs";
+import { validate, assertValid } from "@openpresentation/opf/validator";
+import type { Presentation, Audience, Tone } from "@openpresentation/opf/types";
+```
+
+Validate catalog records locally:
+
+```ts
+import { audiences, validateCatalogRecord } from "@openpresentation/opf";
+
+for (const record of audiences) {
+  const result = validateCatalogRecord("audiences", record);
+  if (!result.valid) {
+    console.error(result.errors);
+  }
+}
+```
+
+Raw canonical JSON is published under `spec/`:
+
+```ts
+import presentationSchema from "@openpresentation/opf/spec/schemas/opf.schema.json" with {
+  type: "json",
+};
+```
+
+Package-addressable catalog paths can be used by OPF catalog resolvers:
+
+```json
+{
+  "catalogs": {
+    "narratives": {
+      "source": "pkg:@openpresentation/opf/spec/catalogs/narratives"
+    }
+  }
+}
+```
+
+## Development
+
+```sh
+pnpm --filter @openpresentation/opf typecheck
+pnpm --filter @openpresentation/opf test
+pnpm --filter @openpresentation/opf pack:dry-run
+```
+
+`src/generated/` and `dist/` are generated from the root `spec/` directory and are intentionally ignored by git.