Skip to content

Commit

Permalink
Clarify requirements for literal mappings.
Browse files Browse the repository at this point in the history
When describing how to represent literal mappings, use BCP 14 keywords
to clarify what exactly is required.
  • Loading branch information
gouttegd committed Aug 9, 2024
1 parent 6fb5294 commit 454cb27
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions src/docs/spec-model.md
Original file line number Diff line number Diff line change
Expand Up @@ -100,9 +100,9 @@ The SSSOM model is primarily intended to represent mappings between semantic ent

To represent a mapping whose subject (resp. object) is a literal:

* the `subject_type` (resp. `object_type`) slot is set to `rdfs literal`;
* the `subject_label` (resp. `object_label`) slot is set to the literal itself;
* the `subject_id` (resp. `object_id`) slot is left empty.
* the `subject_type` (resp. `object_type`) slot MUST be set to `rdfs literal`;
* the `subject_label` (resp. `object_label`) slot MUST be set to the literal itself;
* the `subject_id` (resp. `object_id`) slot MAY be left empty.

The last point is an exception to the normal rules about required slots, which state that a mapping must always have a `subject_id` and an `object_id`. Implementations MUST accept a mapping without a `subject_id` (resp. `object_id`) _if and only if_ the `subject_type` (resp. `object_type`) slot is set to `rdfs literal`.

Expand Down

0 comments on commit 454cb27

Please sign in to comment.