mvf:issues
====== Differences ====== This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
mvf:issues [2017/06/21 18:27] fred.a.cummins_gmail.com [Representation of Concept] |
mvf:issues [2018/03/02 14:06] (current) admin [Use of SKOS] |
||
|---|---|---|---|
| Line 22: | Line 22: | ||
| - | ==== Linking model elements to concepts ==== | + | ==== What a model element links to -- the "MVF Entry" ==== |
| - | What does a model element link to? Some "concept" object? Multiple terms/entries in different vocabularies? | + | What exactly does a model element link to? A concept? a vocabulary entry? Something else? |
| - | * Proposal: Placeholder ‘concept’ object lives somewhere. It is linked to entries in multiple vocabularies. Model elements link to it. | + | We agreed that a model element links to an object temporarily called an MVF Entry. What an MVF Entry actually is is discussed in detail on the [[mvf:MVFentry|MVF Entry page]]. |
| - | + | ||
| - | Where does it live? Is it in a separate resource from all vocabularies? | + | |
| - | + | ||
| - | Is it just an IRI that all the related language vocabularies agree to use? | + | |
| - | If so, then the link from the model element is the IRI, but how does the modeling tool find the language-based vocabulary entries? | + | |
| - | + | ||
| - | * Proposal: The model element contains the links to all of the corresponding vocabulary entries. The idea that they represent the same concept is implied. Effectively, the model element is the cluster point and the reference form of the concept. | + | |
| - | + | ||
| - | Objection (Evan): The business concept exists without the model. The model element should not be the center concept. Model element to concept relationships are also many-to-many. Different models may have links to different vocabulary entries (in different languages) for the same concept. How would the modeling tool or the user find translations of a business term that are only linked by other models? | + | |
| - | + | ||
| - | * Proposal: A concept is a vocabulary entry, or something in a vocabulary that entries link to. These entries can be linked to each other across vocabularies, or in a separate resource (a la Linked Open Data). The model element can point to any of those resources as a starting point. | + | |
| - | + | ||
| - | The effect is that the model element points to one element of some kind of linked list. How does one add to the list? Is it circular? And how easy is that to maintain, if multiple tools are involved? | + | |
| ==== Nature of a vocabulary "entry" ==== | ==== Nature of a vocabulary "entry" ==== | ||
| Line 120: | Line 107: | ||
| [Elisa] Thematix wants to add support for a much richer subset of ISO 1087-1, because we have found it useful in dealing with the conflicts and nuances in the finance industry. So we would want to specify that model, which goes well beyond SKOS, but MVF should treat most of it as an optional extension to the basic support model. | [Elisa] Thematix wants to add support for a much richer subset of ISO 1087-1, because we have found it useful in dealing with the conflicts and nuances in the finance industry. So we would want to specify that model, which goes well beyond SKOS, but MVF should treat most of it as an optional extension to the basic support model. | ||
| + | |||
| + | [Elisa] In addition to SKOS, we should review the lemon and babelnet ontologies for their approach to representation of multilingual synsets, and potentially map MVF to those ontologies after integrating any relevant concepts or properties that we don't already have. See http://www.lemon-model.net/lemon# for the Lemon ontology and http://babelnet.org/model/babelnet# for the babelnet vocabulary. | ||
mvf/issues.1498084051.txt.gz · Last modified: 2017/06/21 18:27 by fred.a.cummins_gmail.com
Page Tools
