mvf:extending_a_vocabulary_for_a_canonical_model
====== Differences ====== This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
mvf:extending_a_vocabulary_for_a_canonical_model [2019/07/26 14:01] evan.wallace_nist.gov [Terms and assumptions] removed old note about dictionary and vocabulary relationship that has been resolved |
mvf:extending_a_vocabulary_for_a_canonical_model [2019/08/23 13:57] evan.wallace_nist.gov added partial narrative detailing the sequence for the story |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== MVF Requirements to support this use case ===== | ===== MVF Requirements to support this use case ===== | ||
| - | * Ability to have a Model Dictionary with its supporting Vocabularies and one or more Domain Vocabularies //loaded// and //active// in a //workspace// for browsing, searching, and linking. | + | * Ability to have a Model Dictionary with its supporting Vocabularies as well as one or more Domain Vocabularies //loaded// and //active// in a //workspace// for browsing, searching, and linking. |
| * Ability to link Model Dictionary entries and/or Model Vocabulary entries to Domain Vocabulary entries. | * Ability to link Model Dictionary entries and/or Model Vocabulary entries to Domain Vocabulary entries. | ||
| * Ability to annotate entries with references to their source (text or machine readable) | * Ability to annotate entries with references to their source (text or machine readable) | ||
| Line 12: | Line 12: | ||
| * Domain Vocabularies are resources imported from some machine readable form to provide reference terms and definitions for domain concepts relevant to the model. | * Domain Vocabularies are resources imported from some machine readable form to provide reference terms and definitions for domain concepts relevant to the model. | ||
| + | ===== Narrative ===== | ||
| + | * The group developing the model is expanding the scope of their standard. Thus new concepts will be added to the model that will need appropriate terms and definitions. | ||
| + | * A standard developer (MVF user) researches the new area and finds that concepts in the extension to the standard are defined in a mix of machine readable reference vocabularies and more traditional text references (papers or web links). | ||
| + | * The user imports the machine readable vocabulary file containing the terms and definitions that he wants into his MVF facility. This creates a new MVFDictionary for all the concepts in the reference vocabulary and one or more Vocabularies in the Workspace. [there should probably be a parameters to the import operation that allow the user to specify which languages will be supported by the import and thus what vocabularies will be created.][There is a question as to whether or not to create a separate MVFDictionary for the reference vocabularies imported or just use the model MVFDictionary.] | ||
| + | * For each concept, the user will indicate the VocabularyEntry to add to the model Dictionary and have the tool add a corresponding MVFEntry to the reference MVFDictionary and to the model vocabularies. The MVFEntry would have the same externalReference as the entry in the reference dictionary. | ||
mvf/extending_a_vocabulary_for_a_canonical_model.txt ยท Last modified: 2019/08/23 13:57 by evan.wallace_nist.gov
Page Tools
