====== Differences ====== This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
mvf:term-in-context [2017/06/19 18:35] ebarkmeyer_thematix.com annotated D |
mvf:term-in-context [2017/06/19 18:36] ebarkmeyer_thematix.com Annotated E |
||
---|---|---|---|
Line 61: | Line 61: | ||
This would require a considerable investment and the work of specialists to develop the concept definition expressions. Most likely it would require associations motivated by business value to share the costs and returns on investment. | This would require a considerable investment and the work of specialists to develop the concept definition expressions. Most likely it would require associations motivated by business value to share the costs and returns on investment. | ||
+ | [ejb] I think this case (E) is the one case in which the idea 'context of use' is completely determined by the symbol-to-interpretation rules of the formal language. All modeling languages are formal languages, and so are OWL and CLIF and RuleML and RDF and ... In formal languages there are symbol declarations and namespaces and other "module" concepts, and there may also be axioms and definitions. Appearances of symbols in those axioms and definitions and in other declarations are interpreted as references to other declared or built-in items according to the syntax and interpretation rules of the formal language. Whether such 'schemas' or 'modules' or 'ontologies' can or should be considered 'vocabularies' in the MVF sense is a separate issue. | ||