Changes between Version 10 and Version 11 of Archtectural Overview Paths


Ignore:
Timestamp:
Apr 18, 2008, 10:41:38 PM (10 years ago)
Author:
KOBAYASHI, Shinji
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Archtectural Overview Paths

    v10 v11  
    11[wiki:"Archtectural Overview index" TOC] [wiki:"Archtectural Overview Archetypes" PREV] [wiki:"Archtectural Overview Terminology" NEXT]
    2 
     2[[TOC]]
    33この文書は[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]の翻訳である。正確性については保証しないので,適宜原文を参照すること
    44
    5 
    65= 11 パスとロケーター =
    7 [[TOC]]
     6
    8711 Paths and Locators
    98
    10 == 11.1 概要 ==
     9== 11.1 概要 == #overview
    1110
    121111.1 Overview
     
    2019Technically, 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.
    2120
    22 == 11.2 パス ==
     21== 11.2 パス == #path
    2322
    242311.2 Paths
    2524
    26 === 11.2.1 基本文法 ===
     25=== 11.2.1 基本文法 === #syntax
    2726
    282711.2.1 Basic Syntax
     
    5453·       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 `//'.
    5554
    56 === 11.2.2 述語表現 ===
     55=== 11.2.2 述語表現 === #predicate
    5756
    585711.2.2 Predicate Expressions
     
    150149        AND value/defining_code/code_string = "A04"]
    151150
    152 === 11.2.3 最上位構造におけるパス ===
     151=== 11.2.3 最上位構造におけるパス === #top_level
    153152
    15415311.2.3 Paths within Top-level Structures
     
    186185Paths within the other top level types follow the same general approach, i.e. are created by following the required attributes down the hierarchy.
    187186
    188 === 11.2.4 データ・パスと一意性 ===
     187=== 11.2.4 データ・パスと一意性 === #uniqueness
    189188
    19018911.2.4 Data Paths and Uniqueness
     
    402401  * 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.
    403402
    404 == 11.3 EHR URI ==
     403== 11.3 EHR URI == #uri
    405404
    40640511.3 EHR URIs
     
    410409There 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.
    411410
    412 === 11.3.1 EHR参照URI ===
     411=== 11.3.1 EHR参照URI === #reference
    413412
    41441311.3.1 EHR Reference URIs