Comments below. > -----Original Message----- > From: Peter B. West [mailto:[EMAIL PROTECTED] > Sent: February 24, 2003 6:53 AM > To: [EMAIL PROTECTED] > Subject: Re: markers in redesign > [ SNIP ]
> It seems to me that the "hierarchy" is not the same as the area tree or > fo tree hierarchy. It is a unique hierarchy constructed by applying the > constraints on the qualifying areas. The boundary conditions impose > absolute constraints - violate one and you are out. But the other > conditions are not absolute, and they, along with actual page for > multi-page boundaries, are used to construct the hierarchy. Yes, that's my interpretation. Precisely so. It is tempting to confuse "hierarchy" for "tree". But the language of the spec in regard of markers defines a different hierarchy, one which happens to map closely to the area tree, but is highly filtered. I re-assert that in the case of this particular section of the spec, we can fall back on common sense, although normally I am loath to do so (it may sound funny to hear that, but I am a professional software developer, and I'd rather follow the letter than the spirit. That approach usually assures better code, and better specs). That means to me that in this case we use the use cases in the spec to identify what makes sense. Markers are amenable to this, as opposed to "reference-orientation", because the latter is an artificial concept, and several interpretations may apply. That means, to me, first, that we use the naming to identify qualifying areas. Two, we use "retrieve-boundary" to filter out qualifying areas. I make that distinction, because qualifying areas are defined by the naming alone. Three, we use "retrieve-position" coupled with area traits (and the traits are easy to establish) to figure out the best qualifier on the _current_ page. The thing that bugs me is, when there is no qualifying area in the "containing page" (Note to spec editors: try saying currently-formatted page), after filtering, then it becomes anarchy. It seems like user preferences based on "retrieve-position" lose all relevance. In other words, there is an elaborate set of definitions based on the current page, with a hierarchy defined by "retrieve-position", but as soon as one establishes that there is no such qualifying area on the current page, than it's just the first qualifying area one can find, moving back in the document. Arved --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
