Last discussion about this issue.

======================================================================
Shane Bryzak: i think it's ok if we extend the @AttributeProperty annotation08:05:21 PM
Shane Bryzak: so we have @IdentityStereotype(ROLE) on the class08:05:43 PM
Shane Bryzak: then @AttributeProperty(stereotypeProperty = ROLE_NAME)08:06:01 PM
Shane Bryzak: on the property field or method08:06:09 PM
Pedro Igor: I see, actually, I did that after our last discussion ...08:06:32 PM
Pedro Igor: but I really don't liked how we specify the property08:06:42 PM
Pedro Igor: i think we're complicating ... i single annotation should do the trick ...08:07:00 PM
Shane Bryzak: we shouldn't use a string value, it's not typesafe08:07:08 PM
Pedro Igor: yeah, i know ..08:07:16 PM
Shane Bryzak: and who knows, we might introduce a stereotype in the future for which there are multiple properties required08:07:43 PM
Shane Bryzak: so a single annotation wouldn't be future-proof08:07:51 PM
Pedro Igor: actually, we just create a new one ... 08:08:11 PM
Pedro Igor: but i understand your point ..08:08:17 PM
Pedro Igor: and I'm half way to make it working ..08:08:26 PM
Pedro Igor: considering that "gaps" that i found and we discussed yesterday ..08:08:46 PM
Shane Bryzak: yeah i still don't have an elegant solution for the relationship types...08:09:31 PM
Pedro Igor: which is common for whatever solution we define ...08:09:34 PM
Pedro Igor: ok08:09:37 PM
Shane Bryzak: i see why the idea of interfaces is appealing to you08:09:50 PM
Shane Bryzak: actually you know what..08:10:25 PM
Pedro Igor: :)08:10:31 PM
Shane Bryzak: we could use the stereotypes for the relationship types also08:10:41 PM
Shane Bryzak: @RelationshipStereotype(APPLICATION_ROLE)08:10:54 PM
Pedro Igor: yeah08:11:11 PM
Shane Bryzak: that would solve the gaps issue, and be consistent with the other changes08:11:44 PM
Pedro Igor: and also define which property is related with the role ?08:11:46 PM
Shane Bryzak: right08:11:53 PM
Shane Bryzak: which means i'm no longer happy with using @AttributeProperty...08:12:14 PM
Shane Bryzak: hmm maybe we need a new annotation for that08:12:23 PM
Pedro Igor: we can use that StereotypeProperty that you suggested in both cases ?08:12:58 PM
Shane Bryzak: @RelationshipProperty(stereotype = ROLE)08:13:18 PM
Pedro Igor: so we define a big enum with stereotype properties for identity types and relationships ?08:13:20 PM
Shane Bryzak: either a single enum or two separate enums08:13:42 PM
Shane Bryzak: if two enums, i think we need two annotations08:13:50 PM
Shane Bryzak: maybe @StereotypeProperty is ok08:14:05 PM
Pedro Igor: yeah08:14:07 PM
Shane Bryzak: actually i like @StereotypeProperty, it's abstract enough to make sense 08:14:33 PM
Pedro Igor: yeah08:14:37 PM
Pedro Igor: so ..08:14:39 PM
Shane Bryzak: so perhaps one big enum08:14:47 PM
Shane Bryzak: @StereotypeProperty(RELATIONSHIP_ROLE)08:15:03 PM
Shane Bryzak: @StereotypeProperty(IDENTITY_LOGIN_NAME)
=================================================================================