Generic Function Update: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Currently, we are in the process of the introduction of a renewed vocabulary. It is a further development of the Generic Functions presented below. The new approach is aiming at giving more flexibility with and a broader usage of the vocabulary, while maintaining a proper degree of standardization. | Currently, we are in the process of the introduction of a renewed vocabulary. It is a further development of the Generic Functions presented below. The new approach is aiming at giving more flexibility with and a broader usage of the vocabulary, while maintaining a proper degree of standardization. | ||
'''Before the new vocabulary is implemented in the OIAr, it is presented here: [[Media:RFC-OIAm-vocabulary-renewal.pdf | RFC-OIAm-vocabulary-renewal.pdf]]. Everyone is invited to comment it on the [[Talk:Generic_Function_Update| 'Talk page']] of this page.''' | |||
There are a number of significant changes in the new approach: | There are a number of significant changes in the new approach: | ||
* The list of words that are present in the vocabulary is extended greatly. | * The list of words that are present in the vocabulary is extended greatly. | ||
* A new distinction is made between Data/Object Type names and Function names. The idea is to freely enable the combination of <Data/Object Type names> and <Function names>, as an expansion of the now known and documented combinations (e.g. ‘Identity Validation’). New combinations are for example ‘File Verification’ or ´Session Offloading´, et cetera. Of course, combinations should be valid and meaningful, but it is up to the OIAm practitioner to choose combinations that fit the expression needed in a model. | * A new distinction is made between Data/Object Type names and Function names. The idea is to freely enable the combination of <Data/Object Type names> and <Function names>, as an expansion of the now known and documented combinations (e.g. ‘Identity Validation’). New combinations are for example ‘File Verification’ or ´Session Offloading´, et cetera. Of course, combinations should be valid and meaningful, but it is up to the OIAm practitioner to choose combinations that fit the expression needed in a model. | ||
* Not all combinations will be documented as such, the ones that are derived from earlier development cycles of the vocabulary will be retained as examples of valid combinations and the way they can be documented | * Not all combinations will be documented as such, the ones that are derived from earlier development cycles of the vocabulary will be retained as examples of valid combinations and the way they can be documented. | ||
Revision as of 14:03, 16 May 2017
Currently, we are in the process of the introduction of a renewed vocabulary. It is a further development of the Generic Functions presented below. The new approach is aiming at giving more flexibility with and a broader usage of the vocabulary, while maintaining a proper degree of standardization.
Before the new vocabulary is implemented in the OIAr, it is presented here: RFC-OIAm-vocabulary-renewal.pdf. Everyone is invited to comment it on the 'Talk page' of this page.
There are a number of significant changes in the new approach:
- The list of words that are present in the vocabulary is extended greatly.
- A new distinction is made between Data/Object Type names and Function names. The idea is to freely enable the combination of and <Function names>, as an expansion of the now known and documented combinations (e.g. ‘Identity Validation’). New combinations are for example ‘File Verification’ or ´Session Offloading´, et cetera. Of course, combinations should be valid and meaningful, but it is up to the OIAm practitioner to choose combinations that fit the expression needed in a model.
- Not all combinations will be documented as such, the ones that are derived from earlier development cycles of the vocabulary will be retained as examples of valid combinations and the way they can be documented.