Reviews:BorisVillaz�n-Terrazas about Standard Enforcer Pattern Revision as of 15:52, 30 August 2012 by {{| (Talk | contribs)}} (New page: {{Content OP Proposal Review Template |CreationDate=2012/8/30 |SubmittedBy=BorisVillazón-Terrazas |ContentOPUnderReview=Standard Enforcer Pattern |RevisionID=11210 |Score=1 - needs minor ...) (diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

{{#reviewabout:Submissions:Standard Enforcer Pattern|}}

BorisVillazón-Terrazas about Standard Enforcer Pattern (Revision ID: Enforcer Pattern?oldid=11210 11210)

Overall suggestion (score): 1 - needs minor revision

Review Summary: The proposed pattern describes modelling guidelines to describe a standard and the process that enforce the standard.

Reviewer Confidence: Medium

Problems: The author has to explain, in a better way, the modelling principles of the Figure 1.

One minor comment, regarding the OWL file. Probably this is for all patterns.

The community is adopting TURTLE as human-readable syntax for RDF, so I would prefer to have the patterns in TURTLE instead of RDF/XML.

Community Relevance: The pattern is relevant

Relation to Best Practices: I would need more use cases for this pattern.

Reusability: The pattern is reusable

Relations to Other Patterns:

Overall Understandability: The pattern needs to be explained in a better way. Also the author needs to improve the description of the uses cases.

Clear Problem Description: The problem is clearly described.

Clear Relevance and Consequences:

Clear Figures and Illustrations:

Missing Information: Use case/Scenario

Posted: 2012/8/30 Last modified: 2012/08/30

All reviews | Add a comment at the bottom of this page