Changes between Version 4 and Version 5 of Archtectural Overview Paths

Timestamp:

Oct 26, 2007, 2:42:38 PM (17 years ago)

Author:

KOBAYASHI, Shinji

Comment:

--

Archtectural Overview Paths

@@ -181 +181 @@
 Paths within the other top level types follow the same general approach, i.e. are created by following the required attributes down the hierarchy. 
 
-11.2.4 データ・パスと一意性
+=== 11.2.4 データ・パスと一意性 ===
 
 11.2.4 Data Paths and Uniqueness
@@ -397 +397 @@
 ·       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. 
 
-11.3 EHR URI 
+== 11.3 EHR URI ==
 
 11.3 EHR URIs 
@@ -405 +405 @@
 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. 
 
-11.3.1 EHR参照URI 
+=== 11.3.1 EHR参照URI ===
 
 11.3.1 EHR Reference URIs 
@@ -423 +423 @@
 An ehr:// URI implies the availability of a name resolution mechanism in ehr-space, similar to the DNS, which provides such services for http-, ftp- and other well-known URI schemes. Until such services are established, ad hoc means of dealing with ehr:// URIs are likely to be used, as well as more traditional http:// style references. The subsections below describe how URIs of both kinds can be constructed. 
 
-EHRロケーション
+==== EHRロケーション ====
 
 EHR Location 
@@ -439 +439 @@
 ehr://1234567@rmh.nhs.net/
 
-最上位構造のロケーター
+==== 最上位構造のロケーター ====
  
 Top-level Structure Locator
@@ -473 +473 @@
 ehr://1234567/87284370-2D4B-4e3d-A3F3-F303D2F4F34B
  
-項目のURI
+==== 項目のURI ====
 
 Item URIs 
@@ -489 +489 @@
         events[at0006, 'any event']/data/items[at0004]
  
-相対URI
+==== 相対URI ====
 
 Relative URIs