From 7df9a53bfe2e3022d9889b3de71d56fa1c4fd65d Mon Sep 17 00:00:00 2001 From: "Tiffany J. Callahan" Date: Tue, 12 Dec 2023 23:24:55 -0700 Subject: [PATCH] Update README.md fixing typo --- resources/construction_approach/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/resources/construction_approach/README.md b/resources/construction_approach/README.md index db3bcc8c..a9fac9d1 100644 --- a/resources/construction_approach/README.md +++ b/resources/construction_approach/README.md @@ -52,7 +52,7 @@ Instance-Instance | Relations + Inverse Relations | **`HGNC_1234567`, `REL`, `HG
-*Note.* `UUID` is a `BNode` that is created from an md5 hash of concatenated URIs. The URIs used in the hash string includes the subject and object URIs (each appended with "subject" and "object", respectfully) in addition to a relation (`<>`). To account for future use cases, we have devised a heuristic to determine what is used for `<>`: (1) for a given relation, determine if it has an inverse (via `owl:InverseOf`); (2) sort the relations alphabetically; and (3) select the first relation. The selected relation is then used for creating both `UUID` `BNodes` (i.e. `UUID1` and `UUID2` in all examples in the table above). For example, if the relations were `causes` and `caused_by` both `UUID` `BNodes` would be created using `caused_by`. Please note that all `UUID` `BNodes` created during the construction process are explicitly defined within the `pkt` namespace (`https://github.com/callahantiff/PheKnowLator/pkt/`). +*Note.* `UUID` is a `BNode` that is created from an md5 hash of concatenated URIs. The URIs used in the hash string includes the subject and object URIs (each appended with "subject" and "object", respectively) in addition to a relation (`<>`). To account for future use cases, we have devised a heuristic to determine what is used for `<>`: (1) for a given relation, determine if it has an inverse (via `owl:InverseOf`); (2) sort the relations alphabetically; and (3) select the first relation. The selected relation is then used for creating both `UUID` `BNodes` (i.e. `UUID1` and `UUID2` in all examples in the table above). For example, if the relations were `causes` and `caused_by` both `UUID` `BNodes` would be created using `caused_by`. Please note that all `UUID` `BNodes` created during the construction process are explicitly defined within the `pkt` namespace (`https://github.com/callahantiff/PheKnowLator/pkt/`).