Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improper warning for TI contact URL #939

Open
russellott opened this issue Aug 13, 2024 · 2 comments
Open

Improper warning for TI contact URL #939

russellott opened this issue Aug 13, 2024 · 2 comments
Labels
Approved Change has been reviewed and accepted and can now be applied to the templates bug Something isn't working

Comments

@russellott
Copy link

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.

@lmckenzi
Copy link
Contributor

Vocab, apparently, is special. We've revised it in JiraSpec so it should now accept 'Vocab'. Please check to see if this is now addressed.

@lmckenzi lmckenzi added bug Something isn't working Approved Change has been reviewed and accepted and can now be applied to the templates labels Aug 13, 2024
@russellott
Copy link
Author

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"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Approved Change has been reviewed and accepted and can now be applied to the templates bug Something isn't working
Projects
Status: In progress
Development

No branches or pull requests

2 participants