Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Special Relations / When is an IRI a node #22

Open
BenjaminHofstetter opened this issue Oct 23, 2024 · 0 comments
Open

Special Relations / When is an IRI a node #22

BenjaminHofstetter opened this issue Oct 23, 2024 · 0 comments
Labels
enhancement New feature or request next Topic for the next version

Comments

@BenjaminHofstetter
Copy link
Contributor

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.

  1. plain mode (create all nodes)

  2. only show classes if the appear as a subject

  3. show rdfs type in the header of the node and never create nodes

  4. is for education

  5. is how it is now

  6. may be it's good to have it but it will maybe not implemented

@BenjaminHofstetter BenjaminHofstetter added enhancement New feature or request next Topic for the next version labels Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request next Topic for the next version
Projects
None yet
Development

No branches or pull requests

1 participant