Stream: IG creation
Topic: Jira Spec File --> Named wrong...
Saul Kravitz (Aug 12 2020 at 20:12):
I get the following error, but I don't know what user error I'm committing.
There is no jira specification file defined with the expected name of FHIR-us-davinci-pdex-plan-net in the xml folder of the https://github.com/HL7/Jira-Spec-Artifacts project. This must exist before ballot or publication.
This file exists, almost...it is not quite a match (plannet vs plan-net): https://github.com/HL7/JIRA-Spec-Artifacts/blob/master/xml/FHIR-us-davinci-plannet.xml
Is the XML file named wrong, or do I need to something in my IG to have the publisher look in the right place?
Paul Denning (Aug 12 2020 at 21:27):
also missing "-pdex"
Eric Haas (Aug 12 2020 at 22:16):
see this thread for how to fix: https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/what.20do.20I.20do.20about.20this.20warning.3F
Saul Kravitz (Sep 01 2020 at 11:24):
I think I followed the directions. There is still an error when I try to build it because I'm trying to deprecate one name and add the correct name:
[xslt] ERROR: Specification with effective key FHIR-us-davinci-plannet has been removed or changed. Keys should never change - just change the name. Keys should also not usually be removed. Instead, set the 'deprecated' flag to true. Keys can only be removed if no JIRA tracker references that specification. If this is the case and the key should really be removed, please coordinate with an administrator.
That is precisely what I was trying to do.
https://github.com/HL7/JIRA-Spec-Artifacts/pull/75
Lloyd McKenzie (Sep 01 2020 at 15:40):
You can't deprecate a name. You just change the name (and perhaps put the old one in brackets). E.g. "CapabilityStatement (Conformance)". The key should never be removed or changed. (The key for CapabilityStatement remains 'conformance' - and will be that way forever.)
Last updated: Apr 12 2022 at 19:14 UTC
