Reviews:KarlHammar about LicenseLinkedDataResources
Revision as of 15:16, 5 August 2013 by KarlHammar (Talk | contribs) (New page: {{Content OP Proposal Review Template |CreationDate=2013/8/5 |SubmittedBy=KarlHammar |ContentOPUnderReview=LicenseLinkedDataResources |RevisionID=11657 |Score=0 - needs major revision |Rev...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

KarlHammar about LicenseLinkedDataResources (Revision ID: 11657)

Overall suggestion (score): 0 - needs major revision

Review Summary: The pattern as introduced and described in the associated WOP 2013 short description seems relevant, and reasonably constructed, with good reuse of existing schemas, and solving an important problem. Unfortunately however, the pattern as published here in the ODP portal is lacking in several key fields, making it difficult to understand.

Reviewer Confidence: High

Problems:

Community Relevance: The problem the pattern addresses (expressing actor- or context-specific licensing details for RDF data) seems to be highly relevant in the future Semantic Web.

Relation to Best Practices: The pattern makes use of and extends established schemas in a seemingly well thought-through way.

Reusability: The pattern is domain-independent and may be used for any type of RDF data that has rights restrictions in place (i.e., it is highly reusable).

Relations to Other Patterns:

Overall Understandability: Due to the lack of many fields, the pattern is difficult to understand as here posted (i.e. without access to the WOP 2013 pattern summary paper). I would strongly urge the authors to spend some time on developing this pattern page.

Clear Problem Description: The problem that the pattern solves can be partly inferred from the intent field, but this could be expanded upon and exemplified.

Clear Relevance and Consequences: Relevance of the problem can partly be inferred from reading the bullet points under "Solution description", but this can be expanded upon and exemplified.

Clear Figures and Illustrations: My preference would be for ODP illustrations in the portal to not only illustrate the pattern structure itself, but also illustrate a usage example. This pattern is however not unique in not doing so (in fact, most don't).

Missing Information: Competency questions, consequences, scenarios, solution description..

Posted: 2013/8/5 Last modified: 2013/08/5

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