Open BenjaminHofstetter opened 2 weeks ago
When do we show a node?
The current sketch (old) is showing an IRI as a node if it appears as a Subject or an Object except rdf:type.
<a> <x> <b> .
This creates a node ---x--> . This creates two nodes.
But but type is different:
<a> a <b> . <c> a <b> .
this creates a node and a node in the UI. And it shows the type relation in the node predicate object table but doesn't create the arrow. Why not? This is a display optimisation. I did some tests. If we create nodes for types then the amount of arrows increases a lot. I decided we don't need that to reduce the amount of arrows.
But ....
<a> a <b> . <c> a <b> . <b> <label> "I am a class".
If we have the class as a subject then it appears as node.
This behaviour may be configured in the future.
plain mode (create all nodes)
only show classes if the appear as a subject
show rdfs type in the header of the node and never create nodes
is for education
is how it is now
may be it's good to have it but it will maybe not implemented
When do we show a node?
The current sketch (old) is showing an IRI as a node if it appears as a Subject or an Object except rdf:type.
This creates a node ---x--> . This creates two nodes.
But but type is different:
this creates a node and a node in the UI. And it shows the type relation in the node predicate object table but doesn't create the arrow.
Why not? This is a display optimisation. I did some tests. If we create nodes for types then the amount of arrows increases a lot. I decided we don't need that to reduce the amount of arrows.
But ....
If we have the class as a subject then it appears as node.
This behaviour may be configured in the future.
plain mode (create all nodes)
only show classes if the appear as a subject
show rdfs type in the header of the node and never create nodes
is for education
is how it is now
may be it's good to have it but it will maybe not implemented