When it comes to [[Information Mapping]] - creating [[Graphs, Charts, and Diagrams]] - frequently **position of graphical elements matters**. This is not *always* true, but frequently diagrams use some sort of **spatial encoding** technique(s). This would include absolute and relative semantics. # Absolute Position Semantics Things like [[Scatter Chart]]s are framed with top-level axes. This means that the absolute position of elements within the chart carries semantic meaning. - [[Scatter Chart]] element values are encoded by their position in the chart - [[Sequence Diagrams]] sequences flow from top-to-bottom # Relative Position Semantics Some positional semantics aren't related to the diagram as a whole, but instead how graphical elements are placed *relative to one-another*. - In the case of [[IDEF0]] the orientation of lines entering function boxes carries meaning. - [[Venn Diagram]]s are all about the position of elements with respect to the placement of the category-defining circles # No Positional Semantics For completeness, here are some examples of diagrams for which position doesn't *really* play a role. - [[Mind Mapping|Mind Maps]] - lines connect elements that are related, but aside from that the elements can really be anywhere - [[Internal Block Diagram]]s - aside from the position of *ports* on components, there really isn't any spatial encoding in IBDs **** # More ## Source - [[Myself]]