|
From: Johannes S. <top...@fr...> - 2010-02-02 22:33:57
|
Hi all, as PHPTMAPI is aligned to TMAPI I now wanted to update Construct::equals() and Construct::hashCode() according to updated semantics of equals() and hashCode() in final RC of TMAPI 2.0 [1]. Well, I am not really satisfied with this changing but missed the discussion on TMAPI mailing list. In final RC the semantics of equals() has changed from comparing the identity of TM CONSTRUCTS towards comparing the identity of (Java) OBJECTS. This is significantly different. Identity of TM constructs is "materialized" by TM system specific arbitrary identifiers [2]. IMO in federation of different topic maps from different TM systems processing of such construct identifiers must be omitted; focus is on processing the identity of subjects. To be honest: I'd like to preserve current semantics of PHPTMAPI equals(). Implementors will know how to identify PHP objects [3]. Thoughts? Best regards, Johannes [1] http://sourceforge.net/mailarchive/forum.php?thread_name=1521353800.20100113175400%40semagia.com&forum_name=tmapi-discuss [2] http://phptmapi.sourceforge.net/2.0/docs/core/Construct.html#getId [3] http://www.php.net/manual/en/language.oop5.object-comparison.php |