Changes between Version 12 and Version 13 of Archtectural Overview Overview
- Timestamp:
- Jul 27, 2007, 1:12:16 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Archtectural Overview Overview
v12 v13 32 32 The abstract specifications are also available in a tool-oriented computable UML format in order to enable development of software and systems. The computable expressions for all practical purposes can be assumed as being a lossless rendition of the published abstract specifications. 33 33 34 一方で,実装技術仕様は特定のモデルからさまざまなプログラミング言語やスキーマ言語により抽象仕様の表現と対応している。その表現は完全ではなく通常は部分的に変換される。実装技術はプログラミング言語やXMLのような連続した形式から,データベースや分散オブジェクトインターフェースにいたるまで数多くある。それぞれに限界と長所がある. 35 既存の実装技術によるopenEHRの抽象モデルの実装への取り組みはすべて,まず特定の技術のためのITSを定義し,それに従い抽象モデルをその技術的表現に形式を置き換えていくということになる。 36 34 37 The implementation technology specifications on the other hand correspond to the expression of abstract specifications in various programming and schema languages, each of which represents an imperfect and usually partial transformation from the specification models. There are numerous implementation technologies, ranging from programming languages, serial formalisms such as XML, to database and distributed object interfaces. Each of these has its own limits and strengths. The approach to implementing any of the openEHR abstract models in a given implementation technology is to firstly define an ITS for the particular technology, then to use it to formally map the abstract models into expressions in that technology. 35 38