Bert Verhees wrote:
> The OCEAN-editor creates a C_DV_ORDINAL which is empty in the definition but
> handles the constraint in the term-defitions
> ADL-part:
> C_DV_ORDINAL <
> >
> And in the term-definitions, it looks like this (it is under the NodeID from
> the parent ELEMENT)
> ["at0004"] = <
> description = <"*">
> a1 = <"een">
> text = <"New element">
> a2 = <"twee">
> >
Hi Bert,
This seems to be the day for Archetype Editor questions ? first Pablo, and now
you :-)
How did you create that with the Ocean editor? Sure, you'll get this if you
simply add an ordinal and don't constrain it:
> C_DV_ORDINAL <
> >
But how did you get that other a1 and a2 stuff in the term definitions section?
That is not what you get if you add ordinal constraints.
If you constrain the ordinal, the Ocean editor generates this:
ELEMENT[at0001] occurrences matches {0..1} matches {
-- New element
value matches {
1|[local::at0002], -- een
2|[local::at0003] -- twee
}
}
And in the term definitions you get:
["at0001"] = <
text = <"New element">
description = <"*">
>
["at0002"] = <
text = <"een">
description = <"*">
>
["at0003"] = <
text = <"twee">
description = <"*">
>
Which is how ordinal constraints have always been expressed in archetypes, as
far as I'm aware.
Peter
