The document provides detailed explanations around change control and versioning requirements. At the same time, it is relatively sparse in terms of how to represent semantics in a common language, which is key issue at stake. Other than requiring each term has a parent, Tinkar does not appear to provide the essentials of a grammar for defining concepts, a standard set of relationships, or ways to create new concepts from existing concepts. As a proposed standardized knowledge architecture for terminology, these omissions are surprising. If Tinkar is primarily about change management, and outsources the representation of semantics, it may not be a sufficient framework to achieve the stated objectives of meaningful data analysis and increased semantic interoperability. Change management and versioning are relatively well understood and the parts of this document addressing those topic do not break significant new ground.

Perhaps the fault is my own lack of understanding, or in the construct of the document, rather than the underlying ideas put forth in Tinkar.