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

XML/JSON parsers should fail for the elements that can't be recognised. #152

Open
czajek opened this Issue Apr 9, 2015 · 4 comments

Comments

Projects
None yet
3 participants
@czajek

czajek commented Apr 9, 2015

We make use of HAPI parsers for the validation purpose. Right now parsers accept content that contains unsupported elements (it ignores such elements). For example content below passes validation:

<Patient>
    <someUnsupportedElement/>
</Patient>

Is it possible to configure parsers so it fails in mentioned scenario.

@czajek

This comment has been minimized.

czajek commented Apr 15, 2015

It's the same problem with single element added twice for example:

<Patient>
    <active value="true"/>
    <active value="true"/>
</Patient>
@jamesagnew

This comment has been minimized.

Owner

jamesagnew commented Apr 15, 2015

FYI- My plan for addressing this issue is to add a 'strict' mode to the parser, probably next week some time.

Per a discussion with Bill De Beaubien, we should also error out if a resource contains an empty tag (i.e. no term)

@izi

This comment has been minimized.

izi commented May 14, 2015

Is it still on your roadmap? Will this be a part of 1.0 or 1.1 release?

@jamesagnew

This comment has been minimized.

Owner

jamesagnew commented May 14, 2015

Hi All,

This is still very much on the roadmap. Unfortunately it did not make it in
for the 1.0 release, which I wanted to get out quickly because there are a
few minor breaking API changes needed for the harmonization work we're
doing with the HL7.org Java RI. This should land in the development builds
fairly soon.

Cheers,
James

On Thu, May 14, 2015 at 8:19 AM, izi notifications@github.com wrote:

Is it still on your roadmap? Will this be a part of 1.0 or 1.1 release?


Reply to this email directly or view it on GitHub
#152 (comment)
.

jamesagnew added a commit that referenced this issue May 27, 2015

jamesagnew added a commit that referenced this issue Jul 21, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment