Reviews:JoseEmilioLabraGayo about LicenseLinkedDataResources

From Odp

Revision as of 15:13, 8 August 2013 by JoseEmilioLabraGayo (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search

JoseEmilioLabraGayo about LicenseLinkedDataResources (Revision ID: 11657)

Overall suggestion (score): 1 - needs minor revision

Review Summary: The authors propose a pattern to assert license issues based on n-ary relations between license, action, agent, resource and condition. The accompanying paper contains a more detailed introduction than the web page. Although the authors don't mention if the pattern has been employed in some real scenarios.
Reviewer Confidence: High
Problems: The authors declare that they relate license, author, agent, resource and condition. It is not clear if condition is the same as "cc:Requirement". If it is, I would advise to clarify or to define a property "lldr:Condition".

Although reusing existing properties can be a good practice, if those properties have different meanings, it may be better to define new properties with a more specific meaning and relate the new properties to the others.

It is not clear if the authors separate instances and classes. It is also not clear the granularity of their proposal. The goal is to add licensing information to a statement (in the PDF document they use a partial statement about google stimated stock price) or about a dataset, or both.

The submission does not contain OWL examples. The examples in the PDF paper are very simple.
Community Relevance: The pattern can be applied to any context.
Relation to Best Practices: The pattern is related with the work on Provenance. The final goal is how to add metadata information about a dataset. Some information that would be complimentary is the time period in which that license information is valid.
Reusability: I think the proposed ontology/pattern is necessary and although this proposal may still need some work, it has a lot of potential for the future of linked data adoption.
Relations to Other Patterns: As I said, the pattern is related with the work that is being done in defining provenance. It is also related with n-ary relations.
Overall Understandability: The pattern lacks some fields in the description that could improve its understandability. A good set of examples and use scenarios could help its adoption.
Clear Problem Description: The problem is clearly described.
Clear Relevance and Consequences: This pattern or some variation of this pattern should be adopted in order for the linked data project to success.
Clear Figures and Illustrations: The figures are clear. Although, it would be interesting that the authors had provided some good example.
Missing Information: There is a lack of several fields in the description, specially the examples field.

Posted: 2013/8/8 Last modified: 2013/8/8

All reviews | Add a comment at the bottom of this page
Personal tools
Quality Committee
Content OP publishers