Odp:WhatIsAModelingIssue

From Odp

(Difference between revisions)
Jump to: navigation, search
(New page: How do I submit a modeling issue? Post a modeling issue A modeling issue is a question or problem that aris...)
Current revision (03:52, 3 March 2010) (view source)
 
(16 intermediate revisions not shown.)
Line 1: Line 1:
-
[[Submissions:HowDoISubmitAModelllingIssue| How do I submit a modeling issue?]]
+
''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:
-
[[Community:PostModelingIssue| Post a modeling issue]]
+
* 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: [http://www.w3.org/TR/swbp-classes-as-values/ Representing Classes As Property Values on the Semantic Web].
-
A modeling issue is a question or problem that arises during the ontology engineering process.  If you want help in solving a modeling issue, or you wish to contribute an issue you are aware of with a solution, please The idea is Modeling issues are linked to ontology patterns that solve a defined problem.
 
-
This area is dedicated to the ODP Community discussions.
+
Two key ways that modeling issues vary are:
-
If you are designing an ontology and have met a modeling issue, you can discuss it here and find help to solve it.  
+
* ''Domain Specificity:'' Modeling issues may be
-
Below you can find a list of the modeling issues that have been posted.  
+
** highly specific to narrow domains (''e.g.'' protein folding in molecular biology)
-
Each of them is associated with a discussion page where other users can help finding a solution.
+
** 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 domains.
-
[[Community:PostModelingIssue| Post a modeling issue]]
+
* ''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.
 +
 
 +
 
 +
''Actions:''
 +
* [[Community:Main| View or Contribute to modeling issues already posted]]
 +
* [[Submissions:HowDoISubmitAModelllingIssue| How do I Post or Contribute to a modeling issue?]]
 +
* [[Community:PostModelingIssue| Post a modeling issue now.]]
{{Info tip
{{Info tip
-
| Before posting your modeling issue look at the list below, maybe somebody else had a similar problem
+
|  
 +
The goal is for all modeling issues to:
 +
* reach a stage of being very clearly defined
 +
* have one or more implemented solutions linked to design patterns
 +
* be clearly explained so others can benefit from your efforts
 +
* be illustrated by at least one figure.
}}
}}

Current revision

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 issues 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 domains.
  • 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.


Actions:


The goal is for all modeling issues to:

  • reach a stage of being very clearly defined
  • have one or more implemented solutions linked to design patterns
  • be clearly explained so others can benefit from your efforts
  • be illustrated by at least one figure.
Personal tools
Quality Committee
Content OP publishers