You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ensure that all enum values throughout the specification have an
explicit property assigned to them. This is important for consistency of
the RDF serialisation.
Copy file name to clipboardExpand all lines: src/sssom_schema/schema/sssom_schema.yaml
+26-8Lines changed: 26 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -27,8 +27,12 @@ default_range: string
27
27
enums:
28
28
sssom_version_enum:
29
29
permissible_values:
30
-
"1.0": SSSOM specification version 1.0
31
-
"1.1": SSSOM specification version 1.1
30
+
"1.0":
31
+
meaning: sssom:version1.0
32
+
description: SSSOM specification version 1.0
33
+
"1.1":
34
+
meaning: sssom:version1.1
35
+
description: SSSOM specification version 1.1
32
36
entity_type_enum:
33
37
permissible_values:
34
38
owl class:
@@ -59,22 +63,36 @@ enums:
59
63
rdf property:
60
64
meaning: rdf:Property
61
65
composed entity expression:
66
+
meaning: sssom:ComposedEntityExpression
62
67
description: This value indicates that the entity ID does not represent a single entity, but a composite involving several individual entities. This value MUST NOT be used in the predicate_type slot. This specifications does not prescribe how an ID representing a composite entity should be interpreted; this is left at the discretion of applications.
0 commit comments