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 display of rdf:List #11

Open
VladimirAlexiev opened this issue Aug 23, 2022 · 0 comments
Open

special display of rdf:List #11

VladimirAlexiev opened this issue Aug 23, 2022 · 0 comments

Comments

@VladimirAlexiev
Copy link
Owner

VladimirAlexiev commented Aug 23, 2022

Continuing #10, the display of rdf:Lists is pretty ugly because it puts siblings (list members) at different ranks in the diagram, and thus obscures what is going on. Lists are involved in:

  • OWL constructs (eg intersectionOf, unionOf)
  • SHACL constructs (eg sh:and, sh:or)

It would be nicer to have a special display: a horizontal box with dots inside, something like

This won't be easy for several reasons.

RDF processing

  • most lists in the wild don't have type a rdf:List but need to be recognized by rdf:first, rdf:rest
  • need special processing of the list RDF: to consume it all, produce diagram markup, and delete the triples

PlantUML

  • PlantUML can mix JSON structures into class/object diagrams, eg see
    image
  • but those cannot refer to other class/object nodes i.e. they are trees not graphs
    (unlike standalone JSON diagrams, JSON embedded in class/object diagram never displays links, only nested tree structures)

So currently I don't see any way to do this with PlantUML. I could do it with Graphviz dot (or with https://plantuml.com/dot) but I can't afford to rework (downgrade) my tool to use dot instead of PlantUML.

Discussion at https://forum.plantuml.net/15481/possible-link-elements-from-two-jsons-with-both-jsons-embeded?show=15567#c15567

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant