Re: The original version

From: vldm10 <vldm10_at_yahoo.com>
Date: Fri, 24 Dec 2010 09:47:47 -0800 (PST)
Message-ID: <423b745e-b223-46cb-aefb-baaa3aba1f19_at_l8g2000yqh.googlegroups.com>


Anchor Modeling solves relationships using the following explanation: “When a transaction has some property, like PEDAT-PerformanceDate in Fig. 4, it should be modeled as an anchor. It can be modeled as a tie only if the transaction has no properties.” (see Anchor Modeling, section 4.1 Modeling Core Entities and Transactions)

However no scientific explanation for the above statement is given. In contrast to Anchor Modeling, many university lectures include definitions of relationships by their attributes - often giving examples for relationships with attributes. Wikipedia also defines relationships through attributes.

In fact, Anchor Modeling cannot solve a relationship that has an attribute.
Explanation: In this case the Historized Tie would have the following form: Htie (C1, C2, ..., Cn, A, T) where A is an attribute. Here it is not clear what T is - is T time that is related to a set of anchors or is T time related to A?

Vladimir Odrljin Received on Fri Dec 24 2010 - 18:47:47 CET

Original text of this message