The KGE Archiver plans to use the KGX Validator code to validate KGX knowledge graphs; however, this validation is only rudimentary (and doesn't yet deal with "deep" Biolink Model semantics). Where and how should such validation be done in the future.
The platform could also use graph-summary to generate the desired content_metadata.json, instead of expecting users to provide it as an upload(?).
The platform needs to support JSON Lines (perhaps other formats) in addition to TSV. KGX transformcould provided this?
The KGE Archiver plans to use the KGX Validator code to validate KGX knowledge graphs; however, this validation is only rudimentary (and doesn't yet deal with "deep" Biolink Model semantics). Where and how should such validation be done in the future.
The platform could also use
graph-summary
to generate the desired content_metadata.json, instead of expecting users to provide it as an upload(?).The platform needs to support JSON Lines (perhaps other formats) in addition to TSV. KGX
transform
could provided this?