Who can recommend tools/software to visualize knowledge graphs with RDF* support? (https://w3c.github.io/rdf-star/cg-spec/editors_draft.html) Stardog has something like this, but not very flexible/adaptible imo...
Could you please give details about your usage and which pain points are you trying to make disappear ? In our team, we have been using Protégé (https://protege.stanford.edu) for personal visualisation (WebProtégé for collaborative edition). I will be interested in other tools, too, though.
Great question Maja 💯 I have used Protege in the past, but at a very beginner level, very curious to learn more about that
For storing RDF* data, the Ontotext recently published a blog post on on it and I anticipate that it is supported or in the process of being supported. Similarly, RDF* data can be imported to Neo4J through the neosemantics plugin.
Amine Saboni / daria Does Protege 5.x support RDF* as a serialization? I thought that it based on the OWL API, which does not seem to support Turtle* as a serialization.
There is also a GitHub page on preliminary implementations of RDF*
Quentin R. we mainly use XML serialization for integration purposes, but it seems that (Web)Protégé supports rdf/turtle too.
With knowledge graph, I mean not the ontology itself, but the underlying linked data using the ontology, i.e. basically the instance level. Amine Saboni, daria Which tool in Protege supports visualization of these instances? I only know of Ontograph, OWLviz, WebVOWL for visualization of the classes. My question is really about the visualization. I have never seen an intuitive visualization of a knowledge graph. Especially I don't want the ontological classes and the instances in my KG to appear on the same graph as this would make the graph explode and make it even messier. I would like a software where I can for example
color instances of different classes in different colors
display RDF* statements like edge properties preferably with
filters for specific values or
ability to scale the edges according to the RDF* statements' value
So basically RDF* combines knowledge graphs with property graphs, so I want to be able to use the advantages of bothh.
Well and of course support for import of external files as I have my KG already and don't want to recreate it manually XD
I might not be the best person to answer, as I am not an ontology expert (we do manage/visualize individuals dynamically with python objects, overloading rdf syntax with business rules). However, as Protégé is able to load collections of individuals without class definition, an additional plugin might satisfy your needs (I would not have much hope on that).
Maja-O. L., we have found the same issue, though we visualize the "data" that is in the graph in a "knowledge store viewer" that sort of feels like a wiki - but only in that entities represent what would be "pages" in a wiki, but it is anything but a wiki - as the whole GUI interprets the knowledge store ontology live - so the GUI doesn't understand an object specifically, but uses the ontology to "know" how to display it. We allow plug-ins for specific entity types that allow different visualizations for a person versus a place versus a vehicle for example if one doesn't want the basic "this is an entity in your knowledge store, with your relationships: generic view. For us, we wanted an EASY way to deal with the class definition - without the data blowing up the display. We like to keep the data separate from the definition. We don't find any of the current editors very friendly to support this. Let me know if you find something different in your research, and we will do the same. Have you looked at OWLGrEd Ontology Editor? An interesting concept in some ways.
This is super interesting. What I’m hearing from the thread contributors is: instance-level visualization does not work for model-level visualization — it’s either inefficient or too awkward/cluttered for modeling workflow. Did I understand correctly? I’m interested in knowing whether there is any preference for old-school text-based or OO/ERD-style visualization (still k-graph underneath). Or, do we need something new?
Thanks for the link Juan S.. Looks good. I’m really asking the question because I spent a large slice of my career designing and implementing graph modeling and CASE (remember those?) toolsets and it feels like we’re at one of those cyclic junctures where repurposing trusted tools for the new era might solve some of the current frustrations that new-era practitioners are expressing.
Agreed!!
