looking at it again, I missed the minOccurs=0 when translating it
to a simpler grammar form. Need a marker for optional.
Not quite sure why DV_ORDERED has all its extra fields as optional,
since you could convert any DV_VALUE to DV_ORDERED type, and the type
would be meaningless ( it's becomes labelled as DV_ORDERED, but doesn't
contain any information to show why it is ordered). It really should be
DV_RANGED , as ordered usually means that instances can be sorted into
an order, and DV_QUANTIFIED is a misnomer as well, as it has accuracy
fields, and being accurate and quantified don't normally imply each
other. Maybe DV_ACCURACY_GIVEN , and remove the minOccurs ? In fact,
all the types where the extra fields are all minOccurs =0 shouldn't be
in an inheritance heirarchy, they should be optional components of
minOccurs = 0, with mandatory values, in the classes that inherit from
them currently. e.g. the heirarchy should be refactored to
DV_ABSTRACT <-- DV_POSSIBLY_RANGED_POSSIBLY_ACCURACY_GIVEN
- ACCURACY minOccurs=0
- RANGES minOccurs =0
<-- DV_QUANTITY
<-- DV_COUNT
Maybe it's a good thing openehr hasn't been proliferated yet,
otherwise we'd be stuck with some basic flaws.
On Wed, 2006-11-22 at 12:30 +1100, Andrew Patterson wrote:
> > It seems obvious they did not run their xml translation
> > through a verifier, which should have been easy.
>
> Syan, computer people have been using mutually
> recursive data types for many years. I'm not sure what
> the problem is here? You are correct that if the
> mutual type reference elements were compulsory, then it
> would be impossible to construct a serialized
> instance - but the references are all optional and
> hence the recursion stops when we have no more
> data to fill in...
>
> attached is an (meaningless) instance that validates against
> this xsd using xerces
>
> Andrew
> _______________________________________________
> Gpcg_talk mailing list
> [email protected]
> http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
