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
The new version of linkml 1.8.2+ fixed an issue with how range:uri is expressed in jsonld-context. After talking with LinkML community it seems like range:curie is not expressed in json format and all curie must be expanded into uri. Certain attributes from biolink i.e. category are range:uriorcurie and are now causing issues when we import the data into the graph, since the data value is forced into being interpreted as a uri. We need to resolve this issue but either changing the type of category to range:curie in our bican_biolink model or providing a uri data value to category.
Note: Since range:curie is not expressed in json, the type gets defaulted to range:string; which is how range:uri and range:uriorcurie were also expressed before the updates were made to linkml. Changing the range to curie will allow us to keep track of the ideal/correct type for this attribute in other formats i.e yaml and pydantic.
The text was updated successfully, but these errors were encountered:
The new version of linkml 1.8.2+ fixed an issue with how
range:uri
is expressed in jsonld-context. After talking with LinkML community it seems likerange:curie
is not expressed in json format and allcurie
must be expanded intouri
. Certain attributes from biolink i.e.category
arerange:uriorcurie
and are now causing issues when we import the data into the graph, since the data value is forced into being interpreted as auri
. We need to resolve this issue but either changing the type ofcategory
torange:curie
in ourbican_biolink
model or providing auri
data value tocategory
.Note: Since
range:curie
is not expressed in json, the type gets defaulted torange:string
; which is howrange:uri
andrange:uriorcurie
were also expressed before the updates were made to linkml. Changing the range tocurie
will allow us to keep track of the ideal/correct type for this attribute in other formats i.eyaml
andpydantic
.The text was updated successfully, but these errors were encountered: