Reviews:AldoGangemi about VesselSpecies
From Odp
(Difference between revisions)
Current revision (09:12, 5 August 2009) (view source) m (Text replace - '|ReviewText=' to '|ReviewSummary=') |
|||
| Line 5: | Line 5: | ||
|RevisionID=3686 | |RevisionID=3686 | ||
|Score=2 - need major revision | |Score=2 - need major revision | ||
| - | | | + | |ReviewSummary=After Aureliano's evaluation, here you need to link vesseltypes to geartypes to species, therefore the pattern requires at least three classes, with relations between vesseltypes to geartypes, and geartypes to species respectively. |
The synthetic relation can then be instantiated by using SPARQL CONSTRUCT. | The synthetic relation can then be instantiated by using SPARQL CONSTRUCT. | ||
Alternatively, it can be generated with a SWRL rule, or by using an OWL2 alternate pattern, in which a property chain is defined (best practice). | Alternatively, it can be generated with a SWRL rule, or by using an OWL2 alternate pattern, in which a property chain is defined (best practice). | ||
}} | }} | ||
Current revision
AldoGangemi about VesselSpecies (Revision ID: 3686)
Overall suggestion (score): 2 - need major revision
Review Summary: After Aureliano's evaluation, here you need to link vesseltypes to geartypes to species, therefore the pattern requires at least three classes, with relations between vesseltypes to geartypes, and geartypes to species respectively.
The synthetic relation can then be instantiated by using SPARQL CONSTRUCT.
Alternatively, it can be generated with a SWRL rule, or by using an OWL2 alternate pattern, in which a property chain is defined (best practice).Reviewer Confidence:
Problems:
Community Relevance:
Relation to Best Practices:
Reusability:
Relations to Other Patterns:
Overall Understandability:
Clear Problem Description:
Clear Relevance and Consequences:
Clear Figures and Illustrations:
Missing Information:
Posted: 2009/3/17 Last modified: 2009/8/5
