Changes between Version 1 and Version 2 of ADL1.4

Timestamp:

May 19, 2008, 10:54:07 PM (16 years ago)

Author:

KOBAYASHI, Shinji

Comment:

--

ADL1.4

@@ -28 +28 @@
 1. Introduction
 
-== 1.1 目的 ==
+=== 1.1 目的 ===
 1.1 Purpose
 
@@ -54 +54 @@
  * Health data managers.
 
-== 1.2 関連する文書 ==
+=== 1.2 関連する文書 ===
 1.2 Related Documents
 
@@ -72 +72 @@
  * The openEHR Archetype Profile (oAP)
 
-== 1.3 命名規則 ==
+=== 1.3 命名規則 ===
 1.3 Nomenclature
 
@@ -79 +79 @@
 In this document, the term ‘attribute’ denotes any stored property of a type defined in an object model, including primitive attributes and any kind of relationship such as an association or aggregation. XML ‘attributes’ are always referred to explicitly as ‘XML attributes’.
 
-== 1.4 状況 ==
+=== 1.4 状況 ===
 1.4 Status
 
@@ -97 +97 @@
 
 New versions are announced on openehr-announce@openehr.org.
+
+== 2 概要 ==
+
+2 Overview
+
+=== 2.1 ADLとは何か ===
+
+2.1 What is ADL?
+
+アーキタイプ定義言語(ADL; Archetype Definition Language)はアーキタイプを表現する形式言語であり、ドメインエントリーの制約ベースのモデルである。つまり、「構造化されたビジネスルール」といってもいいようなものである。アーキタイプの概念はBealによって記載されている[[FootNote(Beale T. Archetypes: Constraint-based Domain Models for Future-proof Information Systems.
+OOPSLA 2002 workshop on behavioural semantics.[BR] Available at http://www.deepthought.com.au/it/archetypes.html)]], [[FootNote(Beale T. Archetypes: Constraint-based Domain Models for Future-proof Information Systems. OOPSLA 2002 workshop on behavioural semantics.[BR] Available at http://www.deepthought.com.au/it/archetypes.html)]]。
+
+Archetype Definition Language (ADL) is a formal language for expressing archetypes, which are
+constraint-based models of domain entities, or what some might call ‘structured business rules’. The
+archetype concept is described by Beale [1], [2]. The openEHR Archetype Object Model [3]
+describes the definitive semantic model of archetypes, in the form of an object model. The ADL syntax
+is one possible serialisation of an archetype.
+The openEHR archetype framework is described in terms of Archetype Definitions and Principles [6]
+and an Archetype System [7]. Other semantic formalisms considered in the course of the development
+of ADL, and some which remain relevant are described in detailed in section 10 on page 109.
+ADL uses three other syntaxes, cADL (constraint form of ADL), dADL (data definition form of
+ADL), and a version of first-order predicate logic (FOPL), to describe constraints on data which are
+instances of some information model (e.g. expressed in UML). It is most useful when very generic
+information models are used for describing the data in a system, for example, where the logical concepts
+PATIENT, DOCTOR and HOSPITAL might all be represented using a small number of classes such
+as PARTY and ADDRESS. In such cases, archetypes are used to constrain the valid structures of
+instances of these generic classes to represent the desired domain concepts. In this way future-proof
+information systems can be built - relatively simple information models and database schemas can be
+defined, and archetypes supply the semantic modelling, completely outside the software. ADL can
+thus be used to write archetypes for any domain where formal object model(s) exist which describe
+data instances.
+When archetypes are used at runtime in particular contexts, they are composed into larger constraint
+structures, with local or specialist constraints added, via the use of templates. The formalism of templates
+is dADL. Archetypes can be specialised by creating an archetypes that reference existing
+archetypes as parents; such archetypes can only make certain changes while remaining compatible
+with the parent.
+Another major function of archetypes is to connect information structures to formal terminologies.
+Archetypes are language-neutral, and can be authored in and translated into any language.
+Finally, archetypes are completely path-addressable in a manner similar to XML data, using path
+expressions that are directly convertible to Xpath expressions.
+2.1.1 Structure
+Archetypes expressed in ADL resemble programming language files, and have a defined syntax.
+ADL itself is a very simple “glue” syntax, which uses two other syntaxes for expressing structured
+constraints and data, respectively. The cADL syntax is used to express the archetype definition,
+while the dADL syntax is used to express data which appears in the language, description, ontology,
+and revision_history sections of an ADL archetype. The top-level structure of an ADL archetype
+is shown in FIGURE 1.
+
+[[FootNote]]