Hide Forgot
Do dimensions need ordering to encode proximity? For example: installation precedes configuration. Does this mean that we should order the concern dimension, and place installation "before" configuration and "next to" configuration. In this way we map a temporal or dependency relationship in the users mental space with the physical display of the information, allowing them to reuse their existing mental model to locate information = intuitive. Look at some examples, and examine some output. Try to discern some patterns and rules that we can apply to try to encode the relationships between the ..... come up with a terminology for the points along an axis. The whole thing is a dimension, but what is the right term to describe the individual technology components or end-user concerns that populate that dimension - one that encodes their system-component relationship. If the system is "dimension", the component is ? I think accurate defining and naming the members of the set will help to illuminate their internal relationship.
In short: Should we order the Concerns on the front page alphabetically, or using another hierarchy, like this: Getting Started Installation Configuration etc...
This is Semantic Web.