Article 1

取自 NKOS

Harold R Solbrig, Christopher G Chute (M.D., Dr. P.H., Division of Biomedical Informatics, Mayo Clinic) A Common Terminology Services (CTS) Back-end to Protégé，

目的：

Purpose of the Project

1. Use Protégé to create an interface between terminologyand the information model
2. Use Protégé to extend standard terminologies and (potentially) author new content.

术语服务：

• An integrated collection of terms, definitions, annotations, and relationships
• Defines the specialized language of a discipline or subject area

术语（词表）和本体的区别

• Terminology -Definethe language / tokens used in a given domain
• Ontology -Describes domain knowledge in a generic way and provides understanding of a domain*

信息模型（Information Model)

• Describes what information is required to accomplish a particular task or process
• Consists of named collections of data elements and their relationships
• Typically includes definitions of each of the elements, how they are used, possible values (at least on a conceptual level)

术语（词表）与信息模型的关系

• There can be many information models that reference the same terminology
• It is the shared terminological references that allows information to be searched, compared and aggregated

由于有这种多对多（？）的关系，给术语服务带来了复杂性。

术语间的关系

• 类class-槽slot-值possible values
• 槽即属性
• MS可以用RDF描述？

Concept References

• Concept resources can include
• Existing taxonomies
• Trade and specialty nomenclature
• Standardized code sets (e.g. country codes)
• Reporting and classification schemes
• Ontologies
• ...

类似于取值的可能性规定

术语服务的目的（Why）

Terminology Resources are Heterogeneous

• Structure -varies from code/value pairs to complex formalisms such as NCI Thesaurus or SNOMED-CT
• Size –varies from 3 or 4 entries to well over half a million
• Format –can be CSV’s, SQL Tables, XML Documents, OWL

Terminology = content + software

• Sophisticated text search algorithms
• DL style inference
• Distribution, authoring, performance...

本方案只是基于Protégé，或者把Protégé作为一个注册系统使用的考虑。在Web环境中可能需要SW的架构。不过这两者应该可以转换，而对于Protégé社区来说，目前的方案更易实现。

把软件的功能也放入注册系统，似乎搞得太复杂了。可以采用类似于MIME的机制。

The Common Terminology Services (CTS) API

• (Relatively) Simple API
• Read-only
• A specification on how to do things like
  • List supported code systems
  • Get code system information
  • Search coded concepts by text
  • Traverse relationships
• Draft HL7 / ANSI Standard

这倒是个可以借鉴的想法。在Web上，以REST（WS）方式实现。不过该方案支持多种服务：SOAP/LDAP/Lit（LexGrid？）

目前似乎还有运行效率以及系统完善（成为一标准的服务）上的问题。

似乎应用于特殊领域（Health care）比较合适，还难以作为普适的方式展开。