Proposal / Task for Exposing Graph Versioning

[YaphetKG]

Finding ways to expose graph version in the running qlever / fuseki servers.

Here's an initial proposal:

We could add a .ttl file on build time which will use the PAV ontology (https://pav-ontology.github.io/pav/) and contain the following triple

<http://purl.org/okn/frink/kg-short-name> pav:version "`lakefs-future-tag`" .

This could be create before the merging / conversion takes place by the pipeline itself, ensuring that the resulting graph would have it's build version baked in there.

As for other information build time etc... PAV has other predicates that can be used and added to this .ttl file.

[cbizon]

This looks reasonable to me. Two thoughts -

1. If this is in the graph, how does that information make it on our pages?
2. I think on the page it would be a good idea to also put an update timestamp (this graph was last updated in Nov 2025). Should we use another PAV predicate to handle that the same way as the version or should we use some other source of information?

[balhoff]

@YaphetKG use this format for the graph IRIs: <https://purl.org/okn/frink/kg/kg-short-name>

[YaphetKG]

Void nt file will now contains this information and is part of the pipeline.

[YaphetKG]

This can be marked as done.