Changes between Version 6 and Version 7 of Support Information Model 3 Assumed Types


Ignore:
Timestamp:
Sep 29, 2008, 9:08:19 PM (16 years ago)
Author:
KOBAYASHI, Shinji
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Support Information Model 3 Assumed Types

    v6 v7  
    3838The assumptions that openEHR makes about existing types are documented below in terms of interface definitions. Each of these definitions contains only the assumptions required for the given type to be used in the openEHR Reference Model -it is not by any means a complete interface definition. The name and semantics of any function used here for an assumed type might not be identical to those found in some implementation technologies. Any mapping required should be stated in the relevant implementation technology specification (ITS). To give a concrete example, where the assumed Set<T> type defined below has an operation has(item: T): Boolean which is used throughout the openEHR specifications, Java has the method contains() on its Set<T> class. In a Java implementation, the contains() method should then be used throughout the openEHR classes as expressed in Java, in place of the has() method.
    3939
    40 [file:///home/skoba/src/openehr-jp/adl/trunk/pdf2html/rm/support_im/support_im.htm#LinkTarget_15315 Editors:{T Beale, S Heard}, {D Kalra, D Lloyd}] [file:///home/skoba/src/openehr-jp/adl/trunk/pdf2html/rm/support_im/support_im.htm#LinkTarget_19440 Page 13 of 67] Date of Issue:[file:///home/skoba/src/openehr-jp/adl/trunk/pdf2html/rm/support_im/support_im.htm#LinkTarget_15448 08 Apr 2007]
    41 
    42   © 2003-2006 The openEHR Foundation    email: info@openEHR.org web: !http://www.openEHR.org
    43 
    44 Assumed Types [file:///home/skoba/src/openehr-jp/adl/trunk/pdf2html/rm/support_im/support_im.htm#LinkTarget_15311 Support Information Model] Rev [file:///home/skoba/src/openehr-jp/adl/trunk/pdf2html/rm/support_im/support_im.htm#LinkTarget_15315 1.6.0]
    45 
    46 === 3.2 Inbuilt Primitive Types === #LinkTarget_16135
     40== 3.2 組み込みプリミティブ型 == #inbuilt
     413.2 Inbuilt Primitive Types
     42
     43
     44以下の型はopenEHRの実装形式において想定される最小範囲内のプリミティブ型を構成している。
     45
    4746The following types consititute the minimum set of primitive types assumed by openEHR of an implementation formalism.
     47
     48||openEHRでの型名||詳細||ISO 11404での型||
     49||Octet||8ビットの値を表現する型。||Octet||
     50||Character||8ビットの文字セット(ISO: “repertoire”)のメンバーの値を表現する型。||Character||
     51||Boolean||論理的に真/偽値を表現する。通常は物理的には整数で表現されるがそうでなくてもよい||Boolean||
     52||||||||
     53||Integer||32ビット整数を表現する||Integer||
     54||Real||32ビット実数をIEEE単精度浮動小数点を含む相互可用性のある表現であらわす。||Real||
     55||Double||６４ビット実数を表現する型。IEEEの倍精度浮動小数点を含む何らかの相互可用性を持つ表現をとる。||Real||
     56
     57
    4858
    4959||Type name in openEHR||Description||ISO 11404 Type||
    … …  
    5666||Double||type which represents 64-bit real numbers, in any interoperable representation including double-precision IEEE floating point.||Real||
    5767
    58 [file:///home/skoba/src/openehr-jp/adl/trunk/pdf2html/rm/support_im/support_im.htm#LinkTarget_16193 FIGURE 2]  illustrates the built-in primitive types. Simple inheritance relationships are shown which facilitate the type descriptions below. A class “Any” is used to stand for the usual top-level class in all object-oriented type systems, typically called something like “Any” or “Object”. Inheritance from or subsitutability for an Any class is not assumed in openEHR (hence the dotted lines in the UML). It is used here to enable basic operations like ‘=’ to be described once for the type Any, rather than in every subtype. The type Ordered_numeric is on the other hand assumed for purposes of specification in the openEHR data_types.quantity package, and is intended to be mapped to an equivalent type in a real type system (e.g. in Java, java.lang.Number). Here it is assumed that the operations defined on Ordered_numericare available on the types Integer, Realand Double in implementation type systems, where relevant. Data-oriented implementation type systems such as XML-schema do not have such operations.
     68FIGURE 2  illustrates the built-in primitive types. Simple inheritance relationships are shown which facilitate the type descriptions below. A class “Any” is used to stand for the usual top-level class in all object-oriented type systems, typically called something like “Any” or “Object”. Inheritance from or subsitutability for an Any class is not assumed in openEHR (hence the dotted lines in the UML). It is used here to enable basic operations like ‘=’ to be described once for the type Any, rather than in every subtype. The type Ordered_numeric is on the other hand assumed for purposes of specification in the openEHR data_types.quantity package, and is intended to be mapped to an equivalent type in a real type system (e.g. in Java, java.lang.Number). Here it is assumed that the operations defined on Ordered_numericare available on the types Integer, Realand Double in implementation type systems, where relevant. Data-oriented implementation type systems such as XML-schema do not have such operations.
    5969
    6070''Any ''