mvf:extending_a_vocabulary_for_a_canonical_model
====== Differences ====== This shows you the differences between two versions of the page.
| Next revision | Previous revision Next revision Both sides next revision | ||
|
mvf:extending_a_vocabulary_for_a_canonical_model [2017/09/15 16:51] evan.wallace_nist.gov created |
mvf:extending_a_vocabulary_for_a_canonical_model [2017/09/15 17:45] evan.wallace_nist.gov |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Extending a vocabulary for a revision of a canonical model ====== | ====== Extending a vocabulary for a revision of a canonical model ====== | ||
| - | In this use case, a community has developed a "canonical data model" that provides a reference format for sharing data as a basis for sharing data between partners or applications. The developers of this model are extending it to support new concepts and business processes. They collect references for terms and definitions for the concepts being added to the canonical model. Some of the sources have machine readable vocabularies available in a SKOS rdf file. Others have only text or human readable web content. The model developers choose terms and definitions to add to the model dictionary from a number of sources and would like to have references to text sources and links to machine readable sources included in the vocabulary. | + | In this use case, a community has developed a "canonical data model" that provides a reference format as a basis for sharing data between partners or applications. The developers of this model are extending it to support new concepts and business processes. They collect references for terms and definitions for the new concepts being added to the canonical model. Some of the sources have machine readable vocabularies available via SKOS rdf file. Others have only text or human readable web content. The model developers choose terms and definitions to add to the Model Dictionary from a number of sources and would like to have references to text sources and links to machine readable sources included in the vocabulary. |
| ===== 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 and linking. | + | * 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 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) | ||
| + | ===== Terms and assumptions ===== | ||
| + | * The Model Dictionary is the MVFDictionary linking elements in the canonical model with Terms and Definitions to display for its model elements. | ||
| + | * A Model Vocabulary contains the Terms and Definitions used for the Model Dictionary and edited by the community maintaining 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. | ||
| + | |||
| + | //Depending on the design of the MVF metamodel, a Model Vocabulary may be a separate information artifact or just a view of various other vocabularies referenced by the MVF Dictionary.// | ||
mvf/extending_a_vocabulary_for_a_canonical_model.txt ยท Last modified: 2019/08/23 13:57 by evan.wallace_nist.gov
Page Tools
