VCOI WG Wiki

User Tools

Site Tools

Trace:
start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
start [2021/07/19 16:19]
admin [Details] 		start [2021/10/04 16:28] (current)
admin
Line 8: Line 8:
 The aim of this working group is to come up with a common, reusable method for OMG Task Forces and SIGs to use when developing vocabularies.  The aim of this working group is to come up with a common, reusable method for OMG Task Forces and SIGs to use when developing vocabularies. 
  
-==== Activities and Components ====+==== Status ====
  
-=== Overview: ===+This {{ ::20210928_vcoi_update.pptx |Sept 2021 Update}} sets out the basic proposition for TCs and the current status. 
  
-== VCoI Deliverables and Status ==+==== Overview ====
  
-These slides filed at OMG as {{ ::finance2021-06-04--vcoi_deliverables_and_status.pptx |finance/2021-06-04}} constitute the most recent high level outline of each of the various parts that make up the overall VCoI set of parts, and the 'calculus' for context-specific vocabulary linkage to concept models. +These slides from June 2021 filed at OMG as {{ ::finance2021-06-04--vcoi_deliverables_and_status.pptx |finance/2021-06-04}} constitute the most recent high level outline of each of the various parts that make up the overall VCoI set of parts, and the 'calculus' for context-specific vocabulary linkage to concept models. 
  
-== Deliverables and Activities ==+=== Activities per Deliverable ===
  
-  * Concepts Re-use Calculus +See the Activities heading at the foot of this page for links through to work in progress on each activity. 
-  * Content requirements +
-  * Metamodel +
-  * Annotation requirements +
-  * Output formats (presentation) +
-  * Context Ontology +
-  * Process+
  
 +==== Components ====
  
-=== Proposition / Calculus ===+=== 1. Concepts Re-use Calculus ===
  
 The core proposition is that terms are defined in some context - specifically in this case the context of that Task Force or SIG. Further contextual treatment is merited when a TF or SIG decides to use a definition sourced from elsewhere, since then the context of that external definition needs to be represented.  The core proposition is that terms are defined in some context - specifically in this case the context of that Task Force or SIG. Further contextual treatment is merited when a TF or SIG decides to use a definition sourced from elsewhere, since then the context of that external definition needs to be represented. 
Line 43: Line 38:
 Concepts are considered as being made available as a library of concepts. Meaning (for a term) does NOT rely upon the written definition given for the term, but rather the written definition reflects and is derived from the Concept Library. Concepts are considered as being made available as a library of concepts. Meaning (for a term) does NOT rely upon the written definition given for the term, but rather the written definition reflects and is derived from the Concept Library.
  
-=== Content requirements ===+=== 2. Content requirements ===
  
 This is still being explored but will likely consist of  This is still being explored but will likely consist of 
Line 53: Line 48:
 TFs and SIGs may develop their own ontologies for concepts that they choose to define for themselves. Concepts from other sources may already be in the form of ontologies or may be in less ontologically mature formats such as dictionaries or vocabularies.  TFs and SIGs may develop their own ontologies for concepts that they choose to define for themselves. Concepts from other sources may already be in the form of ontologies or may be in less ontologically mature formats such as dictionaries or vocabularies. 
  
-== Representation of Context == +== 2.1 Representation of Context == 
  
 Once the Context ontology is developed the next challenge will be how to represent that in Term / Definition representations. Recall that: Once the Context ontology is developed the next challenge will be how to represent that in Term / Definition representations. Recall that:
Line 67: Line 62:
 That needs to be able to be generated from the Context ontology and its use as the linkage between Term and Concept  needs to be maintained in the underlying machinery that supports all this.  That needs to be able to be generated from the Context ontology and its use as the linkage between Term and Concept  needs to be maintained in the underlying machinery that supports all this. 
  
-== Task Force SME Feedback ==+== 2.2 Task Force SME Feedback ==
  
 Another output of applying the methodology when it exists, is the ability to frame questions for the owning TF or SIG, including: Another output of applying the methodology when it exists, is the ability to frame questions for the owning TF or SIG, including:
Line 78: Line 73:
  
  
-=== Metamodel ===+=== 3. Metamodel ===
  
 This is not just about what the overall metamodel should be (since we intend to use existing metamodels such as SKOS and MVF), but about how the various pieces of any of the available standards metamodels are to be used under the VCoI framework.  This is not just about what the overall metamodel should be (since we intend to use existing metamodels such as SKOS and MVF), but about how the various pieces of any of the available standards metamodels are to be used under the VCoI framework. 
  
-== Existing Models Annotation ==+== 3.1 Existing Models Annotation ==
  
 A further deliverable made possible if we use the MVF emerging standard is the ability to annotate models with links to concept and vocabulary.  A further deliverable made possible if we use the MVF emerging standard is the ability to annotate models with links to concept and vocabulary. 
  
  
-=== Annotation requirements ===+=== 4. Annotation requirements ===
  
 This is the 'Annotations Wishlist'. Work in progress.  This is the 'Annotations Wishlist'. Work in progress. 
Line 97: Line 92:
  
  
-=== Output formats (presentation) ===+=== 5. Output formats (presentation) ===
  
 The deliverables for anyone applying the desired methodology are: The deliverables for anyone applying the desired methodology are:
Line 105: Line 100:
   * References   * References
  
-== Formats ==+== 5.1 Formats ==
  
 These may take one or more physical forms: These may take one or more physical forms:
Line 113: Line 108:
   * Document inserts in the style of the OMG Specification template, for Terms, Abbreviations, References   * Document inserts in the style of the OMG Specification template, for Terms, Abbreviations, References
  
-=== Context Ontology ===+=== 6. Context Ontology === 
 + 
 +== Ontologies Overview ==
 There are two kinds of ontology that may be in play overall. These are referred to in VCoI under the following distinctions:  There are two kinds of ontology that may be in play overall. These are referred to in VCoI under the following distinctions: 
  
Line 121: Line 118:
   * Ontology (2): The conceptual resource maintained by the individual TF or SIG   * Ontology (2): The conceptual resource maintained by the individual TF or SIG
  
-== Ontology (1): VCoI Context Ontology ==+== 6.1 Ontology (1): VCoI Context Ontology ==
  
 As defined in the VCoI Calculus, the notion of 'Context' is simply a nexus or combination of concepts. Often summarized as 'Who, What, When, Where, Why, hoW' (the Ws), these are really a simple reminder list for what are basically concepts, and therefore capable of being represented in a suitable concept ontology. The Ws effectively represent a simplistic Top Level Ontology (TLO).  As defined in the VCoI Calculus, the notion of 'Context' is simply a nexus or combination of concepts. Often summarized as 'Who, What, When, Where, Why, hoW' (the Ws), these are really a simple reminder list for what are basically concepts, and therefore capable of being represented in a suitable concept ontology. The Ws effectively represent a simplistic Top Level Ontology (TLO). 
Line 142: Line 139:
  
  
-== Ontology (2) Sub-group Concept Ontology ==+== 6.2 Ontology (2) Sub-group Concept Ontology ==
  
 It is up to each TF or SIG (Collectively, Sub Group) to determine what form their concept model takes. We anticipate that many SGs would start with a general taxonomy, refining this in stages from a broad business taxonomy (having a range of different organizing relationships) to a generalization-based taxonomy, and then enhancing that taxonomy by the addition of properties to derive an ontology at the concept level.  It is up to each TF or SIG (Collectively, Sub Group) to determine what form their concept model takes. We anticipate that many SGs would start with a general taxonomy, refining this in stages from a broad business taxonomy (having a range of different organizing relationships) to a generalization-based taxonomy, and then enhancing that taxonomy by the addition of properties to derive an ontology at the concept level. 
Line 148: Line 145:
 Note that the kind of concept ontology that is suitable for this usage is unlikely to be anything like a conventional OWL-based application ontology, though SGs may elect to serialize their ontology in OWL, and in some cases may even elect to use a use case-driven OWL operational ontology as a stand-in for their domain concept ontology. We don't recommend that but it's the choice of each individual TF or SIG.  Note that the kind of concept ontology that is suitable for this usage is unlikely to be anything like a conventional OWL-based application ontology, though SGs may elect to serialize their ontology in OWL, and in some cases may even elect to use a use case-driven OWL operational ontology as a stand-in for their domain concept ontology. We don't recommend that but it's the choice of each individual TF or SIG. 
  
-=== Process ===+=== 7. Process ===
  
 In order to develop something that can be used by OMG SGs, there are two aspects to what needs to be delivered or recommended to SGs: In order to develop something that can be used by OMG SGs, there are two aspects to what needs to be delivered or recommended to SGs:
Line 157: Line 154:
 This part of the work focuses on sketching out a basic process workflow that SGs can adopt and extend. This part of the work focuses on sketching out a basic process workflow that SGs can adopt and extend.
  
-==== Details ====+==== Component Details ====
  
 These deliverables and activities are expanded on in the pages below: These deliverables and activities are expanded on in the pages below:
  
-  * Concepts Re-use Calculus+  * **1. Concepts Re-use Calculus**
     * [[Context Treatment]] - Given all the above, how should the 'context' be treated for     * [[Context Treatment]] - Given all the above, how should the 'context' be treated for
     * Word usage (This word W means concept C in the context of this TF or SIG)     * Word usage (This word W means concept C in the context of this TF or SIG)
     * Concept - origin context in the case of externally sourced concepts     * Concept - origin context in the case of externally sourced concepts
-  * Content requirements+  * **2. Content requirements**
     * [[SMEFeedback]] - Considerations and pointers  in gathering domain knowledge by TF or SIG     * [[SMEFeedback]] - Considerations and pointers  in gathering domain knowledge by TF or SIG
     * [[Definitions]] - form of definitions and how to derive these from the concept resource (ontology)     * [[Definitions]] - form of definitions and how to derive these from the concept resource (ontology)
     * [[LocalOntologies]] - Formal reference ontologies for concept defined by the TF or SIG     * [[LocalOntologies]] - Formal reference ontologies for concept defined by the TF or SIG
-  * Metamodel+  * **3. Metamodel**
     * [[Architecture]] - Tools and formats to maintain the terminology and vocabulary of a Task Force or SIG     * [[Architecture]] - Tools and formats to maintain the terminology and vocabulary of a Task Force or SIG
-  * Annotation requirements +  * **4. Annotation requirements** 
-  * Output Formats+  * **5. Output Formats**
     * [[OutputFormats]] - desired form of outputs for the terminology and concepts     * [[OutputFormats]] - desired form of outputs for the terminology and concepts
-  * Context Ontology +  * **6. Context Ontology** 
-  * Process+  * **7. Process** 
 + 
 + 
 +==== Activities ====
  
 +  * **1. Concepts Re-use Calculus**
 +    * Mostly figured out and documented
 +  * **2. Content requirements**
 +    * Considerations and pointers in gathering domain knowledge by TF or SIG - to be done
 +    * Definitions - form of definitions and how to derive these from the concept resource (ontology) - TBD
 +    * Guidelines for Formal reference ontologies for concept defined by the TF or SIG - TBD / in progress
 +  * **3. Metamodel**
 +    * Tools and formats to maintain the terminology and vocabulary of a Task Force or SIG - In progress, see [[Architecture]] page as above
 +  * **4. Annotation requirements**
 +    * In progress [[AnnotationsWishlist]]
 +  * **5. Output Formats**
 +    * Mostly determined (specification for what the underlying 'machinery' needs to emit)
 +    * New formats may be identified from time to time
 +    * Expect to liaise with others on e.g. wiki glossary pages
 +  * **6. Context Ontology**
 +    * In progress July 2021
 +  * **7. Process**
 +    * Some initial work May / June 2021, to be completed
  
 ==== Meeting Notes ==== ==== Meeting Notes ====
start.1626725975.txt.gz · Last modified: 2021/07/19 16:19 by admin

Page Tools

OMG Home Logos and Trademarks Become a Member Become a Sponsor Upcoming TC Meeting TOP