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
Any use of yq should be compact, general and well-documented. It should not be used to apply name-based modifications which can be handled by sheets_and_friends' modifications_and_validation script.
Currently, the validation updates specified by the --validation_config_tsv argument are only triggered when detecting
specified slot ranges
specified slot string_serializations
and only take these actions:
overwriting a slot's pattern
overwriting a slot's DH datatype... which is just a type range as an xsd CURIE?
I don't think the DH datatype changes are necessary any more, as class ranges are generally replaced by the yq operations, and DH seems to understand the range specifications that consist of a linkml:type in name alone.
I would like to continue using yq for these general validation updates, or add additional trigger types to modifications_and_validation.
Any use of yq should be compact, general and well-documented. It should not be used to apply name-based modifications which can be handled by sheets_and_friends'
modifications_and_validation
script.Currently, the validation updates specified by the
--validation_config_tsv
argument are only triggered when detectingrange
sstring_serialization
sand only take these actions:
pattern
I don't think the DH datatype changes are necessary any more, as class ranges are generally replaced by the yq operations, and DH seems to understand the range specifications that consist of a
linkml:type
inname
alone.I would like to continue using yq for these general validation updates, or add additional trigger types to
modifications_and_validation
.cc @pkalita-lbl
The text was updated successfully, but these errors were encountered: