Changes between Version 25 and Version 26 of openEHR XML-schemas - Release 1.0.1
- Timestamp:
- Aug 10, 2007, 9:27:59 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
openEHR XML-schemas - Release 1.0.1
v25 v26 111 111 ||Interval<DateTime>||IntervalOfDateTime (BaseTypes.xsd)|| 112 112 ||Interval<Duration>||IntervalOfDuration (BaseTypes.xsd)|| 113 ||DV_INTERVAL<DV_ORDERED>||only one type is used, namely DV_INTERVAL, with lower and upper of type DV_ORDERED. Software implementations 114 of the relevant generic types (DV_INTERVAL<DV_DATE> etc) are expected to implement further typing sensibly. 113 ||DV_INTERVAL<DV_ORDERED>||only one type is used, namely DV_INTERVAL, with lower and upper of type DV_ORDERED. Software implementations of the relevant generic types (DV_INTERVAL<DV_DATE> etc) are expected to implement further typing sensibly. 115 114 (BaseTypes.xsd)|| 116 115 ||VERSION<T>||only one type is used, namely VERSION. The subtype ORIGINAL_VERSION has its data attribute of type LOCATABLE (Version.xsd)|| … … 120 119 Multiple Inheritance 121 120 122 openEHRの参照モデルでは,多重継承を使っているところがいくつかある。すべての場合で,単一継承によるサブタイプで代替可能な関係(たとえば'is-a')ではあるが, ほかの121 openEHRの参照モデルでは,多重継承を使っているところがいくつかある。すべての場合で,単一継承によるサブタイプで代替可能な関係(たとえば'is-a')ではあるが,機能の継承(たとえば'has-a')や多重継承が常に用いられることもある。参照モデルでは,rm.data_types.quantity.DV_INTERVALやrm.data_types.qualntity.date_timeクラスなどはこのような継承を使っている。 123 122 124 123 There are a couple of places where multiple inheritance occurs in the openEHR reference model. In all cases, only one inheritance branch corresponds to subtyping in the substitutability (i.e. 'is-a') sense; the other branches are always 'facility' or 'mix-in' inheritance. In the RM, classes inheriting in this way include rm.data_types.quantity.DV_INTERVAL and the rm.data_types.quantity.date_time classes. The latter inherit only interface, which has no visibility in XML-schema. For the former, the inheritance of Interval<T> by DV_INTERVAL<T> is done in the schema simply by direct inclusion, since the other branch of inheritance (of DATA_VALUE) is the one which must be visible to schema processing.