docs: add "Implementations in the wild" section (refs #26, #66) - #71
Open
YE-YI7 wants to merge 1 commit into
Open
docs: add "Implementations in the wild" section (refs #26, #66)#71YE-YI7 wants to merge 1 commit into
YE-YI7 wants to merge 1 commit into
Conversation
…ards-project#66) Creates the section proposed in ards-project#26 and lists the ASM tool-selection catalog, following the invitation in ards-project#66. Verified with this repo's conformance CLI v0.5.0 against the live endpoint before opening: PASS, 0 critical errors, 30 warnings — all of them the media-type finding that ards-project#66 asks about. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Creates the
Implementations in the wildsection proposed in #26, and adds the ASM tool-selection catalog to it — following @mindpower's invitation in #66.Per the README's contribution split this is a non-normative documentation change (no edits to
spec/ard.mdorspec/schemas/), so I'm opening it directly as a PR rather than an issue.Conformance
Verified against the live endpoint with this repo's CLI (v0.5.0) immediately before opening:
All 30 warnings are the same finding —
Media type 'application/asm+json' is not one of standard discovery types— which is exactly what #66 asks about. I've noted that inline in the table rather than leaving it implicit, so the row doesn't read as a clean bill of health while that question is still open. If you'd rather the section only list types already in the allowlist, I'm happy to drop the row until #66 is resolved.One more caveat, also in the table: the catalog is hosted on a free tier that sleeps when idle, so the first request after a quiet period can be slow or need a retry. Flagging it up front so a timeout doesn't get read as a dead endpoint.
On #26
#26 proposed this same section back in June for five conformance-tested deployments (SnowSure, SnowData, Afore, LUXSKI, Ski Limone), and the section itself doesn't appear to have landed — so this PR creates it.
I've deliberately not added those five, since their conformance status isn't mine to assert. @mikeslone — happy to include them in this PR if you'd like, or maintainers can land them separately. Placement, ordering, and wording are all yours to change; I have no attachment to the table format.
(Implementation and this PR drafted with Claude, at my direction and with my approval.)