You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When specifying your ImplementationGuide.contact.telecom.value for an IG managed by TI, the following warning is issued unless you match the URL indicated exactly (specifically, with init-capped Vocab):
The nominated WG 'vocab' means that the contact url should be 'http://www.hl7.org/Special/committees/Vocab' but it was not found
However, if you use this URL with the init-capped Vocab, the jira-new.xml template that gets generated has a null value for specification.defaultWorkgroup.
If you change the url to use lowercase vocab as follows - the jira-new.xml template is generated property, but warnings are issued by the IG publisher:
To me, the simplest solution is to update the IG Publisher to check for the URL with lowercase Vocab, as that is a functional URL and allows the jira-new.xml template to continue to be generated as is.
The text was updated successfully, but these errors were encountered:
Confirming - updating the ImplementationGuide.contact.telecom.value="http://www.hl7.org/Special/committees/Vocab" now properly generates the jira-new.xml with specification@defaultWorkgroup="vocab"
When specifying your ImplementationGuide.contact.telecom.value for an IG managed by TI, the following warning is issued unless you match the URL indicated exactly (specifically, with init-capped Vocab):
The nominated WG 'vocab' means that the contact url should be 'http://www.hl7.org/Special/committees/Vocab' but it was not found
However, if you use this URL with the init-capped Vocab, the jira-new.xml template that gets generated has a null value for specification.defaultWorkgroup.
If you change the url to use lowercase vocab as follows - the jira-new.xml template is generated property, but warnings are issued by the IG publisher:
http://www.hl7.org/Special/committees/vocab
To me, the simplest solution is to update the IG Publisher to check for the URL with lowercase Vocab, as that is a functional URL and allows the jira-new.xml template to continue to be generated as is.
The text was updated successfully, but these errors were encountered: