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

FYI: Misspelling in conformance xsd @ Gazelle #5

Open
jkiddo opened this issue Jan 5, 2016 · 7 comments
Open

FYI: Misspelling in conformance xsd @ Gazelle #5

jkiddo opened this issue Jan 5, 2016 · 7 comments

Comments

@jkiddo
Copy link

jkiddo commented Jan 5, 2016

http://gazelle.ihe.net/jira/browse/HLVAL-285

@unixoid
Copy link
Member

unixoid commented Jan 5, 2016

This XML Schema is defined by the "Conformance and Guidance for Implementation/Testing" (CGIT) working group of the HL7 organization, therefore I suppose that you should submit a HL7 change request. HL7 v2.8.2 still contains this typo (volume 2B, page 47).

@jkiddo
Copy link
Author

jkiddo commented Jan 5, 2016

I've written to Frank Oemig - I hope he will take action on it

@jkiddo
Copy link
Author

jkiddo commented Jan 7, 2016

IHE has now corrected its schemas: http://gazelle.ihe.net/XSD/HL7/V2/HL7MessageProfileSchema.xsd

@unixoid
Copy link
Member

unixoid commented Jan 7, 2016

Aehm... And made them incompatible with non-IHE conformance profiles?

@jkiddo
Copy link
Author

jkiddo commented Jan 10, 2016

Well ... that depends. I thought that the xsd previously referred to was dictated by the HL7 standard and not IHE specific?

@unixoid
Copy link
Member

unixoid commented Jan 10, 2016

Yes, the XSD document is the one originally provided by the HL7 organization. IHE has changed the name of an XML element there (because of a typo) -- and in that way we have two different variants of the XSD document now. I suppose the right way would be to wait until the "master" specification is corrected, let it be in HL7 v2.9 or v2.10...

@jkiddo
Copy link
Author

jkiddo commented Jan 10, 2016

I will let that be between IHE and HL7 to decide. IHE has now corrected it. I get your point, and perhaps IHE should act in the way you suggest - they have however not chosen to do so. The WG CGIT has accepted the bug and they have said that they also would like to take the document of the word doc and instead reference it. I do not know when CGIT will execute that plan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants