User Tools

Site Tools


mvf:scenarios

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
mvf:scenarios [2017/06/25 21:14]
fred.a.cummins_gmail.com [How are concepts linked across vocabularies?]
mvf:scenarios [2019/04/19 18:18] (current)
admin [Formal language formulations in vocabularies]
Line 186: Line 186:
 [fac] This represents a substantial ​ investment for specification of formulations and associated vocabularies. ​ Maybe SMIF will address this.  Once the formulation language and concepts are established,​ then the formulations for individual concepts must be specified. ​ This is not likely to be a task for typical users of the modeling tools, and there must be business value realized by the developers of these formulations. ​ [fac] This represents a substantial ​ investment for specification of formulations and associated vocabularies. ​ Maybe SMIF will address this.  Once the formulation language and concepts are established,​ then the formulations for individual concepts must be specified. ​ This is not likely to be a task for typical users of the modeling tools, and there must be business value realized by the developers of these formulations. ​
  
-[ejb] MVF only needs to allow for this.  There is no reason why an OWL model or an OCL model cannot be viewed as a "​vocabulary",​ in which the model elements are entries that have terms (model element names) and perhaps formulations in the language (in OWL EquivalentClasses or EquivalentProperties,​ in OCL def or inv).  In a similar way, an SBVR Structured English definition is a formulation in a formal language, not a natural language. In any formal language, as in any natural language, some terms are "​primitive";​ the modeler does not provide definitions. ​ So such "​vocabularies"​ can be considered to be yet another representation of a concept set in some language, and model elements in models can be linked to them.  The only additional concern for these formal languages is the inclusion of "​rules"​ or "​axioms"​ that are not definitions,​ but are treated as part of the formal language "​corpus"​.  ​+[ejb] MVF only needs to allow for this.  There is no reason why an OWL model or an OCL model cannot be viewed as a "​vocabulary",​ in which the model elements are entries that have terms (model element names) and perhaps formulations in the language (in OWL EquivalentClasses or EquivalentProperties,​ in OCL def or inv).  In a similar way, an SBVR Structured English definition is a formulation in a formal language, not a natural language. In any formal language, as in any natural language, some terms are "​primitive";​ the modeler does not provide definitions. ​ So such "​vocabularies"​ can be considered to be yet another representation of a concept set in some language, and model elements in models can be linked to them.  The only additional concern for these formal languages is the inclusion of "​rules"​ or "​axioms"​ that are not definitions,​ but are treated as part of the formal language "​corpus"​
 + 
 +[fac] The use of a formal language would have a significant impact on the MVF metamodel: each concept would have a single definition.  ​The definition specified in a formal language could be expressed in a terms from a user's selected vocabulary. ​ This is quite different from the need to express each concept definition in multiple vocabularies,​ at least for alternative natural languages, but possibly the vernaculars/​dialects of multiple communities. 
 + 
 +[fac] A formal language would also facilitate automated identification of equivalent or similar concept definitions. 
 + 
 +=== Mayo Clinic Examples and Potential Interface Discussion === 
 + 
 +This presentation includes some thoughts by Mayo of how they would like to use the APIs produced by this specification. See {{ :​mvf:​mvf_discussion-mayo-20190419.pptx |}} 
  
 [[http://​www.omgwiki.org/​mvf-rfp/​doku.php?​id=start|home]] [[http://​www.omgwiki.org/​mvf-rfp/​doku.php?​id=start|home]]
  
  
mvf/scenarios.1498425240.txt.gz · Last modified: 2017/06/25 21:14 by fred.a.cummins_gmail.com