Changes between Version 10 and Version 11 of Archtectural Overview Paths
- Timestamp:
- Apr 18, 2008, 10:41:38 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Archtectural Overview Paths
v10 v11 1 1 [wiki:"Archtectural Overview index" TOC] [wiki:"Archtectural Overview Archetypes" PREV] [wiki:"Archtectural Overview Terminology" NEXT] 2 2 [[TOC]] 3 3 この文書は[http://svn.openehr.org/specification/TAGS/Release-1.0.1/publishing/html/architecture/overview/Output/front.html Archtectural Overview]の[http://www.openehr.org/svn/specification/TAGS/Release-1.0.1/publishing/html/architecture/overview/Output/archetyping.html 11 Paths and Locators]の翻訳である。正確性については保証しないので，適宜原文を参照すること 4 4 5 6 5 = 11 パスとロケーター = 7 [[TOC]] 6 8 7 11 Paths and Locators 9 8 10 == 11.1 概要 == 9 == 11.1 概要 == #overview 11 10 12 11 11.1 Overview … … 20 19 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. 21 20 22 == 11.2 パス == 21 == 11.2 パス == #path 23 22 24 23 11.2 Paths 25 24 26 === 11.2.1 基本文法 === 25 === 11.2.1 基本文法 === #syntax 27 26 28 27 11.2.1 Basic Syntax … … 54 53 · 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 `//'. 55 54 56 === 11.2.2 述語表現 === 55 === 11.2.2 述語表現 === #predicate 57 56 58 57 11.2.2 Predicate Expressions … … 150 149 AND value/defining_code/code_string = "A04"] 151 150 152 === 11.2.3 最上位構造におけるパス === 151 === 11.2.3 最上位構造におけるパス === #top_level 153 152 154 153 11.2.3 Paths within Top-level Structures … … 186 185 Paths within the other top level types follow the same general approach, i.e. are created by following the required attributes down the hierarchy. 187 186 188 === 11.2.4 データ・パスと一意性 === 187 === 11.2.4 データ・パスと一意性 === #uniqueness 189 188 190 189 11.2.4 Data Paths and Uniqueness … … 402 401 * the name value may be systematically defined to be a copy of one or more other attribute values. For example, in an EVENT object, name could clearly be a string copy of the time attribute. 403 402 404 == 11.3 EHR URI == 403 == 11.3 EHR URI == #uri 405 404 406 405 11.3 EHR URIs … … 410 409 There are two broad categories of URIs that can be used with any resource: direct references, and queries. The first kind are usually generated by the system containing the referred-to item, and passed to other systems as definitive references, while the second are queries from the requesting system in the form of a URI. 411 410 412 === 11.3.1 EHR参照URI === 411 === 11.3.1 EHR参照URI === #reference 413 412 414 413 11.3.1 EHR Reference URIs
