In the FHIR Core Subscriptions page, we have a Conformance section that references a "guide":

https://build.fhir.org/subscriptions.html#conformance

"In order to claim conformance with this guide, a server: .."

Was this copy/pasted from the backport IG?  That statement, in the context of FHIR Core, implies that to claim conformance to the FHIR R5 Core spec, a server must support write for Subscription (among other things), which likely isn't the intent.

Also, related to FHIR-43505, should conformance to whatever "thing" we want to name in the core spec require support for dynamic subscriptions (using my term from FHIR-43505)?  Or should a server that only supports administratively created subscriptions be able to claim conformance as well? Or should there be two different named things (one for dynamic, one for administrative) that servers could claim conformance to?