Odp:WhatIsAModelingIssue

From Odp

(Difference between revisions)
Jump to: navigation, search
Line 7: Line 7:
A superb example of this is found in the document: [http://www.w3.org/TR/swbp-classes-as-values/ Representing Classes As Property Values on the Semantic Web].
A superb example of this is found in the document: [http://www.w3.org/TR/swbp-classes-as-values/ Representing Classes As Property Values on the Semantic Web].
-
Modeling issue vary in a number of ways.
+
Two key ways that modeling issue vary are:
-
* ''Generality'' Modeling issues may be
+
* ''Domain Specificity:'' Modeling issues may be
** highly specific to narrow domains (''e.g.'' protein folding in molecular biology)
** highly specific to narrow domains (''e.g.'' protein folding in molecular biology)
** domain independent (''e.g.'' Should instances of classes be modeled as SKOS:Concept).
** domain independent (''e.g.'' Should instances of classes be modeled as SKOS:Concept).
** somewhere in between, ''i.e.'' broadly applicable in one or more fairly general domain. (e.g.  
** somewhere in between, ''i.e.'' broadly applicable in one or more fairly general domain. (e.g.  
 +
* ''How well defined:'' Modeling issues may be
 +
** very clearly defined, with competency questions and proposed solution options with tradeoffs already analyzed
 +
** very rough early thoughts from the person submitting.
 +
** somewhere in between.
 +
 +
The goal is for all modeling issues to reach a stage of being very clearly defined with one or more solutions implemented and explained. It is also very helpful to include figures.

Revision as of 23:10, 26 February 2010

Modeling Issue: A modeling issue is a question or problem that arises during the ontology engineering process. There are many kinds of issues and many ways to solve them. A modeling issue typically involves:

  • not knowing how to proceed during an ontology engineering exercise
  • identifying the specific representation requirements
  • identifying what combinations of language constructs can meet the representation requirements
  • evaluating the tradeoffs of different possible solutions.

A superb example of this is found in the document: Representing Classes As Property Values on the Semantic Web.

Two key ways that modeling issue vary are:

  • Domain Specificity: Modeling issues may be
    • highly specific to narrow domains (e.g. protein folding in molecular biology)
    • domain independent (e.g. Should instances of classes be modeled as SKOS:Concept).
    • somewhere in between, i.e. broadly applicable in one or more fairly general domain. (e.g.
  • How well defined: Modeling issues may be
    • very clearly defined, with competency questions and proposed solution options with tradeoffs already analyzed
    • very rough early thoughts from the person submitting.
    • somewhere in between.

The goal is for all modeling issues to reach a stage of being very clearly defined with one or more solutions implemented and explained. It is also very helpful to include figures.


How do I submit a modeling issue?

Post a modeling issue now.

Personal tools
Quality Committee
Content OP publishers