Thanks, but these descriptions aren't very complete. What's the
difference, for example, between collection-type="unordered" and
collection-type="choice"? Right now, we're trying to figure out how to
render these things by running samples through the Open Toolkit, but
that is sort of putting an implementation before the standard. It seems
that we are still missing the original intent or meaning behind each of
these possible values (unordered, choice, sequence, family).
Chris
Don Day wrote:
>It's there, in a link to the %topicref-atts; group of attributes:
>http://docs.oasis-open.org/dita/v1.0/langspec/topicref-atts.html
>
>Granted, this description is terse. Michael provided more detail that you
>can apply to implementation behavior in the map attribute descriptions
>here:
>http://docs.oasis-open.org/dita/v1.0/archspec/dita_spec_23_common.html .
>The DITA Open Toolkit should demonstrate these processing-based behaviors.
>
>
>
