Hi Bert, I'll clarify because what you interpreted is not what I tried to say,
but we're on the same page.
> Date: Tue, 13 May 2014 08:47:35 +0200
> From: bert.verhees at rosa.nl
> To: openehr-technical at lists.openehr.org
> Subject: Re: Cyclic datatypes: OpenEHR virus
>
> On 13-05-14 07:22, Ing. Pablo Pazos wrote:
> > If the value is not constrained, the validator should return true without
> > continuing checking in cascade-recursive mode. For this to work as
> > expected, the data structure should be validated before than the data
> > validation. The easiest way of validating the structure is serializing the
> > instance to XML and using XSD.
>
> That is the problem, I do not agree, it has to check in cascade because
> there can be required properties left out, or fantasized properties
> which make no sense put in. Every occurring class in a dataset needs, in
> my opinion, to be validated, if there are no constraints, against the
> Reference Model-rules.
What I meant with "structure validation" is to validate against the IM (i.e.
syntactic validation), when I say "data validation" I mean to validate against
archetypes (i.e. semantic validation).
If the constraint over a node is "not constrained at all", so there are not
required values defined by the archetype, but, there might be required values
defined by the information model.
>
> By the way, you cannot validate OpenEHR datasets against an archetype by
> using XSD. You cannot create XSD's according archetype-constraints, not
> even by hand. I have been there, a few years ago.
>
The information model can be validated with the XSDs, because the XSDs define
the IM constraints.
The XSDs are not to validate against archetypes (totally agree with you), is
the IM validation that validates the structure and some required fields (by the
IM!).
Once you receive a well formed structure (should be valid against the IM) you
can validate it against archetypes.
If you already checked the instance against the IM and is valid, you'll have
all the required values (required by the IM), then when validating data (this
is the archetype validation!) and you find a {*} constraint, why the validator
should need to continue traversing the instance?
Hope that helps (or at least make sense :)
Kind regards,Pablo.
> Best regards
> Bert
>
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20140513/a0942c0b/attachment.html>
