OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: redundancy in `Contains' & `Contained By' sections of archspec topics

Some topics in the architectural spec list two or more doctypes separately although they have the identical content model ('Contains' example: topicref); some list more than one doctype in the same table cell to the left of the content model ('Contains' examples: kwd, shortdesk). They should be consistent, and the latter is obviously better.
Are they automatically generated? (it seems so, given the evidently code-driven order of elements in the lists.) Is this something that is easily fixed?
Beyond that, it would be "nice" to have lists that are more easily scanned and compared by humans -- alpha order, maybe even one list of elements common to all topic types, followed by per-topic-typ lists of exceptions.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]