GerdGroener (Talk | contribs)  (New page: {{Content OP Proposal Review Template |CreationDate=2009/9/8 |SubmittedBy=GerdGroener |ContentOPUnderReview=SynonymOrEquivalence (SOE) |RevisionID=5709 |Score=0 - needs major revision |Rev...)  | 
				GerdGroener (Talk | contribs)   (Article updated via HTTP request)  | 
				||
| Line 28: | Line 28: | ||
|ReviewMissing=Provide simple examples: ontology + description.  | |ReviewMissing=Provide simple examples: ontology + description.  | ||
}}  | }}  | ||
| + | <noinclude>=====10-09-2009 [[User:GerdGroener]] says:=====  | ||
| + | Reviewer Confidence: good  | ||
| + | Community Relevance: good  | ||
| + | Overall Understandability: good  | ||
| + | Clear Problem Description: good  | ||
| + | Clear Relevance and Consequences: medium</noinclude>  | ||
{{#reviewabout:Submissions:SynonymOrEquivalence (SOE)|}}
Overall suggestion (score): 0 - needs major revision
engineering, especially for less experienced developers. It focuses a common modeling problem. The proposed anti-pattern is technical sound. However, it is quite simple.
Due to the simplicity of the pattern there are
few discussion issues at WOP.design pattern somehow changes to a collection of simple modeling
primitives.Posted: 2009/9/8 Last modified: 2009/09/10
Reviewer Confidence: good Community Relevance: good Overall Understandability: good Clear Problem Description: good Clear Relevance and Consequences: medium