50 likes | 137 Vues
Explore the informative CTS2 data model, its usage in understanding the SFM, directions on data details, revision scope, extensions alignment, and service granularity implications for various domains. Discover the hierarchy of concept domains, code bindings, and nuances in the Usage Context. Uncover the role of Templates and their connection to terminologies, models, and Artifact Repositories. Evaluate the functions of Models and Servers in a CTS2 setup.
E N D
CTS2 Trial use Nicolas CANU September 13th 2011
CTS2 Trial use • Lessons learnt • Next steps? STS
Lessons learnt • The informative CTS2 data model is useful • Helps to understand the SFM • Provides directions about data details • The data model should be revised • Our implementation contains certain extensions • Not 100 % sure it is aligned with “core principles” • One more possible important issue • Services granularity STS
Some extensions to the data model • Concept domains hierarchy • Binding of one code • Some concepts are linked to structured descriptions (CPM) • Our understanding of Usage Context • Realms are Jurisdictional Domains • Templates “are” Usage Contexts • Link to Templates STS
Services granularity • A Terminology Service provides information about “binding” • That implies certain “Templates Server” functions • Templates refer to models • Models specify some binding • Implies some “Models Server” functions? • Set of services around one “Artifacts Repository”? STS