Greetings! I tried to tweet this to @mesiru (unsuccessfully, you will see why). ;-)
Perhaps by way of example with keys at first. First key/value pair: EmployeeID = 555-33-2222 In a U.S. context, the value is obviously the employees social security number, a number that is assigned by the government. In terms of the topic maps reference model, the key, EmployeeID, is not a primitive but rather a reference to a proxy that represents a subject. In this case, a property class that is constrained to have a value XXX-XX-XXXX. The reason why that is important is that a U.S. government database, say one listing people who have paid into the system from various companies would list: SSN = 555-33-2222 as one key/value pair. We want to identify the subject represented by EmployeeID and SSN so that a future user can discover why we thought they represented the same subject. Could simply do a mapping, EmployeeID = SSN, but any future user would be guessing as to why we made that judgment. Does that help? I am about to break for the night but will pick this back up tomorrow morning. Thanks for all the hard work on Neo4j! Patrick -- View this message in context: http://neo4j-community-discussions.438527.n3.nabble.com/Key-value-pairs-in-Neo4j-tp3173724p3173724.html Sent from the Neo4J Community Discussions mailing list archive at Nabble.com. _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
