Hi, Joel:
In fact, the scheme provides an alternative to defining values with element types.
The scheme is a specialized map.
As the collection structure in DITA, maps are well suited to defining lists of values or even hierarchies of values for a category.
Map aggregation provides a way to merge lists or hierarchies (including schemes defined by separate teams).
Schemes also give you a way to attach properties to a controlled value such as a more readable label (via the navtitle attribute or subelement).
It's quite convenient.
Hoping that clarifies,
Erik Hennum
ehennum AT us DOT ibm DOT com
"Joel Finkle" <> wrote on 01/06/2010 08:49:37 AM:
> [dita] RE: [Potential SPAM] RE: [dita] Filtering logic for
> <enumerationdef> element
>
> Making those kinds of lists extensions in the DITA types seems
> exhausting.
> I would prefer to see something in the type definitions that says, "This
> object expects authors to enter one item selected from a set of things
> of the class FOO." (or zero or one, or one to n or zero to n...)
> Then, the authoring software could be *configured* such that there is a
> list of FOOs that can be selected where needed.
