Changes between Version 3 and Version 4 of Archtectural Overview Paths
- Timestamp:
- Oct 26, 2007, 2:34:44 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Archtectural Overview Paths
v3 v4 1 11パスとロケーター 2 1 = 11 パスとロケーター = 2 [[TOC]] 3 3 11 Paths and Locators 4 4 5 11.1 概要 5 == 11.1 概要 == 6 6 7 7 11.1 Overview … … 15 15 Technically, the combination of a path and a Version identifier such as OBJECT_VERSION_ID forms a "globally qualified node reference" which can be expressed using LOCATABLE_REF. It can also be expressed in portable URI form as a DV_EHR_URI, known as a "globally qualified node locator". Either representation enables any openEHR data node to be referred to from anywhere. This section describes the syntax and semantics of paths, and of the URI form of reference. In the following, the term "archetype path" means a path extracted from an archetype, while "data path" means one that identifies an item in data. They are no different formally, and this terminology is only used to indicate where they are used. 16 16 17 11.2 パス 17 == 11.2 パス == 18 18 19 19 11.2 Paths 20 20 21 11.2.1 基本構文 21 === 11.2.1 基本構文 === 22 22 23 23 11.2.1 Basic Syntax … … 49 49 · path pattern: path starts with or contains a the symbol `//' and is taken to be a pattern which can match any number of path segments in the data; the pattern is matched if an actual path can be found anywhere in the structure for which part of the path matches the path section before the `//' symbol, and a later section matches the section appearing after the `//'. 50 50 51 11.2.2 述語表現 51 === 11.2.2 述語表現 === 52 52 53 53 11.2.2 Predicate Expressions 54 54 55 概要 55 ==== 概要 ==== 56 56 57 57 Overview … … 81 81 The second limitation of basic paths is that they cannot locate objects based on other conditions, such as the object having a child node with a particular value. To address this, predicate expressions can be used to select an object on the basis of other conditions relative to the object, by including boolean expressions including paths, operators, values and parentheses. The syntax of predicate expressions used in openEHR is a subset of the Xpath syntax for predicates with a small number of short-cuts. 82 82 83 アーキタイプと述語 83 ==== アーキタイプと述語 ==== 84 84 85 85 Archetype path Predicate … … 97 97 This path refers to the magnitude of a 1-minute Apgar total in an Observation containing a full Apgar result structure. In this path, the [atNNNN] predicates are a shortcut for [@archetype_node_id = `atNNNN'] in standard Xpath. Note that while an archetype path is always unique in an archetype, it can correspond to more than one item in runtime data, due to the repeated use of the same archetype node within a container. 98 98 99 名前に基づく述語 99 ==== 名前に基づく述語 ==== 100 100 101 101 Name-based Predicate … … 117 117 /data/events[at0001, `standing'] 118 118 119 その他の述語 119 ==== その他の述語 ==== 120 120 121 121 Other Predicates … … 145 145 AND value/defining_code/code_string = "A04"] 146 146 147 11.2.3 最上位構造におけるパス 147 === 11.2.3 最上位構造におけるパス === 148 148 149 149 11.2.3 Paths within Top-level Structures
