mailschema 0.3.0 → 0.3.1

package/README.md

@@ -3,7 +3,7 @@
 [Mail Action Protocol](https://mailschema.org) 0.3 for JavaScript. It parses and checks MAP descriptions, type contracts and Registry implementation records, and computes the RFC 8785 digests that identify contracts. The same code runs the MailSchema specification's own checks. It has no Node.js-only dependencies, so it also runs in browsers and workers.
 
 ```sh
-npm install mailschema@0.3.0
+npm install mailschema@0.3.1
 ```
 
 ## Check a description against its contract
@@ -34,11 +34,13 @@ The profile record, context and schemas are exported byte for byte: `mailschema/
 ## Command line
 
 ```sh
-npx mailschema@0.3.0 contract campaign-send-approval-0.1.json
-npx mailschema@0.3.0 description description.json --contract campaign-send-approval-0.1.json
-npx mailschema@0.3.0 implementation record.json
+npx mailschema@0.3.1 contract campaign-send-approval-0.1.json
+npx mailschema@0.3.1 description description.json --contract campaign-send-approval-0.1.json
+npx mailschema@0.3.1 implementation record.json
 ```
 
+Each command first prints a line naming what it checked. `contract` prints `Valid type contract <id> <version>` and, on the second line, the contract's digest. `description` prints `Valid MAP 0.3 description <@id>` and, on the second line, the description's digest; with `--contract`, it first checks that the description uses that contract as it allows. `implementation` prints `Valid implementation record for <service>`. A digest is `sha-256:` and the SHA-256 of the document's RFC 8785 canonical JSON, the value `digest()` returns; the description's digest is not the contract digest it names. An invalid file prints every reason on standard error and exits with status 1. Nothing is uploaded or changed.
+
 Checking does not authenticate a message, establish a service's authority or perform an action. Those belong to the implementation, under the [specification](https://mailschema.org/specification/core).
 
 Source: [mailschema/javascript](https://github.com/mailschema/javascript). License: MIT.

package/bin/mailschema.js

@@ -4,6 +4,7 @@ import { parseArgs } from 'node:util';
 import {
   Contract,
   CONTRACT_MAX_BYTES,
+  digest,
   InvalidDocument,
   parseDescription,
   parseImplementation,
@@ -16,9 +17,10 @@ const help = `Mail Action Protocol 0.3 checks
   mailschema implementation <record.json>
 
 contract checks a type contract and prints its digest. description checks a
-description and, with --contract, that it uses that contract as it allows.
-implementation checks a Registry implementation record. Nothing is uploaded
-or changed.`;
+description and, with --contract, that it uses that contract as it allows,
+then prints the description's digest. implementation checks a Registry
+implementation record. A digest is the SHA-256 of the document's RFC 8785
+canonical JSON. Nothing is uploaded or changed.`;
 
 async function read(path) {
   const info = await stat(path);
@@ -48,7 +50,7 @@ try {
     const description = parseDescription(await read(path));
     if (values.contract)
       report(Contract.parse(await read(values.contract)).descriptionErrors(description));
-    console.log(`Valid MAP 0.3 description ${description['@id']}`);
+    console.log(`Valid MAP 0.3 description ${description['@id']}\n${digest(description)}`);
   } else if (command === 'implementation') {
     const record = parseImplementation(await read(path));
     console.log(`Valid implementation record for ${record.service}`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mailschema",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "Mail Action Protocol 0.3: parse and check descriptions, type contracts and implementation records",
   "type": "module",
   "license": "MIT",