[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: 12035 Generic collation element
I am going through the remaining 1.2 features trying to make sure we understand them and their impact. As a result, I am sending out several messages, one for each feature, with various comments in an attempt to restart conversation on some of these. Has there been any discussion of this beyond http://lists.oasis-open.org/archives/dita/200703/msg00015.html I'm not sure I understand what processing expectations there are here. I gather almost any element can have a <collate-as> child element and that this is supposed to have some processing expectations. (Don't know what happens if there are more than one <collate-as> children, or if a non-<collate-as> child has, in turn, a <collate-as> child, and there are probably other such things to consider.) But then what is supposed to happen? I know what it means to have index-sort-as, because I know what it means to create and sort an index. But when you put a <collate-as> element in a title (as in the use case), how am I supposed to know what this means? There is no sort processing usually associated with titles. And, in the use case, I see the title is a child of a glossentry, and I'm betting there is some expectation that the entire glossary is supposed to have its glossentry children sorted based on the <collate-as> child element of the title child within the glossentry. But where in the DITA spec is any of this processing discussed? I see mention of sorting tables and lists, but where in the DITA spec is sorting of table and lists discussed? By the way, the time required for this is greatly understated. I could see spending weeks trying to document this after having spent weeks trying to understand all the bits and pieces and special cases involved. paul
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]