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
Schemas may currently be annotated with the owl slot to denote the OWL equivalent, e.g., in the recipe schema:
FoodItem:
is_a: CompoundExpressionannotations:
owl: IntersectionOfattributes:
food:
description: the food itemrange: FoodTypeslot_uri: BFO:0000051annotations:
owl: ObjectProperty, ObjectSomeValuesFromstate:
description: the state of the food item (e.g. chopped, diced)annotations:
owl: DataProperty, DataHasValue
This only comes into play when serializing as OWL.
We can do the same for KGX, as the schema does not define whether a class defines a node, edge, higher-level association, etc.
The annotations field should be able to accept explicit directions for what should be subject, predicate, object and properties.
Perhaps this should be present elsewhere in the LinkML infrastructure.
The text was updated successfully, but these errors were encountered:
At BBOP group meeting today @cmungall mentioned there is general undocumented support in LinkML to handle these kind of annotations but they aren't generally processed by any utility. Would be useful to have a similar strategy for KGX, such that it is treated as a "flavor" of CSV with some added considerations.
Schemas may currently be annotated with the
owl
slot to denote the OWL equivalent, e.g., in therecipe
schema:This only comes into play when serializing as OWL.
We can do the same for KGX, as the schema does not define whether a class defines a node, edge, higher-level association, etc.
The annotations field should be able to accept explicit directions for what should be subject, predicate, object and properties.
Perhaps this should be present elsewhere in the LinkML infrastructure.
The text was updated successfully, but these errors were encountered: