tag:blogger.com,1999:blog-34366572.post4925415096283593177..comments2023-09-22T22:08:35.286+10:00Comments on Semantic DataBase: Uniqueness of EntitiesSamir Kumar Mishrahttp://www.blogger.com/profile/14088080259482491311noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-34366572.post-47217744279931578982008-01-28T19:05:00.000+10:002008-01-28T19:05:00.000+10:00Thanks Simon and Venkk,Yes the context or usages o...Thanks Simon and Venkk,<BR/><BR/>Yes the context or usages of an entity does play a big role in deciding what attribute is unique. In this post my attempt is to identify a pattern to decide what could identify the object as unique. So far I've found a system generated ID as one of the option. But there are many other options which is equally good.Samir Kumar Mishrahttps://www.blogger.com/profile/14088080259482491311noreply@blogger.comtag:blogger.com,1999:blog-34366572.post-82502725433406633012008-01-28T01:55:00.000+10:002008-01-28T01:55:00.000+10:00In my view both are necessary. Its helpful to ide...In my view both are necessary. Its helpful to identify a object uniquely and also based uniqueness on its attribute(s). Depending on application requirements the developer can choose to leverage either one of them.Anonymoushttps://www.blogger.com/profile/17247438550701830784noreply@blogger.comtag:blogger.com,1999:blog-34366572.post-30945842149250736592008-01-08T23:18:00.000+10:002008-01-08T23:18:00.000+10:00You should probably check out Kripke's Naming and ...You should probably check out Kripke's <A HREF="http://en.wikipedia.org/wiki/Naming_and_Necessity" REL="nofollow">Naming and Necessity</A>. As I recall, it turns out that treating names as simple attributes is problematic.Anonymousnoreply@blogger.com