Reference publisher: Snowdata / SnowSure — travel & outdoor snow intelligence #11

Activity

1. mikeslone commented on Jun 18, 2026

   

   mikeslone

   on Jun 18, 2026

   Author

   More actions

   Network update since this was opened: the verified federation has grown beyond SnowSure + Snowdata to five independent publishers — SnowSure, Snowdata, LUXSKI, Afore, and Ski Limone — each serving its own signed ai-catalog.json. The Snowdata/SnowSure registry (POST /api/ard/search, alias /search) now federates all of them: 44 indexed resources, 41 verified via did:web identity + Ed25519 entry-bound trust-manifest signatures (RFC 7515 detached JWS over RFC 8785 JCS). Verification is enforced — only signed, verified entries are ranked.

   On the open question above ("is there a planned index of reference publishers we should be listed on?"): beyond the publisher PRs (#12, #15), we'd suggest the registry itself is a candidate for the Reference Implementations page as the first vertical (domain-specific) discovery service, alongside Hugging Face Discover, GitHub Agent Finder, and Cisco AI Catalog — it demonstrates ARD federation + trust working end-to-end for a single domain. Happy to open that PR if it's wanted.

   Open standard for the vertical (publish + sign + verify): https://opensourcesnow.com

   Quick check across the federated network:

   curl -sS -X POST https://www.snowsure.ai/search \
     -H 'content-type: application/json' \
     -d '{"query":{"text":"best powder in the Alps this week"}}' \
     | jq -r '.results[] | "\(.score)\t\(.source)\t\(.displayName)"'
   
2. mikeslone commented on Jun 19, 2026

   

   mikeslone

   on Jun 19, 2026

   Author

   More actions

   Update: all of our catalogs now pass this repo's conformance CLI (conformance/bin/conformance-test manifest <url>) — 5/5, zero critical errors.

   Publisher	Domain	Role	Conformance
   SnowSure	snowsure.ai	Discovery registry (ski & snow) + publisher	PASS
   SnowData	snowdata.ai	Discovery registry (ski & snow) + publisher	PASS
   Afore	afo.re	Discovery registry (editorial travel) + publisher	PASS
   LUXSKI	lux.ski	Publisher	PASS
   Ski Limone	skilimone.com	Publisher	PASS

   Five independent did:web publishers; three run live ARD POST /search registries with cross-federation. All entries carry did:web + Ed25519 entry-bound detached JWS (RFC 7515 over RFC 8785 JCS), with keys at /.well-known/did.json. Reference registry: POST https://www.snowsure.ai/search.

   Running the CLI surfaced two genuinely useful spec-strictness points for other implementers, FWIW:

   1. The host object is additionalProperties: false — url/description/contact aren't allowed there (only displayName, identifier, documentationUrl, logoUrl, trustManifest).
   2. trustManifest doesn't permit ad-hoc fields like workloadIdentity/publishedFrom; publishing origin goes in provenance[] and attestations require mediaType.

   Happy to open a PR adding an "implementations in the wild" table to the README — glad to match whatever placement/format you'd prefer.
3. mindpower commented on Oct 11, 2026

   

   mindpower

   on Oct 11, 2026

   Collaborator

   More actions

   Closing per the note on #26. Thanks!
4. mindpower

   closed this as completedon Oct 11, 2026