CA Baseline Canonicals- Assessing Impact to Inform Decision

Hey Folks -

We're getting new errors in CA Baseline that are tied to our canonical url convention. You can read the summary of topic here .
We need to make a decision to stay with the same canonical convention or change, and need your help (authors, vendors/systems) to inform that decision!

We understand author/designers that have re-profiled from CA Baseline artefacts will be the primary impacted party if the canonicals changes (would need to perform updates to the basedefinition, refresh of package, documentation, etc.). Let us know if you are an impacted author in the chat so we can assess breadth of impact.

We really want to understand impacts to vendors/systems/production data. We've narrowed down the areas most likely to be impacted by canonical changes to our artefacts:

• Are you using any of the CA Baseline Extensions in production?
• Are you performing validation directly against any CA Baseline artefacts?
• Have you written code that is hardcoded against the canonical (vs package dependencies)?

We are working in the background with HL7 International to pursue a grandfathered exception to continue using our canonical - but want to do our due diligence at the same time to assess risks for all options.